dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 6 Jun 2024.
Dir 600 FirmwareOperating system · Dlink

CVE-2014-100005

HIGH · 8.0 CVSS v3.1 Published 2015-01-13
Fix available
A fix is available. Upgrade to after 2.16ww or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Public exploit Zero-click Patch available

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
Multiple cross-site request forgery (CSRF) vulnerabilities in D-Link DIR-600 router (rev. Bx) with firmware before 2.17b02 allow remote attackers to hijack the authentication of administrators for requests that (1) create an administrator account or (2) enable remote management via a crafted configuration module to hedwig.cgi, (3) activate new configuration settings via a SETCFG,SAVE,ACTIVATE action to pigwidgeon.cgi, or (4) send a ping via a ping action to diagnostic.php.

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

Multiple CSRF vulnerabilities in D-Link DIR-600 router (rev Bx) firmware before 2.17b02 allow remote attackers to hijack administrator authentication. Successful exploitation enables attackers to create new admin accounts, enable remote management, activate malicious configuration settings, or trigger diagnostic actions by tricking authenticated administrators into visiting crafted pages.

MitigationUpgrade DIR-600 firmware to version 2.17b02 or later. If upgrade is unavailable, restrict administrative access to trusted networks only and avoid browsing untrusted sites while logged into router management.

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 600 FirmwareOperating system
Affected:<= 2.16ww

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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. Check the router firmware version
    Log into the D-Link DIR-600 admin interface (typically at 192.168.0.1) and navigate to the Status or Maintenance section to view the firmware version. Alternatively, check the footer of admin pages or look for a firmware version in the system info page.
    Affected if The displayed firmware version is 2.16ww or lower, or any version below 2.17b02
  2. Verify the web management interface is accessible
    Confirm the router's web admin interface (HTTP/HTTPS on port 80 or 443) is reachable from the network. CSRF attacks require the target user to be able to access the admin interface.
    Affected if The web management interface is accessible and responds to requests
  3. Check for presence of vulnerable CGI endpoints
    Attempt to access the hedwig.cgi and pigwidgeon.cgi endpoints via the router's IP (e.g., http://192.168.0.1/hedwig.cgi). These are the paths used to create unauthorized admin accounts and modify configurations.
    Affected if These endpoints return any response (even an error) indicating they exist and are reachable
  4. Confirm if remote management is enabled
    In the router admin interface, check under Advanced or Security settings for Remote Management (WAN access) settings. This configuration determines if the admin interface is accessible from outside the local network.
    Affected if Remote management is enabled, allowing exploitation from outside the local network

A user is affected if their D-Link DIR-600 router runs firmware version 2.16ww or lower (any version below 2.17b02) and the web management interface is accessible, regardless of whether remote management is enabled.

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 2.16ww
Vendor patch securityadvisories.dlink.com →
Interim mitigation

Upgrade DIR-600 firmware to version 2.17b02 or later. If upgrade is unavailable, restrict administrative access to trusted networks only and avoid browsing untrusted sites while logged into router management.

Recommended fix High confidence

DIR-600 Firmware 2.17b02 or later

  1. 1. Log into the D-Link DIR-600 router web interface and check the current firmware version (typically under Status or System menu)
  2. 2. Navigate to the official D-Link support website (dlink.com or securityadvisories.dlink.com) and locate the DIR-600 firmware download section
  3. 3. Download firmware version 2.17b02 or later for the DIR-600 revision Bx hardware
  4. 4. In the router's web interface, go to Management or System settings
  5. 5. Select the firmware upgrade option and upload the downloaded 2.17b02 (or later) firmware file
  6. 6. Wait for the firmware upload to complete and the router to reboot automatically
  7. 7. After reboot, log back into the router and verify the firmware version has been updated to 2.17b02 or later
Caveat Router firmware upgrades may reset configuration to defaults; reconfigure your network settings after upgrading

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

Fix this in Dir 600 Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get it fixed fast

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-2014-100005 — 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-2014-100005 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