CVE-2014-0356
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 · uneditedThe ZyXEL Wireless N300 NetUSB NBG-419N router with firmware 1.00(BFQ.6)C0 allows remote attackers to execute arbitrary code via shell metacharacters in input to the (1) detectWeather, (2) set_language, (3) SystemCommand, or (4) NTPSyncWithHost function in management.c, or a (5) SET COUNTRY, (6) SET WLAN SSID, (7) SET WLAN CHANNEL, (8) SET WLAN STATUS, or (9) SET WLAN COUNTRY udps command.
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 confidenceCommand injection vulnerability in ZyXEL NBG-419N router firmware 1.00(BFQ.6)C0 allows unauthenticated remote attackers to execute arbitrary OS commands via shell metacharacters passed to multiple CGI functions (detectWeather, set_language, SystemCommand, NTPSyncWithHost) in management.c and certain UDP-based SET commands for WLAN configuration.
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.00\(bfq_6\)c0all 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:M/Au:N/C:C/I:C/A:C
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 router model and firmware versionLog into the router web administration interface (typically at 192.168.1.1) and navigate to Administration > Firmware or System Status page. Record the exact firmware version displayed.Affected if Firmware version is 1.00(BFQ.6)C0 or any version prior to vendor patch
-
Verify management interface network exposureCheck router firewall settings or WAN access configuration. Attempt to access the router login page from an external network (or check NAT/firewall rules that might forward HTTP/HTTPS to the router).Affected if Management interface is accessible from untrusted networks (WAN side) on ports 80/443 or custom management ports
-
Confirm CGI endpoint availabilityInspect the router firmware or web interface for presence of CGI scripts: detectWeather, set_language, SystemCommand, NTPSyncWithHost. These are typically found in management.c within the web server.Affected if Router firmware contains any of these CGI functions and responds to requests
-
Check WLAN configuration UDP exposureExamine router's WLAN settings page and network firewall rules. Identify if UDP-based configuration commands are enabled and reachable on the LAN/WAN interface.Affected if UDP-based SET commands for WLAN configuration are reachable from network
Router is affected if it runs firmware version 1.00(BFQ.6)C0 or unpatched, with vulnerable CGI endpoints or exposed WLAN UDP configuration accessible from an attacker's network.
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 patch from ZyXEL; as interim measure, restrict network access to router management interface to prevent external exploitation.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0356 — 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-2014-0356 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