# CVE-2020-36128: Auth bypass in n/a

> Attackers can impersonate payment terminals by spoofing session tokens, bypassing authentication to access the application store.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2mmj-hgqm-x284

## What is CVE-2020-36128?

CVE-2020-36128 is a high-severity authentication bypass vulnerability in n/a, published on 7 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by a token spoofing vulnerability. Each payment terminal has a session token (called X-Terminal-Token) to access the marketplace. This allows the store to identify the terminal and make available the applications distributed by its reseller. By intercepting HTTPS traffic from the application store, it is possible to collect the request responsible for assigning the X-Terminal-Token to the terminal, which makes it possible to craft an X-Terminal-Token pretending to be another device. An attacker can use this behavior to authenticate its own payment terminal in the application store through token impersonation.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Paxtechnology Paxstore.

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

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

## Is CVE-2020-36128 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36126](https://insights.sbomify.com/CVE-2020-36126/): Missing authorization in n/a (high 8.1)
- [CVE-2020-36125](https://insights.sbomify.com/CVE-2020-36125/): Missing authorization in n/a (high 7.1)
- [CVE-2020-36124](https://insights.sbomify.com/CVE-2020-36124/): XML external entity in n/a (medium 6.5)
- [CVE-2020-36127](https://insights.sbomify.com/CVE-2020-36127/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36128 is a high-severity authentication bypass vulnerability in n/a, published on 7 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36128 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-36128/ (Markdown: https://insights.sbomify.com/CVE-2020-36128/index.md)
```

## Sources

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

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