CVE-2018-0631
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 W300P Ver1.0.13 and earlier allows attacker with administrator rights to execute arbitrary OS commands via targetAPSsid 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 confidenceThis is an authenticated OS command injection vulnerability in Aterm W300P router firmware versions 1.0.13 and earlier. An attacker with administrator credentials can execute arbitrary operating system commands by injecting them into the targetAPSsid parameter, likely through insufficient input sanitization before passing the value to a system shell call.
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.13CVSS 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 modelAccess the router web administration interface or check the device label. Look for 'Aterm W300P' or 'W300P' model designation.Affected if The device is not an Aterm W300P router.
-
Locate the firmware versionIn the router web interface, navigate to the status or system information page. The firmware version is typically displayed under 'Firmware Version' or 'Version' in the administrative console.Affected if The firmware version cannot be determined or the interface is inaccessible.
-
Compare firmware version to affected rangeCheck if the installed firmware version is 1.0.13 or any version lower than 1.0.13. Note that some interfaces may display only the major version number.Affected if The firmware version is 1.0.13 or lower.
-
Verify remote management is enabledIn the router web interface, check the 'Remote Management' or 'Administration' settings. Confirm whether the web-based administration interface is accessible from the WAN side or LAN side.Affected if The web administration interface is enabled and accessible, making the injected parameter reachable.
-
Assess credential accessibilityReview whether default or weak administrator credentials are in use, or if credentials could be obtained through other means such as sniffing on an unencrypted local network.Affected if Administrator credentials are known or easily guessable, enabling the authenticated attack vector.
A user is affected if the device is an Aterm W300P router running firmware version 1.0.13 or lower with its web administration interface accessible and administrator credentials available 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 dataUpdate the Aterm W300P firmware to a version newer than 1.0.13. If the device has reached end-of-life and no patched firmware is available, replace the device with a currently supported router model.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0631 — 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-0631 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