CVE-2024-11065
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 · uneditedThe D-Link DSL6740C modem has an OS Command Injection vulnerability, allowing remote attackers with administrator privileges to inject and execute arbitrary system commands through a specific functionality provided by SSH and Telnet.
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 confidenceAuthenticated OS command injection vulnerability in D-Link DSL6740C modem. An attacker with administrator-level access can inject and execute arbitrary system commands through SSH or Telnet interfaces, potentially leading to complete device compromise and lateral movement.
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 dataall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 device model and firmware versionAccess the device web interface (usually at 192.168.1.1) and check the status or management page for the exact model number (DSL6740C) and firmware version. Alternatively, check the device label on the physical unit.Affected if The device model is D-Link DSL6740C with any firmware version - all versions are affected per vendor.
-
Check if SSH service is enabledAttempt to connect to the device on port 22 (SSH). Use a network scanner (nmap -p 22 192.168.1.1) from within the local network to test if SSH is listening.Affected if SSH is accessible on the device - this is one of the command injection vectors.
-
Check if Telnet service is enabledAttempt to connect to the device on port 23 (Telnet). Use nmap (nmap -p 23 192.168.1.1) or telnet 192.168.1.1 from the local network.Affected if Telnet is accessible on the device - this is the second command injection vector.
-
Verify administrative access restrictionsCheck the device web interface under Remote Management, Administration, or Access Control settings to see if SSH/Telnet access is restricted to specific IP addresses or if it allows connections from any source.Affected if Remote SSH or Telnet administrative access is open to untrusted IP addresses (e.g., internet-facing or to any LAN hosts).
The device is affected if it is a D-Link DSL6740C with SSH or Telnet administrative interfaces enabled and accessible, especially from untrusted networks.
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 dataImmediately restrict administrative access to trusted IP addresses, change default credentials, and disable Telnet if unused. Contact D-Link for firmware patches and monitor for unauthorized administrative access.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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 $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11065 — 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-11065 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