Twilio · Authy · CWE-203 · published 2024-07-02
CVE-2024-39891Twilio Authy Information Disclosure Vulnerability
This week Known exploited in the wild.
CVE-2024-39891 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2024-07-23. EPSS estimates a 1.7% chance of exploitation in the next 30 days, higher than 77% of all CVEs. This Authy vulnerability: CVSS 5.3 (v3.1), attacks can be automated. CISA’s required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. US federal agencies must remediate by 2024-08-13. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (federal due date 2024-08-13)
Patch events
Other softwareTwilio Authy
Information DisclosureCVE-2024-39891
Why: Known exploited in the wild.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2024-07-23 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 1.7% (77th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v3.1)CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Weakness: CWE-203: Observable Discrepancy
More from this vendor: all Twilio vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Product
n/a(affected)
Description (from the CVE record)#
In the Twilio Authy API, accessed by Authy Android before 25.1.0 and Authy iOS before 26.1.0, an unauthenticated endpoint provided access to certain phone-number data, as exploited in the wild in June 2024. Specifically, the endpoint accepted a stream of requests containing phone numbers, and responded with information about whether each phone number was registered with Authy. (Authy accounts were not compromised, however.)
Quoted from the CVE Program record.