# CVE-2021-36380: Sunhillo SureLine OS Command Injection Vulnerablity

> Unauthenticated attackers can execute arbitrary OS commands via shell metacharacters in network diagnostic parameters on Sunhillo SureLine devices.

- **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:** Yes, since 5 Mar 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2021
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-76jq-2jjj-76w4

## What is CVE-2021-36380?

CVE-2021-36380 is a critical command injection vulnerability in n/a, published on 13 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sunhillo SureLine before 8.7.0.1.1 allows Unauthenticated OS Command Injection via shell metacharacters in ipAddr or dnsAddr /cgi/networkDiag.cgi.

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

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

It affects 1 product.


Products: Sunhillo Sureline.

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

No fix has been published for CVE-2021-36380 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Mar 2024.

## Is CVE-2021-36380 being exploited?

Yes. Attackers have exploited CVE-2021-36380 in the wild since at least 5 Mar 2024.

Public exploit code:

- Sunhillo SureLine <8.7.0.1.1 - Unauthenticated OS Command Injection (nuclei): http/cves/2021/CVE-2021-36380.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2021-36380 is a critical command injection vulnerability in n/a, published on 13 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-36380 in the wild since at least 5 Mar 2024.

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-36380/ (Markdown: https://insights.sbomify.com/CVE-2021-36380/index.md)
```

## Sources

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

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