CVE-2024-23486
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 · uneditedPlaintext storage of a password issue exists in BUFFALO wireless LAN routers, which may allow a network-adjacent unauthenticated attacker with access to the product's login page may obtain configured credentials.
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 confidenceBUFFALO wireless LAN routers store passwords in plaintext, allowing a network-adjacent unauthenticated attacker with access to the device's login page to retrieve configured credentials. The critical CVSS score reflects the ease of exploitation combined with complete credential disclosure.
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.07< 1.07< 1.11< 1.11CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Buffalo router modelAccess the device admin interface or check the device label to confirm the exact model number (Wsr-2533dhp, Wsr-2533dhpl, Wsr-2533dhp2, or Wsr-A2533dhp2)Affected if The device is one of these four models and the vulnerability applies to that model
-
Check the installed firmware versionLog into the router admin panel and navigate to the System or Status section to view the firmware version, or check via telnet/SSH if enabledAffected if The firmware version is below 1.07 for Wsr-2533dhp or Wsr-2533dhpl, or below 1.11 for Wsr-2533dhp2 or Wsr-A2533dhp2
-
Verify web interface accessibilityAttempt to access the router login page from a network-adjacent position using the device IP addressAffected if The login page is reachable from an untrusted network segment, allowing a network-adjacent attacker to reach it
-
Inspect for credential exposure riskReview any accessible configuration backups, diagnostic logs, or API endpoints that may expose stored credentials in plaintextAffected if Configuration data or logs contain plaintext passwords rather than hashed values
You are affected if you have a Buffalo Wsr-2533dhp, Wsr-2533dhpl, Wsr-2533dhp2, or Wsr-A2533dhp2 device running firmware below the threshold (1.07 or 1.11 depending on model) and the router login page is accessible to network-adjacent 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 data1.071.11
Apply vendor firmware updates when available; immediately change default/admin passwords on affected devices and consider network segmentation to limit adjacent attacker access until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23486 — 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-2024-23486 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