CVE-2019-1054

A security feature bypass vulnerability exists in Edge that allows for bypassing Mark of the Web Tagging (MOTW). Failing to set the MOTW means that a large number of Microsoft security technologies are bypassed. In a web-based attack scenario, an attacker could host a malicious website that is designed to exploit the security feature bypass. Alternatively, in an email or instant message attack scenario, the attacker could send the targeted user a specially crafted .url file that is designed to exploit the bypass. Additionally, compromised websites or websites that accept or host user-provided content could contain specially crafted content to exploit the security feature bypass. However, in all cases an attacker would have no way to force a user to view attacker-controlled content. Instead, an attacker would have to convince a user to take action. For example, an attacker could entice a user to either click a link that directs the user to the attacker's site or send a malicious attachment. The security update addresses the security feature bypass by correcting how Edge handles MOTW tagging.

• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-1054
• https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1054Patch, Vendor Advisory

Published

Jun 12, 2019

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2019-10534Null-pointer dereference can occur while accessing the super…9.8
• CVE-2019-10535Improper validation for loop variable received from firmware…5.5
• CVE-2019-10536Potential double free scenario if driver receives another DI…7.8
• CVE-2019-10537Improper validation of event buffer extracted from FW respon…7.8
• CVE-2019-10538Lack of check of address range received from firmware respon…9.8
• CVE-2019-10539Possible buffer overflow issue due to lack of length check w…9.8
• CVE-2019-10540Buffer overflow in WLAN NAN function due to lack of check of…9.8
• CVE-2019-10541Dereference on uninitialized buffer can happen when parsing …9.8
• CVE-2019-10542Buffer over-read may occur when downloading a corrupted firm…9.8
• CVE-2019-10544Improper length check on source buffer to handle userspace d…7.8
• CVE-2019-10545Null pointer dereference issue in kernel due to missing chec…5.5
• CVE-2019-10546Buffer overflow can occur in WLAN firmware while parsing bea…9.8