CVE-2024-52015
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 · uneditedNetgear R8500 v1.0.2.160, XR300 v1.0.3.78, R7000P v1.3.3.154, and R6400 v2 1.0.4.128 were discovered to contain a stack overflow via the pptp_user_ip parameter at bsw_pptp.cgi. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted POST request.
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 confidenceStack buffer overflow vulnerability in the pptp_user_ip parameter of bsw_pptp.cgi on multiple Netgear router models (R8500, XR300, R7000P, R6400v2). Attackers can cause Denial of Service via crafted POST requests with oversized input.
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.0.2.160= 1.0.3.78= 1.3.3.154= 1.0.4.128CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label on the router or log into the web admin interface (typically 192.168.1.1) and look for the model number on the status or dashboard page.Affected if Model is R8500, XR300, R7000P, or R6400v2.
-
Check installed firmware versionIn the web admin interface, navigate to the Router Update or Administration page to view the current firmware version. Alternatively, access the router via CLI and run the appropriate version command if available.Affected if Firmware version matches exactly 1.0.2.160 (R8500), 1.0.3.78 (XR300), 1.3.3.154 (R7000P), or 1.0.4.128 (R6400v2).
-
Verify PPTP VPN is enabledIn the web admin interface, look for VPN, PPTP, or Remote Access settings under the Advanced or VPN configuration section. Check if PPTP VPN is turned on or configured.Affected if PPTP VPN functionality is enabled or has been configured on the device.
-
Confirm bsw_pptp.cgi is accessibleAttempt to access the bsw_pptp.cgi endpoint via HTTP or HTTPS POST request to the router. This is typically found at /bsw_pptp.cgi or similar path under the router's web interface.Affected if The bsw_pptp.cgi endpoint responds to requests and accepts the pptp_user_ip parameter.
You are affected if you own one of the listed models AND the firmware version matches exactly AND PPTP VPN is enabled, as the buffer overflow only triggers when the pptp_user_ip parameter in bsw_pptp.cgi receives crafted input.
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 available firmware updates from Netgear for affected models; if no update exists, consider network segmentation or replacing affected devices.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52015 — 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-52015 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