CVE-2022-43466
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 · uneditedOS command injection vulnerability in Buffalo network devices allows a network-adjacent attacker with an administrative privilege to execute an arbitrary OS command if a specially crafted request is sent to a specific CGI program.
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 · moderate confidenceOS command injection vulnerability in Buffalo network devices allows a network-adjacent attacker with administrative privileges to execute arbitrary OS commands via specially crafted requests to a specific CGI program.
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.26= 1.25<= 1.22<= 1.22<= 1.26<= 1.26<= 1.03<= 1.07CVSS 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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 Buffalo device modelAccess the router web interface or check the device label to confirm the exact model number (e.g., Wsr 3200ax4s, Wsr 2533dhp3, etc.)Affected if The device model is one of: Wsr 3200ax4s, Wsr 3200ax4b, Wsr 2533dhp2, Wsr A2533dhp2, Wsr 2533dhp3, Wsr A2533dhp3, Wsr 2533dhpl2, or Wsr 2533dhpls
-
Check installed firmware versionLog into the router admin panel and navigate to the system or status page to view the firmware version, or use the command line and check /etc/version or the kernel command line if accessibleAffected if The firmware version falls within the affected ranges: Wsr 3200ax4s <= 1.26, Wsr 3200ax4b = 1.25, Wsr 2533dhp2 <= 1.22, Wsr A2533dhp2 <= 1.22, Wsr 2533dhp3 <= 1.26, Wsr A2533dhp3 <= 1.26, Wsr 2533dhpl2 <= 1.03, Wsr 2533dhpls <= 1.07
-
Verify web interface accessibilityAttempt to access the router web interface via HTTP/HTTPS on the local network (typically at the default gateway IP address)Affected if The administrative web interface is reachable from an untrusted network segment
-
Check for evidence of command injectionReview web server logs or CGI application logs for unusual or malformed requests to the vulnerable CGI endpoint, or check for unexpected processes or shell execution patternsAffected if Logs show suspicious requests containing shell metacharacters (e.g., ; | & $ `) or unexpected command execution traces
-
Confirm administrative access statusVerify whether default administrative credentials are still in use, or check for unauthorized admin accounts or session hijacking indicatorsAffected if Default credentials are unchanged, or there are signs of unauthorized administrative access
-
Inspect network access controlsReview router firewall or access control settings to determine if the administrative interface is exposed to untrusted networksAffected if The administrative web interface (CGI programs) is accessible from wide-area network (WAN) or untrusted LAN segments
The device is affected if it is a Buffalo Wsr model matching the listed variants and runs a firmware version within the specified vulnerable ranges, with the administrative CGI interface accessible to the 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 dataApply vendor-supplied firmware patches when available; restrict administrative access to trusted networks and implement strict input validation on CGI programs to prevent command injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43466 — 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-2022-43466 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