CVE-2023-3333
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 · uneditedImproper Neutralization of Special Elements used in an OS Command vulnerability in NEC Corporation Aterm WG2600HP2, WG2600HP, WG2200HP, WG1800HP2, WG1800HP, WG1400HP, WG600HP, WG300HP, WF300HP, WR9500N, WR9300N, WR8750N, WR8700N, WR8600N, WR8370N, WR8175N and WR8170N all versions allows a attacker to execute an arbitrary OS command with the root privilege, after obtaining a high privilege exploiting CVE-2023-3330 and CVE-2023-3331 vulnerabilities.
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 NEC Aterm router firmware (multiple models WG2600HP2, WG2600HP, WG2200HP, WG1800HP2, WG1800HP, WG1400HP, WG600HP, WG300HP, WF300HP, WR9500N, WR9300N, WR8750N, WR8700N, WR8600N, WR8370N, WR8175N, WR8170N) allows authenticated attackers to execute arbitrary OS commands with root privileges, but requires prior privilege escalation via CVE-2023-3330 and CVE-2023-3331.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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 router model and firmware versionAccess the router administrative web interface and check the status or firmware information page, or log in via SSH/Telnet if enabled and run 'firmware info' or check the web UI for the exact model number and firmware version displayedAffected if The model number matches one of: WG2600HP2, WG2600HP, WG2200HP, WG1800HP2, WG1800HP, WG1400HP, WG300HP, WF300HP, and the firmware version is any version (all versions are affected)
-
Verify administrative interface accessibilityCheck if the router web administration interface (HTTP/HTTPS on ports 80/443 or vendor default ports) is reachable from untrusted networks by scanning external IP or reviewing firewall rulesAffected if The administrative interface is exposed to the internet or to untrusted network segments without proper access controls
-
Confirm presence of CVE-2023-3330 and CVE-2023-3331Check for signs of prior privilege escalation exploitation: review system logs for suspicious commands, unexpected administrative accounts, or modified configuration files. These are prerequisites - CVE-2023-3333 cannot be exploited without first exploiting one of them.Affected if Evidence exists of compromise from CVE-2023-3330 (authentication bypass) or CVE-2023-3331 (privilege escalation), or if the device was not patched after disclosure of those vulnerabilities
-
Review for indicators of compromiseExamine router logs for unexpected command execution, unusual scheduled tasks, or outbound connections to unknown IP addresses. Check for new user accounts or modified administrative credentials.Affected if Any unauthorized commands, scripts, or network connections are found in logs or system configuration
A user is affected if they run one of the listed Aterm models with any firmware version, have the admin interface exposed to untrusted networks, and either have been previously compromised by CVE-2023-3330/CVE-2023-3331 or have not applied vendor patches for those prerequisite vulnerabilities.
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 updates for all three CVEs (CVE-2023-3330, CVE-2023-3331, CVE-2023-3333); if patches unavailable, restrict administrative interface access to trusted networks or implement compensating network segmentation controls.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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 $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3333 — 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-2023-3333 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