CVE-2024-39891: Twilio Authy Information Disclosure Vulnerability
CVE-2024-39891 · Severity: critical · CVSS 5.3 · Exploited in the wild · Published 2024-07-23
The Twilio Authy API contained an unauthenticated endpoint that allowed attackers to verify if specific phone numbers were registered with the service. By submitting a stream of phone numbers, unauthorized actors could perform large-scale information disclosure, though Twilio stated that Authy accounts themselves were not compromised.
Quick answers
Is CVE-2024-39891 exploited in the wild?
Yes. CVE-2024-39891 is known to be exploited in the wild, first recorded on 23 July 2024. Treat it as urgent.
How severe is CVE-2024-39891?
Critical severity, with a CVSS score of 5.3, published 23 July 2024.
Which products and versions are affected?
Twilio Authy Android before 25.1.0; Twilio Authy iOS before 26.1.0.
Is there a fix for CVE-2024-39891?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2024-39891 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2024-39891?
Check whether you run Twilio Authy. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Affected products
Twilio Authy Android before 25.1.0
Twilio Authy iOS before 26.1.0
Timeline
2024-06: exploited: Exploited in the wild.
2024-07-02: disclosed
2024-07-23: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.