# CVE-2020-24655: Race condition in n/a

> A race condition in the Twilio Authy Android app allows bypassing the PIN lock to approve or deny authentication requests on older devices.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-85p3-g932-hx25

## What is CVE-2020-24655?

CVE-2020-24655 is a medium-severity vulnerability in n/a, published on 10 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A race condition in the Twilio Authy 2-Factor Authentication application before 24.3.7 for Android allows a user to potentially approve/deny an access request prior to unlocking the application with a PIN on older Android devices (effectively bypassing the PIN requirement).

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2020-24655?

It affects 1 product.


Products: Twilio Authy 2-Factor Authentication.

## How do I fix CVE-2020-24655?

No fix has been published for CVE-2020-24655 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-24655 being exploited?

There is no known exploitation of CVE-2020-24655 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24655 and fix it if it is affected.

What it is: CVE-2020-24655 is a medium-severity vulnerability in n/a, published on 10 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24655 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-24655/ (Markdown: https://insights.sbomify.com/CVE-2020-24655/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-24655
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-24655
- OSV: https://osv.dev/vulnerability/CVE-2020-24655

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-24655/
Summaries are generated and may contain mistakes; the official description above is the record.