Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2015-2051

D-Link DIR-645 Router Remote Code Execution Vulnerability

D-Link DIR-645 Router

The D-Link DIR-645 Wired/Wireless Router Rev. Ax with firmware 1.04b12 and earlier allows remote attackers to execute arbitrary commands via a GetDeviceSettings action to the HNAP interface.

CVSS
8.8
HIGH
EPSS
97.1%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
23 Feb 2015
CWE-77

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 10 February 2022. US federal agencies were required to remediate it by 10 August 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 97.1%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2015-2051 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2015-2051.

What does CVE-2015-2051 affect?

CVE-2015-2051 affects D-Link DIR-645 Router. The D-Link DIR-645 Wired/Wireless Router Rev. Ax with firmware 1.04b12 and earlier allows remote attackers to execute arbitrary commands via a GetDeviceSettings action to the HNAP interface.

How severe is CVE-2015-2051?

CVE-2015-2051 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 97.1%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 10 August 2022.

How should organisations respond to CVE-2015-2051?

Apply the vendor patch for D-Link DIR-645 Router as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.