Windows 10: PrintNightmare and CVE-2021-1675

petrula · Jul 7, 2021

Does "2021-07 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems KB5004945" include the patch for CVE-2021-1675 i.e. PrintNightmare?If not, where do I find the proper update?Thank you in advance.

:)

Brink · Jul 7, 2021

Updates - TCP/IP:  CVE-2021-24074, CVE-2021-24094, and CVE-2021-24086

Today Microsoft released a set of fixes affecting Windows TCP/IP implementation that include two Critical Remote Code Execution (RCE) vulnerabilities (CVE-2021-24074, CVE-2021-24094) and an Important Denial of Service (DoS) vulnerability (CVE-2021-24086). The two RCE vulnerabilities are complex which make it difficult to create functional exploits, so they are not likely in the short term. We believe attackers will be able to create DoS exploits much more quickly and expect all three issues might be exploited with a DoS attack shortly after release. Thus, we recommend customers move quickly to apply Windows security updates this month.

The DoS exploits for these CVEs would allow a remote attacker to cause a stop error. Customers might receive a blue screen on any Windows system that is directly exposed to the internet with minimal network traffic.

It is essential that customers apply Windows updates to address these vulnerabilities as soon as possible. If applying the update quickly is not practical, workarounds are detailed in the CVEs that do not require restarting a server. These three vulnerabilities are unique and require separate workarounds depending on the exposure of an affected system; however, they can be thought of in terms of Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) solutions.

The IPv4 workaround simply requires further hardening against the use of Source Routing, which is disallowed in Windows default state. This workaround is documented in CVE-2021-24074 and can be applied through Group Policy or by running a NETSH command that does not require a reboot. The IPv6 workarounds are documented in CVE-2021-24094 and CVE-2021-24086, and require blocking IPv6 fragments, which may negatively impact services with dependencies on IPv6.

Note: IPv4 Source Routing requests and IPv6 fragments can be blocked on an edge device, such as a load balancer or a firewall. This option can be used to mitigate systems with high-risk exposure and then allow the systems to be patched following their standard cadence.

These vulnerabilities were discovered by Microsoft as part of our continual focus on strengthening the security of our products. At this time, we have no evidence that these vulnerabilities were known to any third party. These vulnerabilities result from a flaw in Microsoft’s implementation of TCP/IP and affect all Windows versions. Non-Microsoft implementations are not affected.

It is important that affected systems are patched as quickly as possible because of the elevated risk associated with these vulnerabilities, and downloads for these can be found in the Microsoft Security Update Guide.  Customers who have automatic updates enabled are automatically protected from these vulnerabilities.

We recommend that you apply the updates released February 9, 2021 with priority to all of your Windows devices, as they address CVE-2021-24074, CVE-2021-24094 and CVE-2021-24086. Here is what you need to know:

If you are running a supported version of Windows and have automatic updates enabled, you are automatically protected and do not need to take any further action.

If you are managing updates on behalf of your organization, you should download the latest updates from the Microsoft Security Update Guide and apply those updates to your Windows devices as soon as possible.

If you are unable to apply updates right away, look at the CVEs for the workaround mitigations to use in the short term until you can deploy the updates.

If you are running an unsupported version of Windows, we recommend that you upgrade to the current version of Windows to benefit from the latest security protections.
Click to expand...

Source:

https://msrc-blog.microsoft.com/2021...ecting-tcp-ip/

https://docs.microsoft.com/en-us/win...ge-center#1556

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

DaveCiP · Jul 7, 2021

Patching of CVE-2020-0601

I have a computer that does not list the patch for CVE-2020-060, KB4534293, OS build17134.1246. However, KB4554349 is listed on the same PC, which is OS build 17134.1401. Was the patch for CVE-2020-0601 included in OS build 17134.1401?

Aleena97 · Jul 7, 2021

Cumulative Patch addressing CVE

Hi All,

I have a List of CVE dated from 2017 to 2020. Recently we have patched "June 2020 Cumulative update- KB4567517". However, none of the CVEs are addressed by this cumulative update-KB4567517. In my understanding from Microsoft portal, "Cumulative update encompasses
all previous patches". Is it safe to close CVE from 2017 to 2020 by saying these CVEs are addressed by latest cumulative patch?

Thank you very much for time.

Windows 10: PrintNightmare and CVE-2021-1675

PrintNightmare and CVE-2021-1675

PrintNightmare and CVE-2021-1675

PrintNightmare and CVE-2021-1675

PrintNightmare and CVE-2021-1675 - Similar Threads - PrintNightmare CVE 2021

windows network printers ; a giant shitshow after printnightmare updates august 2021

windows network printers ; a giant shitshow after printnightmare updates august 2021

windows network printers ; a giant shitshow after printnightmare updates august 2021

Microsoft’s Response to CVE-2021-44228 Apache Log4j 2

CVE-2021-41379

CVE-2021-41379

Windows – CVE-2021-36934 Work around

Vulnerability CVE-2021-36934

Updates - TCP/IP:  CVE-2021-24074, CVE-2021-24094, and CVE-2021-24086