dbcve.org
Wzr 300hp FirmwareOperating system · Buffalo

CVE-2022-34840

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to after 2.00 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click Patch available

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 · unedited
Use of hard-coded credentials vulnerability in multiple Buffalo network devices allows a network-adjacent attacker to alter?configuration settings of the device. The affected products/versions are as follows: WZR-300HP firmware Ver. 2.00 and earlier, WZR-450HP firmware Ver. 2.00 and earlier, WZR-600DHP firmware Ver. 2.00 and earlier, WZR-900DHP firmware Ver. 1.15 and earlier, HW-450HP-ZWE firmware Ver. 2.00 and earlier, WZR-450HP-CWT firmware Ver. 2.00 and earlier, WZR-450HP-UB firmware Ver. 2.00 and earlier, WZR-600DHP2 firmware Ver. 1.15 and earlier, and WZR-D1100H firmware Ver. 2.00 and earlier.

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
How this class of weakness works · CWE-798

A password or key is baked into the source or binary, so anyone who obtains the code obtains the credential. These are trivially found once the software is distributed. Remediation means removing the secret, rotating it, and loading credentials from secured configuration at runtime.

General guidance for the hard-coded credentials class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Wzr 300hp FirmwareOperating system
Affected:<= 2.00
Wzr 450hp FirmwareOperating system
Affected:<= 2.00
Wzr 600dhp FirmwareOperating system
Affected:<= 2.00
Wzr 900dhp FirmwareOperating system
Affected:<= 1.15
Hw 450hp Zwe FirmwareOperating system
Affected:<= 2.00
Wzr 450hp Cwt FirmwareOperating system
Affected:<= 2.00
Wzr 450hp Ub FirmwareOperating system
Affected:<= 2.00
Wzr 600dhp2 FirmwareOperating system
Affected:<= 1.15

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.00
Vendor patch www.buffalo.jp →
Recommended fix Moderate confidence

Firmware versions greater than 2.00 (for most models) or greater than 1.15 (for WZR-900DHP and WZR-600DHP2) - consult Buffalo's official release notes

  1. 1. Identify the specific Buffalo router model from the affected product list (WZR-300HP, WZR-450HP, WZR-600DHP, WZR-900DHP, HW-450HP-ZWE, WZR-450HP-CWT, WZR-450HP-UB, WZR-600DHP2, or WZR-D1100H)
  2. 2. Visit the official Buffalo support page at https://www.buffalo.jp/news/detail/20221003-01.html to obtain the firmware update
  3. 3. Download the latest firmware version for your specific model (versions after 2.00 for most models, or after 1.15 for WZR-900DHP, WZR-600DHP2)
  4. 4. Access your router's web management interface
  5. 5. Navigate to the firmware update or administration section
  6. 6. Upload and apply the new firmware version
  7. 7. After reboot, verify the firmware version has been updated
  8. 8. Change any default credentials that may still be present after the update
Caveat Review Buffalo's release notes for any configuration changes or feature modifications that may require reconfiguration after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34840 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34840 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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