After installing .NET fixlet, WSUS still finds KB5034272 relevant

After installing Source ID KB5034272, WSUS still finds security update KB5034272 relevant and will install the update if prompted. Seems like something this specific BigFix fixlet is incorrect?

MS24-JAN: Cumulative Update for .NET Framework 3.5 and 4.8 for Windows Server 2022 - Windows Server 2022 - .NET Framework 3.5/4.8 - KB5033914 (x64)

ID 503427201
Site Patches for Windows
Category Security Update
CVE ID CVE-2023-0056; CVE-2023-21312; CVE-2023-0057
Download Size 65.91 MB
Source Microsoft
Source ID KB5034272
Source Severity Important
Source Release Date 1/9/2024

Hi @SmokyMTN, I’m finding some inconsistencies on 2 different Win2022 endpoints where a WSUS scan continues to state that I’m applicable for:

2024-01 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Microsoft server operating system version 21H2 for x64 (KB5034272)

When I attempt to manually install each KB# associated with the parent KB5034272, here are the install dialog boxes reported for both install attempts:
KB5033914

KB5033922

Are you able to reproduce by manually attempting to install each patch?

Thanks, Gus.

We ran into the same ordeal with our vulnerability scanner still flagging KB5034272 due to the “System.Web.Extensions.dll” version being at “3.5.30729.9151” even though we applied all the relevant updates from MS for Jan and KB5033914 is supposed to update that version.

Ultimately, we ended up noticing that the fixlet in the External Patches for Windows site for KB5033914 was leveraging the URL below:

https://catalog.s.download.windowsupdate.com/d/msdownload/update/software/secu/2023/12/windows10.0-kb5033914-x64-ndp48_2973910f6d0e2f30cbb62d631806c1d7526ca4ab.msu

However, when taking a look at the MS Update Catalog site, we saw that KB5033914’s download URL was:

https://catalog.s.download.windowsupdate.com/d/msdownload/update/software/secu/2023/12/windows10.0-kb5033914-x64-ndp48_c1d63ed465ac02b50d77addcad025580f6fc9f58.msu

We ended up creating a custom fixlet to deploy KB5033914 from the new URL and added a relevance clause around the “System.Web.Extensions.dll” file being at version “3.5.30729.9151”. This ended up working for us, updating the .dll file as expected, and falling off our internal vulnerability scanner.

3 Likes