CVE-2024-57680
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 · uneditedAn access control issue in the component form2PortriggerRule.cgi of D-Link 816A2_FWv1.10CNB05_R1B011D88210 allows unauthenticated attackers to set the port trigger of the device 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 confidenceAuthentication bypass in D-Link 816A2 router firmware's form2PortriggerRule.cgi component allows unauthenticated attackers to manipulate port trigger rules via crafted POST requests. The vulnerability stems from missing access controls on this administrative CGI function, enabling unauthorized configuration of network forwarding rules without credentials.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 router modelLocate the device label on the router physical casing or check the admin interface for the model number (D-Link Dir 816)Affected if The device is a D-Link Dir 816 router
-
Determine the firmware versionLog into the router web interface and navigate to the Status or Firmware section to view the installed firmware version; alternatively, check the firmware file name if you have direct access to the firmware binaryAffected if The installed firmware version is 1.10cnb05_r1b011d88210 (exact match)
-
Verify the vulnerable CGI component existsAttempt to access the file form2PortriggerRule.cgi via HTTP POST request to the router; this is typically found under the /cgi-bin/ directory of the web interfaceAffected if The router responds to requests for form2PortriggerRule.cgi without requiring authentication
-
Check network exposure of management interfaceDetermine whether the router web administration interface (port 80 or 443) is reachable from untrusted networks such as the public internet or an unfiltered LAN segmentAffected if The management interface is exposed to networks where untrusted users can reach the router without firewall protection
A user is affected if they are running firmware version 1.10cnb05_r1b011d88210 on a D-Link Dir 816 router with the form2PortriggerRule.cgi component accessible to unauthenticated network users.
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 vendor firmware patch when available; meanwhile, restrict exposure of the device's management interface via firewall rules or network segmentation to prevent external unauthenticated access.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57680 — 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-57680 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