Threats / Sunhillo / CVE-2021-36380
CVE-2021-36380
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Sunhillo SureLine vulnerability
Sunhillo SureLine contains an OS command injection vulnerability in the network diagnostics CGI endpoint that allows attackers to execute arbitrary commands via shell metacharacters, enabling denial-of-service or network persistence.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject OS commands through the ipAddr or dnsAddr parameters in /cgi/networkDiag.cgi to disrupt service availability or establish persistent access to the affected device for lateral network movement.
CISA KEV Yes · 2024-03-054EPSS 0.97599 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3Exploit Public PoC / detection · nuclei template12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
677 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-03-05).
Probability (EPSS)
EPSS 0.97599 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Sunhillo, SureLine. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 935 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTTP request with shell metacharacters in the ipAddr or dnsAddr parameter to the networkDiag.cgi endpoint.
Business
The organization's network diagnostic infrastructure becomes a vector for command execution and potential compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary OS commands on the SureLine device with the privileges of the web service process.
Business
Attackers gain a foothold to move laterally through the network and establish persistence mechanisms.
3
Lateral reach — past segmentation narrative 3
Attacker
I trigger resource exhaustion or crash the service through denial-of-service payloads.
Business
Critical network diagnostic capabilities become unavailable, disrupting operational visibility and incident response.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05