CVE-2018-10562
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered on Dasan GPON home routers. Command Injection can occur via the dest_host parameter in a diag_action=ping request to a GponForm/diag_Form URI. Because the router saves ping results in /tmp and transmits them to the user when the user revisits /diag.html, it's quite simple to execute commands and retrieve their output.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDasan GPON home routers contain a pre-authentication command injection vulnerability in the web interface. The diag_action=ping parameter dest_host in the GponForm/diag_Form URI allows attackers to inject arbitrary OS commands. Ping results are stored in /tmp and returned when users access /diag.html, enabling attackers to execute commands and retrieve output without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router's web interface or check the device label/metadata to confirm the manufacturer and model. Look for 'Dasan', 'GPON', or 'Dasannetworks' branding.Affected if The device is a Dasan GPON home router from any version.
-
Confirm firmware versionLog into the router's admin interface and navigate to the status or system information page to view the installed firmware version.Affected if The firmware is any version from this vendor, as all versions are affected.
-
Check web management accessibilityDetermine if the router's web interface (port 80 or 443) is accessible from untrusted networks such as the internet or guest networks. Use external scanning tools or review firewall rules.Affected if The web management interface is exposed to untrusted networks, increasing exploitation risk.
-
Verify vulnerable endpoint existsSend a request to the URI /GponForm/diag_Form with the parameter diag_action=ping and a test value in dest_host (such as a simple ping to an internal IP) to confirm the endpoint responds.Affected if The endpoint /GponForm/diag_Form is accessible and processes the dest_host parameter, indicating the command injection vulnerability is present.
You are affected if you have a Dasan GPON router with an accessible web management interface that exposes the /GponForm/diag_Form endpoint handling ping diagnostics.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware patches if available; if no patch exists, block external access to the router's web management interface via firewall or place the device behind a NAT gateway to prevent unauthenticated attackers from reaching the vulnerable endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-10562 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data