CVE-2018-0639
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 tools_firmware.cgi date parameter, time parameter, and offset parameter.
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 confidenceAuthenticated OS command injection vulnerability in Aterm HC100RC router firmware. The tools_firmware.cgi script does not properly sanitize the date, time, and offset parameters, allowing an authenticated administrator to execute arbitrary operating system commands on the device.
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 modelCheck the device label or access the router web interface and look for the model name (Aterm HC100RC)Affected if Device is not an Aterm HC100RC router, then not affected
-
Check the installed firmware versionAccess the router admin panel, typically at 192.168.0.1 or 192.168.10.1, and navigate to the firmware or status page to view the firmware version numberAffected if Firmware version is greater than 1.0.1, then not affected; versions 1.0.1 and below are affected
-
Confirm web management interface is accessibleVerify the router HTTP/HTTPS management interface is reachable on the local networkAffected if Web interface is not accessible or has been disabled, the attack surface is reduced but the vulnerability still exists in the firmware if versions match
-
Verify tools_firmware.cgi existsAttempt to access the CGI script directly via browser or curl: http://<router-ip>/cgi-bin/tools_firmware.cgiAffected if Script returns a 404 or is not found, the specific vulnerable endpoint may not be present; if it responds, the vulnerable script is present
-
Check if default or weak credentials are in useAttempt to log into the router admin panel using default credentials (consult Aterm documentation for default username/password, often admin/admin or admin/password)Affected if Authentication is not required or uses default credentials, exploitation is possible; however, the vulnerability is still present in the firmware regardless of authentication status for detection purposes
The device is affected if it is an Aterm HC100RC router running firmware version 1.0.1 or lower, regardless of whether the web interface is currently accessible or uses default credentials.
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 if available. If no update exists, implement strict input validation on all CGI parameters and replace unsafe system call functions with parameterized alternatives to prevent command injection.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0639 — 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-0639 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