CVE-2024-39891 Twilio Authy Information Disclosure
An unauthenticated API endpoint in Twilio Authy mobile apps leaked registration status for phone numbers, allowing attackers to identify registered users.
- Exploited in the wild
- Since 23 Jul 2024
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-39891?
CVE-2024-39891 is a medium-severity vulnerability in n/a, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.)
Weakness: CWE-203
Which versions are affected by CVE-2024-39891?
It affects 2 products.
Products include Twilio Authy, Twilio Authy Authenticator.
How do I fix CVE-2024-39891?
No fix has been published for CVE-2024-39891 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 13 Aug 2024.
Is CVE-2024-39891 being exploited?
Yes. Attackers have exploited CVE-2024-39891 in the wild since at least 23 Jul 2024.
Sources
Also known as GHSA-vg5j-h7r8-88x8.