CVE-2024-13105
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 · uneditedA vulnerability has been found in D-Link DIR-816 A2 1.10CNB05_R1B011D88210 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /goform/form2Dhcpd.cgi of the component DHCPD Setting Handler. The manipulation leads to improper access controls. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceThe D-Link DIR-816 A2 router firmware 1.10CNB05_R1B011D88210 contains an improper access control vulnerability in the DHCPD Setting Handler component (/goform/form2Dhcpd.cgi). This allows remote attackers to manipulate DHCP server settings without authentication due to missing or inadequate authorization checks.
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.10cnb05_r1b011d88210CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 router label or access the web interface and look for the model number (DIR-816 A2) in the status or system information pageAffected if Device is not a D-Link DIR-816 A2 - not affected
-
Check the firmware versionAccess the router web interface, navigate to Status or System settings, and locate the firmware version information. Compare it exactly to 1.10CNB05_R1B011D88210Affected if Firmware version is exactly 1.10CNB05_R1B011D88210 - likely affected
-
Verify remote management accessibilityAttempt to access the router login page from an external network (outside your local LAN) using the public IP address, or check router firewall/NAT settings for port forwarding to port 80/443 from WANAffected if Remote management interface (web UI on port 80/443) is accessible from the internet - vulnerable exposure exists
-
Test the vulnerable endpoint exposureFrom an external network, attempt to access http://[public-ip]/goform/form2Dhcpd.cgi or check if the router responds to this path without authenticationAffected if The /goform/form2Dhcpd.cgi endpoint is reachable from WAN without authentication - direct exposure confirmed
If the device is a DIR-816 A2 running firmware 1.10CNB05_R1B011D88210 and its management interface or the specific /goform/form2Dhcpd.cgi endpoint is accessible from the internet, the environment is affected by this vulnerability.
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 D-Link; if no update exists, disable remote management interface access from the internet and place the device behind a properly configured firewall to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13105 — 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-13105 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