Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 48.04% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2019
CVE-2019-1040High confidence
Windows NTLM Tampering Vulnerability
Microsoft · Windows 10 Version 1703
5.3MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Windows 10 Version 1703 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
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.
What
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.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration. - CWE not yet assigned
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N/E:P/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Windows 10 Version 1703: 10.0.0 < publication
- Windows 10 Version 1803: 10.0.0 < publication
- Windows Server, version 1803 (Server Core Installation): 10.0.0 < publication
- Windows 10 Version 1809: 10.0.17763.0 < publication, 10.0.0 < publication
- Windows Server 2019: 10.0.17763.0 < publication
- Windows Server 2019 (Server Core installation): 10.0.17763.0 < publication
- Windows 10 Version 1709 for 32-bit Systems: 10.0.0 < publication
- Windows 10 Version 1709: 10.0.0 < publication
- Windows 10 Version 1903 for 32-bit Systems: 10.0.0 < publication
- Windows 10 Version 1903 for x64-based Systems: 10.0.0 < publication
- Windows 10 Version 1903 for ARM64-based Systems: 10.0.0 < publication
- Windows Server, version 1903 (Server Core installation): 10.0.0 < publication
- Windows 10 Version 1507: 10.0.10240.0 < publication
- Windows 10 Version 1607: 10.0.14393.0 < publication
- Windows Server 2016: 10.0.14393.0 < publication
- Windows Server 2016 (Server Core installation): 10.0.14393.0 < publication
- Windows 7: 6.1.0 < publication
- Windows 7 Service Pack 1: 6.1.0 < publication
- Windows 8.1: 6.3.0 < publication
- Windows Server 2008 Service Pack 2: 6.0.6003.0 < publication, 6.0.0 < publication
- Windows Server 2008 Service Pack 2 (Server Core installation): 6.0.6003.0 < publication
- Windows Server 2008 Service Pack 2: 6.0.6003.0 < publication
- Windows Server 2008 R2 Systems Service Pack 1: 6.1.0 < publication
- Windows Server 2008 R2 Service Pack 1: 6.1.7601.0 < publication
- Windows Server 2008 R2 Service Pack 1 (Server Core installation): 6.1.7601.0 < publication
- Windows Server 2012: 6.2.9200.0 < publication
- Windows Server 2012 (Server Core installation): 6.2.9200.0 < publication
- Windows Server 2012 R2: 6.3.9600.0 < publication
- Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < publication
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 12 Jun 2019 · Last source change 20 May 2025, 17:50 UTC · CWE not yet assigned
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2019-9625
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2019-9625 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2019-9625"}
- Vendor guidanceAuthoritative vendor guidance changed: added patch: portal.msrc.microsoft.com/CVE-2019-1040; added remediation: portal.msrc.microsoft.com/CVE-2019-1040; removed vendor advisory: msrc.microsoft.com/CVE-2019-1040.portal.msrc.microsoft.com ↗
- Before
- vendor advisory: msrc.microsoft.com/CVE-2019-1040
- After
- patch: portal.msrc.microsoft.com/CVE-2019-1040 · remediation: portal.msrc.microsoft.com/CVE-2019-1040
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.0 < publication; 10.0.17763.0 < publication · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 10.0.0 < publication; 10.0.17763.0 < publication · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.portal.msrc.microsoft.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.