CVE-2024-47864
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 · uneditedhome 5G HR02, Wi-Fi STATION SH-52B, and Wi-Fi STATION SH-54C contain a buffer overflow vulnerability in the hidden debug function. A remote unauthenticated attacker may get the web console of the product down.
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 confidenceA buffer overflow exists in a hidden debug function across three SoftBank mobile router models (home 5G HR02, Wi-Fi STATION SH-52B, and Wi-Fi STATION SH-54C). Remote unauthenticated attackers can trigger this overflow to crash the web management console, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 your router modelLocate the model number on the device label or in the web management console (usually on the status or settings page). Compare against the affected models: home 5G HR02, Wi-Fi STATION SH-52B, and Wi-Fi STATION SH-54C.Affected if The device model matches one of these three models.
-
Check your firmware versionAccess the web management console and navigate to the firmware or system information section (often under Settings, Maintenance, or System). Record the firmware version string displayed.Affected if The installed firmware version is older than the vendor patched version for your model.
-
Verify if remote web management is enabledIn the web management console, look for settings labeled Remote Access, Remote Management, Web Access from WAN, or similar. Check whether remote access is turned ON or allowed from external IP addresses.Affected if Remote web management access from WAN/internet is enabled.
-
Inspect for exposed debug or hidden functionsExamine the web management console URLs and interfaces for any hidden or undocumented debug endpoints, test pages, or diagnostic functions that are not documented in the user manual.Affected if A hidden debug function exists and is accessible without authentication.
-
Check device stability and console accessibilityAttempt to access the web management console normally. Note any crashes, slow responses, or inability to load the interface after potential exploitation attempts.Affected if The web management console crashes or becomes unresponsive.
You are affected if you own one of the three listed SoftBank router models, have an unpatched firmware version, and the remote web management interface is accessible from the internet, allowing unauthenticated attackers to reach the hidden debug function.
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 when available; as an interim control, disable remote web management interfaces or place devices behind a restrictive firewall to limit attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47864 — 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-47864 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