Windows 10: Is Visual Studio affected by Apache Log4j Vulnerability, CVE-2021-44228?

KamilWolanski · Dec 14, 2021

Is Visual Studio Affected by the vulnerability below, and if so what the recommendation is to address it? I mean not only newest version, but for example 2010, 2012, 2013.

:)

steve108 · Dec 14, 2021

Log4J???

From Microsoft 365 Defender Threat Intelligence Team

Microsoft Threat Intelligence Center (MSTIC)

"December 11, 2021
Guidance for preventing, detecting, and hunting for CVE-2021-44228 Log4j 2 exploitation"

https://www.microsoft.com/security/b...-exploitation/

Brink · Dec 14, 2021

Clarified Guidance CVE-2021-34527 Windows Print Spooler Vulnerability

On Tuesday July 6, 2021, Microsoft issued CVE-2021-34527 regarding a Windows Print Spooler vulnerability. Updates were released on July 6 and 7 which addressed the vulnerability for all supported Windows versions. We encourage customers to update as soon as possible.

CVE-2021-34527 – Windows Print Spooler Remote Code Execution Vulnerability.

Following the out of band release (OOB) we investigated claims regarding the effectiveness of the security update and questions around the suggested mitigations.

Our investigation has shown that the OOB security update is working as designed and is effective against the known printer spooling exploits and other public reports collectively being referred to as PrintNightmare. All reports we have investigated have relied on the changing of default registry setting related to Point and Print to an insecure configuration.

Microsoft has focused its efforts on making customer protections available as quickly as possible and our guidance has been updated as our understanding of the issue has evolved. We recommend that customer follow these steps immediately:

In ALL cases, apply the CVE-2021-34527 security update. The update will not change existing registry settings

After applying the security update, review the registry settings documented in the CVE-2021-34527 advisory

If the registry keys documented do not exist, no further action is required

If the registry keys documented exist, in order to secure your system, you must confirm that the following registry keys are set to 0 (zero) or are not present:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint

NoWarningNoElevationOnInstall = 0 (DWORD) or not defined (default setting)

UpdatePromptSettings = 0 (DWORD) or not defined (default setting)

For more in depth guidance, please see KB5005010: Restricting installation of new printer drivers after applying the July 6, 2021 updates and CVE-2021-34527.

If our investigation identifies additional issues, we will take action as needed to help protect customers.

The MSRC Team
Click to expand...

Source: https://msrc-blog.microsoft.com/2021...vulnerability/

Brink · Dec 14, 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...

Windows 10: Is Visual Studio affected by Apache Log4j Vulnerability, CVE-2021-44228?

Is Visual Studio affected by Apache Log4j Vulnerability, CVE-2021-44228?

Is Visual Studio affected by Apache Log4j Vulnerability, CVE-2021-44228?

Is Visual Studio affected by Apache Log4j Vulnerability, CVE-2021-44228?

Is Visual Studio affected by Apache Log4j Vulnerability, CVE-2021-44228? - Similar Threads - Visual Studio affected

Is Microsoft azure bot Integrated with MS teams affected by the CVE-2021-44228 log4j...

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

Log4J vulnerability

Log4J vulnerability

CVE-2021-41379

Vulnerability CVE-2021-36934

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

When will Visual Studio 2021 be released?

Apache Cordova development lands on Visual Studio Code

Users found this page by searching for:

is loj4j in visual studio vulnerable

log4j check visual studio