CVE-2020-15415
DrayTek Multiple Vigor Routers OS Command Injection Vulnerability
DrayTek Multiple Vigor Routers
On DrayTek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1, cgi-bin/mainfunction.cgi/cvmcfgupload allows remote command execution via shell metacharacters in a filename when the text/x-python-script content type is used, a different issue than CVE-2020-14472.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 30 September 2024. US federal agencies were required to remediate it by 21 October 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 84.5%, which is higher than 99.7% 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:H/A:H
Frequently asked questions
Is CVE-2020-15415 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2020-15415.
What does CVE-2020-15415 affect?
CVE-2020-15415 affects DrayTek Multiple Vigor Routers. On DrayTek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1, cgi-bin/mainfunction.cgi/cvmcfgupload allows remote command execution via shell metacharacters in a filename when the text/x-python-script content type is used, a different issue than CVE-2020-14472.
How severe is CVE-2020-15415?
CVE-2020-15415 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 84.5%, higher than 99.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 21 October 2024.
How should organisations respond to CVE-2020-15415?
Apply the vendor patch for DrayTek Multiple Vigor Routers 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.