dbcve.org
Dir 816 FirmwareOperating system · Dlink

CVE-2024-57679

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An access control issue in the component form2RepeaterSetup.cgi of D-Link 816A2_FWv1.10CNB05_R1B011D88210 allows unauthenticated attackers to set the 2.4G and 5G repeater service 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 confidence

D-Link 816A2 router firmware v1.10CNB05_R1B011D88210 contains an access control vulnerability in the form2RepeaterSetup.cgi component. Unauthenticated attackers can send crafted POST requests to modify 2.4GHz and 5GHz wireless repeater service settings, bypassing authentication mechanisms intended to protect these configuration functions.

MitigationApply vendor-supplied firmware patches when available; until then, restrict network access to the device's management interface via firewall rules or disable remote administration to prevent unauthenticated attackers from reaching the vulnerable CGI component.

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
Dir 816 FirmwareOperating system
Affected:= 1.10cnb05_r1b011d88210

CVSS 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device firmware version
    Access the router admin panel or check the system information page (typically at /Status.asp or /RouterConfig.asp) to view the firmware version string. Alternatively, check the downloaded firmware file name or header if you have access to the firmware binary.
    Affected if The firmware version displays as 1.10cnb05_r1b011d88210, confirming the exact vulnerable version.
  2. Verify the device model
    Confirm the router model is D-Link DIR-816A2 by checking the device label, admin panel status page, or SNMP/network discovery output.
    Affected if The device is a D-Link DIR-816A2 running the affected firmware version.
  3. Check network exposure of the web interface
    Determine if the router's HTTP/HTTPS management interface is accessible from untrusted networks (WAN/Internet) by attempting to access the router's IP from an external network or reviewing firewall rules that permit inbound traffic to ports 80/443.
    Affected if The router's admin interface is exposed to untrusted networks, allowing unauthenticated attackers to reach the device.
  4. Test for unauthenticated access to form2RepeaterSetup.cgi
    Send a crafted POST request to http://[router-ip]/form2RepeaterSetup.cgi without providing authentication cookies or credentials. Observe if the server processes the request or returns a configuration response.
    Affected if The endpoint responds without requiring authentication, indicating the access control bypass is present.
  5. Verify if wireless repeater functionality is enabled
    Check the router's wireless settings page (such as Repeater/Bridge mode settings) to determine if the 2.4GHz or 5GHz repeater service is currently configured or active.
    Affected if Repeater mode is enabled and the device is running the vulnerable firmware, making it a target for configuration tampering.

A user is affected if their D-Link DIR-816A2 router runs firmware version 1.10cnb05_r1b011d88210 and the management interface is network-accessible, allowing unauthenticated attackers to modify repeater settings via form2RepeaterSetup.cgi.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches when available; until then, restrict network access to the device's management interface via firewall rules or disable remote administration to prevent unauthenticated attackers from reaching the vulnerable CGI component.

Fix this in Dir 816 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57679 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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