Skip to content
CTI Academy Sponsor CTI Academy
MEDIUM · CVSS 6.5 CISA Known Exploited Vulnerability

CVE-2019-0703

Microsoft Windows SMB Information Disclosure Vulnerability

Microsoft Windows

An information disclosure vulnerability exists in the way that the Windows SMB Server handles certain requests, aka 'Windows SMB Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2019-0704, CVE-2019-0821.

CVSS
6.5
MEDIUM
EPSS
9.4%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
9 Apr 2019
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 23 May 2022. US federal agencies were required to remediate it by 13 June 2022.

EPSS — exploitation probability

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

Frequently asked questions

Is CVE-2019-0703 being exploited by ransomware groups?

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

What does CVE-2019-0703 affect?

CVE-2019-0703 affects Microsoft Windows. An information disclosure vulnerability exists in the way that the Windows SMB Server handles certain requests, aka 'Windows SMB Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2019-0704, CVE-2019-0821.

How severe is CVE-2019-0703?

CVE-2019-0703 is rated MEDIUM with a CVSS base score of 6.5. EPSS puts the probability of exploitation in the next 30 days at 9.4%, higher than 95.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 13 June 2022.

How should organisations respond to CVE-2019-0703?

Apply the vendor patch for Microsoft Windows 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.