How severe is CVE-2014-100005?

CVE-2014-100005 has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2014-100005?

Affected package information for CVE-2014-100005 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2014-100005?

No patch has shipped for CVE-2014-100005 yet — track the dlink dir-600 advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2014-100005 across my infrastructure?

Inventory every dlink dir-600 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2014-100005 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2014-100005?

O3 detects and blocks CVE-2014-100005 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2014-100005 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-100005, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-100005?

CVE-2014-100005 has an EPSS (Exploit Prediction Scoring System) score of 42.4%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2014-100005 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2014-100005 (D-Link DIR-600 Router Cross-Site Request Forgery (CSRF) Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-05-16. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-06-06. The required action was: This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2014-100005?

CVE-2014-100005 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2014-100005?

CVE-2014-100005 affects dlink dir-600; dlink dir-600 firmware. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2014-100005 published, and has it been updated?

CVE-2014-100005 was published on January 13, 2015 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-05-16 — agencies required to remediate by 2024-06-06

CVE-2014-100005

HIGH

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…

Published

Jan 13, 2015

Updated

Oct 22, 2025

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

42.4%probability of exploitation in next 30 days

High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

2 products · 2 configurations

Hardware

dir-600dlink

all

dir-600 firmwaredlink

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Multiple cross-site request forgery (CSRF) vulnerabilities in D-Link DIR…

resources.infosecinstitute.comNVDSep 2017

Multiple cross-site request forgery (CSRF) vulnerabilities in D-Link DIR…

github.comMetasploitOct 2020

Multiple cross-site request forgery (CSRF) vulnerabilities in D-Link DIR…

cisa.govCISAMay 2024

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every dlink dir-600 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2014-100005 yet — track the dlink dir-600 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2014-100005 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2014-100005. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2014-100005 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2014-100005 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2014-100005

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2014-100005 being exploited in your environment?