As the calendar turns to a fresh, new year, we are back again with a gist of the Patch Tuesday updates, released by the Redmond-based IT giants. This month, Microsoft has listed fixes for 48 vulnerabilities.  

After an initial discussion about this month’s updates, we’ll offer our advice for devising a plan to handle patch management in a hybrid work environment. You can also register for our free Patch Tuesday webinar and listen to our experts break down Patch Tuesday updates in detail.  

What is Patch Tuesday?  

Patch Tuesday falls on the second Tuesday of every month. On this day, Microsoft releases security and non-security updates for its operating system and other related applications. Since Microsoft has upheld this process of releasing updates in a periodic manner, IT admins expect these updates and have time to gear up for them.

Why is Patch Tuesday important?  

Important security updates and patches to fix critical bugs or vulnerabilities are released on Patch Tuesday. Usually zero-day vulnerabilities are also fixed during Patch Tuesday unless the vulnerability is critical and highly exploited, in which case an out-of-band security update is released to address that particular vulnerability.

January 2024 Patch Tuesday: Security updates lineup  

Here is a breakdown of the 48 vulnerabilities fixed this month:

  • CVE IDs: 48

  • Republished CVE IDs: Five (more details on this below)

Here is a breakdown of the 48 vulnerabilities fixed this month, based on the severity:

  • Critical: 2

  • High: 26

  • Medium: 20

Security updates were released for the following products, features, and roles:

  • SQL Server

  • .NET and Visual Studio

  • Windows Scripting

  • Windows Common Log File System Driver

  • Windows ODBC Driver

  • Windows Online Certificate Status Protocol (OCSP) SnapIn

  • Visual Studio

  • Windows Group Policy

  • Microsoft Virtual Hard Drive

  • Windows Message Queuing

  • Windows BitLocker

  • .NET Core & Visual Studio

  • Windows Authentication Methods

  • Azure Storage Mover

  • Microsoft Office

  • Windows Subsystem for Linux

  • Windows Cryptographic Services

  • Windows Win32K

  • Windows Win32 Kernel Subsystem

  • Windows AllJoyn API

  • Windows Nearby Sharing

  • Windows Themes

  • Windows Local Security Authority Subsystem Service (LSASS)

  • Windows Collaborative Translation Framework

  • Windows Libarchive

  • Windows Kernel

  • Windows Hyper-V

  • Unified Extensible Firmware Interface

  • Microsoft Bluetooth Driver

  • Remote Desktop Client

  • Windows Kernel-Mode Drivers

  • Windows Cloud Files Mini Filter Driver

  • .NET Framework

  • Windows TCP/IP

  • Windows Server Key Distribution Service

  • Microsoft Office SharePoint

  • Microsoft Identity Services

  • Microsoft Devices

 Learn more in the MSRC’s release notes.

Republished CVE IDs

Besides the vulnerabilities fixed in this month’s Patch Tuesday, Microsoft has also republished twelve CVE IDs. These are as follows:

Third-party updates released after last month’s Patch Tuesday  

Third-party vendors such as Google, Cisco, Ivanti, and SAP also released updates this January.

Best practices to handle patch management in a hybrid work environment  

Most organizations have opted to embrace remote work even after they have been cleared to return to the office. This decision poses various challenges to IT admins, especially in terms of managing and securing distributed endpoints.

Here are a few pointers to simplify the process of remote patching:

  • Disable automatic updates because one faulty patch could bring down the whole system. IT admins can educate end users on how to disable automatic updates on their machines. Patch Manager Plus and Endpoint Central also have a dedicated patch, 105427, that can be deployed to endpoints to ensure that automatic updates are disabled.

  • Create a restore point—a backup or image that captures the state of the machines—before deploying big updates like those from Patch Tuesday.

  • Establish a patching schedule and keep end users informed about it. It is recommended to set up a time for deploying patches and rebooting systems. Let end users know what needs to be done on their end for trouble-free patching.

  • Test the patches on a pilot group of systems before deploying them to the production environment. This will ensure that the patches do not interfere with the workings of other applications.

  • Since many users are working from home, they all might be working different hours; in this case, you can allow end users to skip deployment and scheduled reboots. This will give them the liberty to install updates at their convenience and avoid disrupting their work. Our patch management products come with options for user-defined deployment and reboot.

  • Most organizations are deploying patches using a VPN. To stop patch tasks from eating up your VPN bandwidth, install Critical patches and security updates first. You might want to hold off on deploying feature packs and cumulative updates since they are bulky updates and consume a lot of bandwidth.

  • Schedule the non-security updates and security updates that are not rated Critical to be deployed after Patch Tuesday, such as during the third or fourth week of the month. You can also choose to decline certain updates if you feel they are not required in your environment.

  • Run patch reports to get a detailed view of the health status of your endpoints.

  • For machines belonging to users returning to the office after working remotely, check if they are compliant with your security policies. If not, quarantine them.

  • Install the latest updates and feature packs before deeming your back-to-office machines fit for production.

  • Take inventory of and remove apps that are now obsolete for your back-to-office machines, like remote collaboration software.

With Endpoint Central, Patch Manager Plus, or Vulnerability Manager Plus you can completely automate the entire process of patch management, from testing patches to deploying them. You can also tailor patch tasks according to your current needs. For a hands-on experience with either of these products, try a free, 30-day trial and keep thousands of applications patched and secure.

Want to learn more about Patch Tuesday updates? Join our experts as they break down this month’s Patch Tuesday updates and offer in-depth analysis. You can also ask our experts questions and get answers to all your Patch Tuesday questions. Register for our free Patch Tuesday webinar.

Ready, get set, patch!

  1. Rob

    How long does it take for Patches to update in Patch Manager – End point Central?

    • Anupam Kundu

      Hey Rob,

      For Microsoft patches, the security updates are released within 12-18 hours from the vendor release and for the non-security updates, they are released within 24 hours. For third-party updates, the patches are released within 6-9 hours from the vendor release.