dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2024-25331

CRITICAL · 9.3 CVSS v3.1 Published 2024-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
No privileges Zero-click

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
DIR-822 Rev. B Firmware v2.02KRB09 and DIR-822-CA Rev. B Firmware v2.03WWb01 suffer from a LAN-Side Unauthenticated Remote Code Execution (RCE) vulnerability elevated from HNAP Stack-Based Buffer Overflow.

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 confidence

Stack-based buffer overflow in the HNAP interface of D-Link DIR-822 Rev. B routers (firmware v2.02KRB09 and v2.03WWb01) allows unauthenticated attackers on the LAN to execute arbitrary code with elevated privileges.

MitigationApply vendor-supplied firmware patch; if unavailable, isolate affected devices on restricted network segments and consider replacement.

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access router admin interface or check device label to confirm hardware revision is 'Rev. B' for D-Link DIR-822
    Affected if Device is not D-Link DIR-822 Rev. B hardware revision
  2. Check firmware version
    Log into router web interface (typically at 192.168.0.1) and navigate to Status or Management page to view firmware version, or use command line if accessible
    Affected if Firmware version matches 2.02KRB09 or 2.03WWb01 exactly
  3. Verify HNAP service is enabled
    Attempt to access HNAP interface by visiting http://[router-ip]/HNAP1/ or check router settings for 'HNAP' or 'Remote Management' settings
    Affected if HNAP interface returns a response or is listed as enabled in router settings
  4. Assess LAN exposure
    Determine if router's LAN interface is accessible to unauthorized users - check if router is on an isolated network segment or shared with untrusted users
    Affected if Untrusted users or devices can reach the router's LAN interface

User is affected if they own a D-Link DIR-822 Rev. B router running firmware version 2.02KRB09 or 2.03WWb01 with the HNAP interface exposed to untrusted LAN users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patch; if unavailable, isolate affected devices on restricted network segments and consider replacement.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25331 — 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-2024-25331 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