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

> Unauthenticated attackers can access Xiongmai DVR devices via an open Telnet port, enabling remote code execution and full device control.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cxgc-jm76-g3rq

## What is CVE-2020-22253?

CVE-2020-22253 is a critical authentication bypass vulnerability in n/a, published on 6 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xiongmai Technology Co devices AHB7008T-MH-V2, AHB7804R-ELS, AHB7804R-MH-V2, AHB7808R-MS-V2, AHB7808R-MS, AHB7808T-MS-V2, AHB7804R-LMS, and HI3518E_50H10L_S39 were all discovered to have port 9530 open which allows unauthenticated attackers to make arbitrary Telnet connections with the victim device.

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

It affects 8 products.


Products: Xiongmaitech Ahb7008t-Mh-V2 Firmware, Xiongmaitech Ahb7804r-Els Firmware, Xiongmaitech Ahb7804r-Lms Firmware, Xiongmaitech Ahb7804r-Mh-V2 Firmware, Xiongmaitech Ahb7808r-Ms-V2 Firmware, Xiongmaitech Ahb7808r-Ms Firmware, Xiongmaitech Ahb7808t-Ms-V2 Firmware, Xiongmaitech Hi3518e 50h10l S39 Firmware.

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

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

## Is CVE-2020-22253 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41506](https://insights.sbomify.com/CVE-2021-41506/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-22253 is a critical authentication bypass vulnerability in n/a, published on 6 Apr 2022. 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-22253 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-22253/ (Markdown: https://insights.sbomify.com/CVE-2020-22253/index.md)
```

## Sources

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

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