vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2019-1040

Windows NTLM Tampering Vulnerability

MEDIUM
5.3
CVSS Score
Published: June 12, 2019 at 01:49 PM UTC
Updated: June 17, 2026 at 02:27 AM UTC
17 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1703 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1703 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM5.3
Exploit prediction
EPSS 48%

Description

A tampering vulnerability exists in Microsoft Windows when a man-in-the-middle attacker is able to successfully bypass the NTLM MIC (Message Integrity Check) protection. An attacker who successfully exploited this vulnerability could gain the ability to downgrade NTLM security features. To exploit this vulnerability, the attacker would need to tamper with the NTLM exchange. The attacker could then modify flags of the NTLM packet without invalidating the signature. The update addresses the vulnerability by hardening NTLM MIC protection on the server-side.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Windows 10· Microsoft
95%
10.0.0 ≤ v < publication160717031709180318091903
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1507· Microsoft
95%
10.0.10240.0 ≤ v < publication10.0.10240.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1607· Microsoft
95%
10.0.14393.0 ≤ v < publication10.0.14393.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 10 1809· Microsoft
95%
10.0.0 ≤ v < publication10.0.17763.0 ≤ v < publication10.0.010.0.17763.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 7· Microsoft
95%
6.1.0 ≤ v < publication6.1.0sp1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows 8-1· Microsoft
95%
6.3.0 ≤ v < publication6.3.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows Rt 8-1· Microsoft
95%
All versions
Windows Server 1803· Microsoft
95%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows Server 1903· Microsoft
95%
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
Windows Server 2008· Microsoft
95%
6.0.0 ≤ v < publication6.0.6003.0 ≤ v < publication6.1.0 ≤ v < publication6.1.7601.0 ≤ v < publication6.0.06.0.6003.06.1.06.1.7601.0r2 sp1sp2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

Vendor Advisory
Source: [email protected]
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-1040
PatchVendor Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1040

CVSS

5.3MEDIUMmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card