dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2024-12147

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was found in Netgear R6900 1.0.1.26_1.0.20. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file upgrade_check.cgi of the component HTTP Header Handler. The manipulation of the argument Content-Length leads to buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

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

Buffer overflow vulnerability in Netgear R6900 router firmware (1.0.1.26_1.0.20) allows remote attackers to overflow the Content-Length HTTP header argument when processing upgrade_check.cgi, potentially enabling arbitrary code execution in the HTTP Header Handler component.

MitigationThis affects an end-of-life unsupported product. Primary mitigation is to replace with a currently supported router. If continued use is unavoidable, restrict network access to the device via firewall to minimize exposure to remote attackers.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm Netgear R6900 model
    Check the product label on the router or log into the admin interface (typically at 192.168.1.1) and look for the model number in the device info or status page
    Affected if Device is NOT a Netgear R6900 (not affected) or IS a Netgear R6900 (potentially affected)
  2. Identify installed firmware version
    In the router admin interface, go to Advanced > Administration > Firmware Update or similar, or check the status/dashboard page for the firmware version number
    Affected if Firmware version is 1.0.1.26_1.0.20 (definitely affected) or falls within or below this version range (potentially affected)
  3. Verify if remote management is enabled
    In the admin interface, look under Advanced > Administration > Remote Management or similar setting. Check if 'Enable Remote Management' or 'Allow remote access' is turned ON
    Affected if Remote management is enabled and the device is directly accessible from the internet (highly vulnerable to remote exploitation)
  4. Check network exposure
    From an external network, attempt to access the router login page using the public IP address, or check router firewall/NAT settings to see if inbound HTTP/HTTPS ports (80/443) are forwarded or DMZ is configured
    Affected if The router admin interface is reachable from the internet via port 80/443 or similar (vulnerable to remote attack)
  5. Confirm upgrade_check.cgi endpoint exists
    Access the router's web interface or use a tool to make an HTTP request to http://[router-ip]/upgrade_check.cgi and observe the response (requires authentication or may return error)
    Affected if The endpoint responds (indicating it exists and could be targeted for the buffer overflow)

The device is affected if it is a Netgear R6900 running firmware version 1.0.1.26_1.0.20 or earlier, especially if remote management is enabled or the admin interface is exposed to the internet.

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

This affects an end-of-life unsupported product. Primary mitigation is to replace with a currently supported router. If continued use is unavoidable, restrict network access to the device via firewall to minimize exposure to remote attackers.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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