dbcve.org
Dir 860l FirmwareOperating system · Dlink

CVE-2024-41611

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
In D-Link DIR-860L REVA FIRMWARE PATCH 1.10..B04, the Telnet service contains hardcoded credentials, enabling attackers to log in remotely to the Telnet service and perform arbitrary commands.

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 · high confidence

The D-Link DIR-860L router firmware version 1.10..B04 contains hardcoded credentials embedded in the Telnet service binary. Attackers can use these credentials to authenticate to the exposed Telnet port remotely and execute arbitrary commands with elevated privileges on the affected device.

MitigationIf the device cannot be updated to a patched firmware version, disable the Telnet service immediately. If Telnet is required for legitimate purposes, restrict access via firewall rules to only trusted management IP addresses.

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 860l FirmwareOperating system
Affected:= 1.10b04

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
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 checks

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

  1. Identify the device model
    Check the device label on the router casing, or access the web administration interface (typically at 192.168.0.1) and look for the model number on the Status or Device Info page.
    Affected if The device is a D-Link DIR-860L router.
  2. Check the installed firmware version
    In the web interface, navigate to Status or System > Firmware Upgrade page to view the current firmware version. Alternatively, check via CLI if SSH/telnet access is already available.
    Affected if The firmware version is exactly 1.10b04.
  3. Determine if Telnet service is enabled
    Log into the web interface and check under System > Remote Management or similar settings for Telnet enable status. Alternatively, from a local network host, run 'telnet <router_ip>' on port 23 to test if the service responds.
    Affected if Telnet service is enabled and port 23 responds to connection attempts.
  4. Assess Telnet network accessibility
    From an external network perspective (or from a non-local subnet), attempt to connect to the router's public IP on port 23, or review firewall rules to determine if inbound Telnet traffic is permitted.
    Affected if Port 23 is accessible from untrusted or external networks (not blocked by firewall).

A device is affected if it is a D-Link DIR-860L running firmware version 1.10b04 with Telnet service enabled and accessible from the network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If the device cannot be updated to a patched firmware version, disable the Telnet service immediately. If Telnet is required for legitimate purposes, restrict access via firewall rules to only trusted management IP addresses.

Recommended fix Moderate confidence
  1. This D-Link DIR-860L model has reached end-of-life and no longer receives firmware updates from the vendor.
  2. Disable the Telnet service on the device if not required for legitimate business use.
  3. If Telnet is required, implement network access controls to restrict Telnet access to trusted IP addresses only via firewall rules.
  4. Consider replacing the affected hardware with a currently supported router that receives regular security updates.
  5. Monitor D-Link's support pages (www.dlink.com) for any future firmware releases that address this vulnerability.
Caveat The DIR-860L is an older end-of-life device with no available firmware patch; replacement is the recommended remediation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 860l Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41611 — 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-41611 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