# CVE-2021-40521: Code injection in n/a

> Remote attackers can execute arbitrary code on Airangel HSMX Gateway devices, compromising the network infrastructure.

- **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:** 10 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fw83-hp96-3f54

## What is CVE-2021-40521?

CVE-2021-40521 is a critical code injection vulnerability in n/a, published on 10 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Airangel HSMX Gateway devices through 5.2.04 allow Remote Code Execution.

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

It affects 5 products.


Products: Airangel Hsmx-App-1000 Firmware, Airangel Hsmx-App-100 Firmware, Airangel Hsmx-App-20000 Firmware, Airangel Hsmx-App-25 Firmware, Airangel Hsmx-App-5000 Firmware.

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

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

## Is CVE-2021-40521 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-40519](https://insights.sbomify.com/CVE-2021-40519/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2021-40520](https://insights.sbomify.com/CVE-2021-40520/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2021-40518](https://insights.sbomify.com/CVE-2021-40518/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2021-40517](https://insights.sbomify.com/CVE-2021-40517/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-40521 is a critical code injection vulnerability in n/a, published on 10 Nov 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-40521 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-2021-40521/ (Markdown: https://insights.sbomify.com/CVE-2021-40521/index.md)
```

## Sources

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

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