Vulnerabilities

If Content Security Policy blocked frame navigation, the full destination of a redirect served in the frame was reported in the violation report; as opposed to the original frame URI. This could be used to leak sensitive information contained in such URIs. This vulnerability affects Firefox

As specified in the W3C Content Security Policy draft, when creating a violation report, "User agents need to ensure that the source file is the URL requested by the page, pre-redirects. If that’s not possible, user agents need to strip the URL down to an origin to avoid unintentional leakage." Under certain types of redirects, Firefox incorrectly set the source file to be the destination of the redirects. This was fixed to be the redirect destination's origin. This vulnerability affects Firefox

Depending on configuration of various package managers it is possible for an attacker to insert a malicious package into a package manager&amp;#39;s repository which can be retrieved and used during development, build, and release processes. This insertion could lead to remote code execution. We believe this vulnerability affects multiple package managers across multiple languages, including but not limited to: Python/pip, .NET/NuGet, Java/Maven, JavaScript/npm.<br /> Attack scenarios<br /> An attacker could take advantage of this ecosystem-wide issue to cause harm in a variety of ways. The original attack scenarios were discovered by Alex Birsan and are detailed in their whitepaper, Dependency Confusion: How I Hacked Into Apple, Microsoft and Dozens of Other Companies.<br /> <br /> With basic knowledge of the target ecosystems, an attacker could create an empty shell for a package and insert malicious code in the install scripts, give it a high version, and publish it to the public repository. Vulnerable victim machines will download the higher version of the package between the public and private repositories and attempt to install it. Due to code incompatibility it will probably error out upon import or upon compilation, making it easier to detect; however the attacker would have gained code execution by that point.<br /> <br /> An advanced attacker with some inside knowledge of the target could take a copy of a working package, insert the malicious code (in the package itself or in the install), and then publish it to a public repository. The package will likely install and import correctly, granting the attacker an initial foothold and persistence.<br /> <br /> <br /> These two methods could affect target organizations at any of these various levels:<br /> <br /> Developer machines<br /> An entire team if the configuration to import the malicious package is uploaded to a code repository<br /> Continuous integration pipelines if they pull the malicious packages during the build, test, and/or deploy stages<br /> Customers, download servers, production services if the malicious code has not been detected<br /> <br /> This remote code execution vulnerability can only be addressed by reconfiguring installation tools and workflows, and not by correcting anything in the package repositories themselves. See the FAQ section of this CVE for configuration guidance.<br />

Windows Event Tracing Elevation of Privilege Vulnerability

.NET Framework Denial of Service Vulnerability

Microsoft Azure Kubernetes Service Elevation of Privilege Vulnerability

Windows Event Tracing Elevation of Privilege Vulnerability

Windows PKU2U Elevation of Privilege Vulnerability

Microsoft Edge for Android Information Disclosure Vulnerability

Microsoft Dataverse Information Disclosure Vulnerability

Windows DirectX Information Disclosure Vulnerability

Microsoft Teams iOS Information Disclosure Vulnerability