CVE-2018-16194
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 WF1200CR and Aterm WG1200CR (Aterm WF1200CR firmware Ver1.1.1 and earlier, Aterm WG1200CR firmware Ver1.0.1 and earlier) allows authenticated attackers to execute arbitrary OS commands via unspecified vectors.
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 OS command injection vulnerability in NEC Aterm WF1200CR and WG1200CR routers. An attacker with valid authentication credentials can execute arbitrary operating system commands on the device through unspecified vectors, likely by injecting shell metacharacters into web interface parameters.
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.1.1<= 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 router modelLocate the device label on the router physical casing or access the administrative web interface and look for the model name displayed on the login page or status sectionAffected if The device is not a NEC Aterm WF1200CR or WG1200CR router (other models are not affected by this specific CVE)
-
Check the WF1200CR firmware versionLog into the web admin interface, navigate to the firmware or status page, and record the firmware version number displayedAffected if The firmware version is 1.1.1 or earlier (versions 1.1.2 and later are patched)
-
Check the WG1200CR firmware versionLog into the web admin interface, navigate to the firmware or status page, and record the firmware version number displayedAffected if The firmware version is 1.0.1 or earlier (versions 1.0.2 and later are patched)
-
Verify web interface accessibilityAttempt to access the router web administrative interface from a browser using the default gateway IP address (commonly 192.168.0.1 or 192.168.1.1)Affected if The web interface is exposed to untrusted networks (this command injection can be exploited by anyone with valid credentials who can reach the interface)
A user is affected if they have a NEC Aterm WF1200CR router running firmware 1.1.1 or earlier, or a WG1200CR router running firmware 1.0.1 or earlier, and the administrative web interface is accessible to them or potential attackers.
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-supplied firmware updates (WF1200CR Ver1.1.2 or later, WG1200CR Ver1.0.2 or later). If updates unavailable, restrict administrative access to trusted IP addresses only and change default credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16194 — 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-16194 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