CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability

CVE-2019-7193

QNAP QTS Improper Input Validation Vulnerability

QNAP QTS

This improper input validation vulnerability allows remote attackers to inject arbitrary code to the system. To fix the vulnerability, QNAP recommend updating QTS to their latest versions.

CVSS
9.8
CRITICAL
EPSS
14.4%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
5 Dec 2019
CWE-20

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 8 June 2022. US federal agencies were required to remediate it by 22 June 2022. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 14.4%, which is higher than 96.5% 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-2019-7193 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2019-7193.

What does CVE-2019-7193 affect?

CVE-2019-7193 affects QNAP QTS. This improper input validation vulnerability allows remote attackers to inject arbitrary code to the system. To fix the vulnerability, QNAP recommend updating QTS to their latest versions.

How severe is CVE-2019-7193?

CVE-2019-7193 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 14.4%, higher than 96.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 June 2022.

How should organisations respond to CVE-2019-7193?

Apply the vendor patch for QNAP QTS 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.