Twilio Authy on Android/iOS API improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Twilio Authy on Android/iOS and classified as critical. Affected by this issue is some unknown functionality of the component API. Such manipulation leads to improper authentication. This vulnerability is referenced as CVE-2024-39891. It is possible to launch the attack remotely. Furthermore, an exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Twilio Authy on Android/iOS (the affected version is unknown). It has been rated as critical. Affected by this issue is an unknown code of the component API. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality. CVE summarizes:
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.)
This vulnerability is handled as CVE-2024-39891 since 07/02/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but an exploit is available.
It is declared as attacked. This issue was added on 07/23/2024 to the CISA Known Exploited Vulnerabilities Catalog with a due date of 08/13/2024:
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.Upgrading eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (MITRE): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
07/02/2024 🔍07/02/2024 🔍
07/02/2024 🔍
11/06/2025 🔍
Sources
Status: ConfirmedCVE: CVE-2024-39891 (🔍)
GCVE (CVE): GCVE-0-2024-39891
GCVE (VulDB): GCVE-100-270260
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 07/02/2024 20:59Updated: 11/06/2025 22:28
Changes: 07/02/2024 20:59 (62), 07/23/2024 18:38 (13), 07/24/2024 03:35 (1), 07/24/2024 17:48 (9), 09/09/2024 22:30 (2), 11/06/2025 22:28 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.