# CVE-2022-26579: Security feature bypass in n/a

> A root-privileged attacker with shell access can bypass signature verification to install unsigned packages on PAX A930 devices.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2022
- **Updated:** 27 Oct 2024
- **Also known as:** GHSA-f22x-pp6j-8h8j

## What is CVE-2022-26579?

CVE-2022-26579 is a medium-severity vulnerability in n/a, published on 16 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PAX A930 device with PayDroid_7.1.1_Virgo_V04.3.26T1_20210419 can allow a root privileged attacker to install unsigned packages. The attacker must have shell access to the device and gain root privileges in order to exploit this vulnerability.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2022-26579?

It affects 1 product.


Products: Paxtechnology Paydroid.

## How do I fix CVE-2022-26579?

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

## Is CVE-2022-26579 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-42136](https://insights.sbomify.com/CVE-2023-42136/): Command injection in POS terminals (high 7.8)
- [CVE-2023-42137](https://insights.sbomify.com/CVE-2023-42137/): Path traversal in POS terminals (high 7.8)
- [CVE-2022-26582](https://insights.sbomify.com/CVE-2022-26582/): Command injection in n/a (high 7.8)
- [CVE-2023-4818](https://insights.sbomify.com/CVE-2023-4818/): Security feature bypass in A920 (high 7.6)
- [CVE-2023-42134](https://insights.sbomify.com/CVE-2023-42134/): Code injection in POS terminals (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26579 and fix it if it is affected.

What it is: CVE-2022-26579 is a medium-severity vulnerability in n/a, published on 16 Dec 2022. 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-2022-26579 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-2022-26579/ (Markdown: https://insights.sbomify.com/CVE-2022-26579/index.md)
```

## Sources

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

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