CVE-2024-52028
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 R7000P v1.3.3.154 was discovered to contain a stack overflow via the pptp_user_netmask parameter at wiz_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 · moderate confidenceNetgear R7000P firmware v1.3.3.154 contains a stack overflow vulnerability in the wiz_pptp.cgi web interface. The pptp_user_netmask parameter does not properly validate input length before copying to a stack buffer, allowing attackers to trigger a denial of service via crafted POST requests with oversized payload.
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.3.3.154CVSS 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.
-
Check router firmware versionAccess the router web interface at http://192.168.1.1 and navigate to Administration > Firmware Update or check the status page to view the current firmware version. Alternatively, use SNMP or check the /proc/version file via telnet/SSH if enabled.Affected if The installed firmware version is exactly 1.3.3.154
-
Verify PPTP service is enabledLog into the router web interface and navigate to Advanced > VPN > PPTP or similar VPN settings page. Check if PPTP server or VPN passthrough is enabled.Affected if PPTP functionality is enabled on the router
-
Confirm wiz_pptp.cgi is accessibleAttempt to access http://<router_ip>/wiz_pptp.cgi via a browser or curl command. A valid response indicates the vulnerable endpoint exists.Affected if The wiz_pptp.cgi script responds to requests (indicating the vulnerable interface is present)
-
Check management interface exposureDetermine if the router's web management interface is exposed to untrusted networks by reviewing firewall rules, port forwards, or WAN accessibility. Use an external scanner or check NAT/firewall configurations.Affected if The router management interface (port 80/443) is accessible from WAN or untrusted networks
The environment is affected if the Netgear R7000P is running firmware version 1.3.3.154 with PPTP enabled and the wiz_pptp.cgi interface accessible, particularly if the management interface is exposed to untrusted networks.
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; if no update exists, consider disabling PPTP service or deploying compensating network controls such as restricting access to the router's management interface.
- Consultation4.0 h
- Implementation2.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 $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52028 — 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-52028 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