# CVE-2020-28044: Missing authorization in n/a

> An attacker with physical access can boot a PAX POS device into management mode to read and modify files with elevated permissions.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x4q6-fxmg-xgcv

## What is CVE-2020-28044?

CVE-2020-28044 is a medium-severity missing authorization vulnerability in n/a, published on 1 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker with physical access to a PAX Point Of Sale device with ProlinOS through 2.4.161.8859R can boot it in management mode, enable the XCB service, and then list, read, create, and overwrite files with MAINAPP permissions.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Pax Prolinos.

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

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

## Is CVE-2020-28044 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28045](https://insights.sbomify.com/CVE-2020-28045/): Security feature bypass in n/a (high 7.8)
- [CVE-2020-28046](https://insights.sbomify.com/CVE-2020-28046/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28044 is a medium-severity missing authorization vulnerability in n/a, published on 1 Nov 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-28044 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-28044/ (Markdown: https://insights.sbomify.com/CVE-2020-28044/index.md)
```

## Sources

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

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