# CVE-2023-26980: Race condition in n/a

> Attackers can bypass payment software to boot directly to Android via a race condition, though the vendor disputes feasibility.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q7gw-cx2f-mh8f

## What is CVE-2023-26980?

CVE-2023-26980 is a high-severity vulnerability in n/a, published on 14 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PAX Technology PAX A920 Pro PayDroid 8.1suffers from a Race Condition vulnerability, which allows attackers to bypass the payment software and force the OS to boot directly to Android during the boot process. NOTE: the vendor disputes this because the attack is not feasible: the home launcher will be loaded before any user applications.

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

## Which versions are affected by CVE-2023-26980?

It affects 1 product.


Products: Pax Paydroid.

## How do I fix CVE-2023-26980?

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

## Is CVE-2023-26980 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26980 and fix it if it is affected.

What it is: CVE-2023-26980 is a high-severity vulnerability in n/a, published on 14 Apr 2023. 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-2023-26980 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-2023-26980/ (Markdown: https://insights.sbomify.com/CVE-2023-26980/index.md)
```

## Sources

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

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