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

CVE-2021-40655

D-Link DIR-605 Router Information Disclosure Vulnerability

D-Link DIR-605 Router

An informtion disclosure issue exists in D-LINK-DIR-605 B2 Firmware Version : 2.01MT. An attacker can obtain a user name and password by forging a post request to the / getcfg.php page

CVSS
7.5
HIGH
EPSS
87%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
24 Sep 2021
CWE-863

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 16 May 2024. US federal agencies were required to remediate it by 6 June 2024.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 87%, which is higher than 99.8% 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:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Frequently asked questions

Is CVE-2021-40655 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2021-40655.

What does CVE-2021-40655 affect?

CVE-2021-40655 affects D-Link DIR-605 Router. An informtion disclosure issue exists in D-LINK-DIR-605 B2 Firmware Version : 2.01MT. An attacker can obtain a user name and password by forging a post request to the / getcfg.php page

How severe is CVE-2021-40655?

CVE-2021-40655 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 87%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 6 June 2024.

How should organisations respond to CVE-2021-40655?

Apply the vendor patch for D-Link DIR-605 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.