IRONSMITHINTEL
HIGHCVSS7.5
|
Actively Exploited
|CISA KEV|CVE-2023-38180|Auth: none — unauthenticated|Reboot: required|Manual only

KB5029688: Windows Server Security Update (August 2023)

Microsoft .NET Core and Visual Studio contain an unspecified vulnerability that allows for denial-of-service (DoS).

Published Aug 8, 2023 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve partial data exposure, complete denial of service or system unavailability. Federal agencies are required to remediate by 2023-08-30 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-400) (CWE-400) vulnerability in Microsoft .NET Core and Visual Studio. .NET and Visual Studio Denial of Service Vulnerability Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

IT Security
Running .net: 6.0.0 ≤ v < 6.0.21, 7.0.0 ≤ v < 7.0.10; asp.net core: 2.1 ≤ v < 2.1.40; visual studio 2022: 17.2.0 ≤ v < 17.2.18, 17.4.0 ≤ v < 17.4.10, 17.6.0 ≤ v < 17.6.6; fedora: 37, 38
Fixed inKB5029688, KB5029689 (applies to 6 product versions) — build 17.2.18, 17.4.10+
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2023-08-09 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2023-08-30.

How to patch

Manual download

For air-gapped servers or out-of-band deployment. Microsoft Update Catalog returns every OS-version variant of this update.

↗ Microsoft Update CatalogKB5029688

Manual remediation steps

Apply the Microsoft Security Update

Microsoft has released an official security update that fixes this vulnerability.

Required KB Updates

    1
    KB5029688 — https://support.microsoft.com/help/5029688
    1
    KB5029689 — https://support.microsoft.com/help/5029689

Affected Products

    1
    .NET 6.0
    1
    .NET 7.0
    1
    ASP.NET Core 2.1
    1
    Microsoft Visual Studio 2022 version 17.2
    1
    Microsoft Visual Studio 2022 version 17.4
    1
    Microsoft Visual Studio 2022 version 17.6

Fixed Build Numbers

    1
    17.2.18
    1
    17.4.10
    1
    17.6.6
    1
    2.1.40
    1
    6.0.21
    1
    7.0.10

Installation Methods

Windows Update (recommended)

1
Settings → Windows Update → Check for updates
2
The security update is offered if your system is in scope
3
Restart when prompted (may or may not be required for this update)

Microsoft Update Catalog (manual download)

1
Open https://catalog.update.microsoft.com
2
Search for KB5029688
3
Download the package matching your OS architecture and Windows build
4
Run the .msu installer with administrator privileges
5
Restart when prompted

WSUS / SCCM / Intune

Approve KB5029688 for the affected products in your update management console.

Microsoft Download Center Links

    1
    https://dotnet.microsoft.com/download/dotnet/6.0
    1
    https://dotnet.microsoft.com/download/dotnet/7.0
    1
    https://github.com/dotnet/announcements/issues/269
    1
    https://my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.2
    1
    https://my.visualstudio.com/Downloads?q=Visual Studio 2022 version 17.4
    1
    (…1 more)

Verification

Confirm the update is installed:

Get-HotFix | Where-Object { $_.HotFixID -in @('KB5029688','KB5029689') }

References

    1
    Microsoft Security Response Center: https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2023-38180
    1
    KB article: https://support.microsoft.com/help/5029688
    1
    KB article: https://support.microsoft.com/help/5029689
    1
    NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2023-38180
    1
    CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-38180
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.