# CVE-2023-27197: Privilege escalation in n/a

> An attacker with shell access can gain root privileges on PAX A930 devices by exploiting an exported function in a shared library.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/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:** 5 Jul 2023
- **Updated:** 5 Dec 2024
- **Also known as:** GHSA-5m9p-83f2-h69j

## What is CVE-2023-27197?

CVE-2023-27197 is a medium-severity vulnerability in n/a, published on 5 Jul 2023. 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.5.02_20220722 can allow an attacker to gain root access by running a crafted binary leveraging an exported function from a shared library. The attacker must have shell access to the device in order to exploit this vulnerability.

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

It affects 1 product.


Products: Paxtechnology Pax A930 Firmware.

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

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

## Is CVE-2023-27197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27198](https://insights.sbomify.com/CVE-2023-27198/): Command injection in n/a (medium 6.8)
- [CVE-2023-27199](https://insights.sbomify.com/CVE-2023-27199/): Security feature bypass in n/a (medium 6.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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