CVE-2024-27683
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 · uneditedD-Link Go-RT-AC750 GORTAC750_A1_FW_v101b03 contains a stack-based buffer overflow via the function hnap_main. An attacker can send a POST request to trigger the vulnerablilify.
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 confidenceStack-based buffer overflow in the hnap_main function of D-Link Go-RT-AC750 firmware v101b03 allows remote, unauthenticated attackers to execute arbitrary code via a crafted HTTP POST request due to improper bounds checking when handling HN
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= 101b03CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label or login to the router admin interface to confirm the model is D-Link Go-RT-AC750Affected if The device is not a D-Link Go-RT-AC750 unit, then this specific CVE does not apply
-
Check the firmware versionAccess the router admin interface (typically at 192.168.0.1), navigate to Status or System settings, and locate the firmware version fieldAffected if The firmware version is 101b03, indicating the exact affected version
-
Verify HNAP functionality is enabledIn the router admin interface, look for HNAP (Home Network Administration Protocol) settings typically under Advanced or Network settings. Confirm the feature is accessible or enabled.Affected if HNAP is enabled and accessible on the device (the vulnerability exists in the hnap_main function)
-
Confirm network accessibility of the router interfaceAttempt to access the router's web interface from the network segment where the router is deployedAffected if The router admin interface is reachable from a network segment where unauthenticated attackers could send HTTP POST requests
You are affected if you have a D-Link Go-RT-AC750 device running firmware version 101b03 with HNAP functionality enabled and accessible from a network where attackers could send crafted HTTP POST requests.
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 dataThis is an end-of-life device with no vendor patch available; mitigate by isolating the device behind a firewall, disabling WAN access, or replacing with a supported router model.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27683 — 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-27683 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