CVE-2024-39891 - Twilio Authy
AI Vulnerability ContextIn 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...
Overview
A source-backed snapshot of this vulnerability.
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.)
Vulnerability status
How serious this vulnerability is and whether it is known to be exploited.
- CVE ID
- CVE-2024-39891
- Vendor/project
- Twilio
- Product
- Authy
- Vulnerability name
- Twilio Authy Information Disclosure Vulnerability
- Date added
- 2024-07-23
- Due date
- 2024-08-13
- Known ransomware campaign use
- Unknown
- CVSS v3
- 5.3
Exploit context
What the vulnerability is about.
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.)
Source evidence
Original public records and references for this page.
Original source
Original source links
Open the public records and source datasets used for this page.