Dir 615Operating system · Dlink

CVE-2017-11436

CRITICAL · 9.8 CVSS v3.1 Published 2017-07-19
Fix available
A fix is available. Upgrade to after 20.12ptb01 or later.
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
D-Link DIR-615 before v20.12PTb04 has a second admin account with a 0x1 BACKDOOR value, which might allow remote attackers to obtain access via a TELNET connection.

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-615 router firmware before version 20.12PTb04 contains a hardcoded backdoor admin account with a special 0x1 BACKDOOR flag value. This hidden account is accessible via remote TELNET connections, allowing unauthenticated attackers to gain full administrative control over the device.

MitigationUpgrade the D-Link DIR-615 firmware to version 20.12PTb04 or later to remove the hardcoded backdoor account. As an interim measure, disable TELNET access on the device and monitor for unauthorized remote access attempts.

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 615Operating system
Affected:<= 20.12ptb01

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
    Access the router web interface or check the device label to confirm it is a D-Link DIR-615 model
    Affected if The device is not a D-Link DIR-615 router
  2. Check the firmware version
    Log into the router web interface and navigate to the Status or System Information page to view the firmware version. Compare it against the affected range: any version 20.12ptb01 or earlier.
    Affected if The firmware version is 20.12ptb01 or lower (older than 20.12PTb04)
  3. Verify if TELNET remote access is enabled
    Access the router web interface and check the Remote Management settings or Security settings for TELNET/port 23 access configuration. Alternatively, attempt a telnet connection to the router's public IP on port 23 from an external network.
    Affected if TELNET access is enabled and accessible remotely (port 23 open)
  4. Test for the backdoor account
    Connect to the router via TELNET (if enabled) and attempt to log in with the hardcoded backdoor credentials. The vulnerability description indicates a hidden admin account exists with a special 0x1 BACKDOOR flag value.
    Affected if A login succeeds using a hidden or undocumented admin account that provides full administrative access

You are affected if you have a D-Link DIR-615 router running firmware version 20.12ptb01 or earlier with TELNET remote access enabled, as this allows unauthenticated attackers to access the hardcoded backdoor admin account.

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
Upgrade available Upgrade to a release after 20.12ptb01
Interim mitigation

Upgrade the D-Link DIR-615 firmware to version 20.12PTb04 or later to remove the hardcoded backdoor account. As an interim measure, disable TELNET access on the device and monitor for unauthorized remote access attempts.

Recommended fix High confidence

v20.12PTb04 or later

  1. Obtain the firmware version v20.12PTb04 or later from the official D-Link support website (ftp2.dlink.com or dlink.com)
  2. Navigate to the device administration web interface
  3. Locate the Firmware Upgrade or System section
  4. Upload and apply the updated firmware file
  5. After the device restarts, verify the firmware version has been updated
  6. Disable TELNET access through the router configuration if not needed

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

Fix this in Dir 615 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11436 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11436 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