# CVE-2021-37123: Auth bypass in Hero-CT060

> Improper authentication in Hero-CT060 allows attackers to perform unauthorized operations by bypassing identity validation checks.

- **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:** 11 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6p74-hfr6-rgm3

## What is CVE-2021-37123?

CVE-2021-37123 is a critical authentication bypass vulnerability in Hero-CT060, published on 11 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is an improper authentication vulnerability in Hero-CT060 before 1.0.0.200. The vulnerability is due to that when an user wants to do certain operation, the software does not insufficiently validate the user's identity. Successful exploit could allow the attacker to do certain operations which the user are supposed not to do.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-37123?

It affects 1 product.


Products: Huawei Hero-Ct060 Firmware.

## How do I fix CVE-2021-37123?

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

## Is CVE-2021-37123 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37123 and fix it if it is affected.

What it is: CVE-2021-37123 is a critical authentication bypass vulnerability in Hero-CT060, published on 11 Oct 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-2021-37123 in the wild and no public exploit code.

Affected product: Hero-CT060. 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-2021-37123/ (Markdown: https://insights.sbomify.com/CVE-2021-37123/index.md)
```

## Sources

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

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