# CVE-2021-37028: Command injection in EchoLife HG8045Q

> Administrators can execute arbitrary commands on Huawei HG8045Q devices if the CLI is enabled, requiring a patch to mitigate.

- **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:** 13 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hghr-6gj9-99m4

## What is CVE-2021-37028?

CVE-2021-37028 is a medium-severity command injection vulnerability in EchoLife HG8045Q, published on 13 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a command injection vulnerability in the HG8045Q product. When the command-line interface is enabled, which is disabled by default, attackers with administrator privilege could execute part of commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Huawei Hg8045q Firmware.

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

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

## Is CVE-2021-37028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-37028 is a medium-severity command injection vulnerability in EchoLife HG8045Q, published on 13 Aug 2021. 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-2021-37028 in the wild and no public exploit code.

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

## Sources

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

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