CVE-2024-39891

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.)

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.)

En la API de Twilio Authy, a la que accedían Authy Android antes de la versión 25.1.0 y Authy iOS antes de la versión 26.1.0, un endpoint no autenticado proporcionaba acceso a determinados datos de números de teléfono, como se explotó en junio de 2024. En concreto, el endpoint aceptaba un flujo de solicitudes que contenían números de teléfono y respondía con información sobre si cada número de teléfono estaba registrado en Authy. (Sin embargo, las cuentas de Authy no se vieron comprometidas).