CVE-2018-0636
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 · uneditedAterm HC100RC Ver1.0.1 and earlier allows attacker with administrator rights to execute arbitrary OS commands via FactoryPassword parameter of a certain URL, different URL from CVE-2018-0634.
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 confidenceOS command injection vulnerability in Aterm HC100RC router firmware versions 1.0.1 and earlier. An authenticated attacker with administrator privileges can execute arbitrary OS commands through the FactoryPassword parameter in a specific URL endpoint.
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 data<= 1.0.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 firmware versionAccess the router administration interface and navigate to the system information or firmware version page. Alternatively, check the version displayed on the product label or in the router's status page.Affected if The firmware version is 1.0.1 or earlier.
-
Verify the router modelConfirm the device model is Aterm HC100RC by checking the router label, administration interface, or SNMP lookup.Affected if The device is an Aterm HC100RC model.
-
Determine if the router administration interface is accessibleAttempt to access the router web interface on its default IP address (typically 192.168.0.1 or 192.168.1.1). Check if the login page is reachable over HTTP/HTTPS.Affected if The administrative web interface is reachable from the network.
-
Check for existing administrator sessionsReview router logs or session tables for any active or recent administrator logins. Look for authentication events in the system logs.Affected if Multiple administrator accounts exist or remote administrator access is enabled.
-
Assess network exposure of the management interfaceDetermine if the router web interface is exposed to untrusted networks (WAN/Internet) by checking port forwarding rules, firewall configuration, or by attempting external access.Affected if The administration interface is accessible from WAN or untrusted networks.
The environment is affected if the device is a Nec Aterm HC100RC with firmware version 1.0.1 or earlier, and the router administration interface is accessible to an attacker.
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 update when available; if no patch exists, consider network segmentation or device replacement. Restrict administrator access and monitor for unauthorized administrative sessions.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0636 — 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-0636 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