{"id":1325,"date":"2025-01-15T03:00:58","date_gmt":"2025-01-15T03:00:58","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2025\/01\/15\/microsoft-happy-2025-heres-161-security-updates\/"},"modified":"2025-01-15T03:00:58","modified_gmt":"2025-01-15T03:00:58","slug":"microsoft-happy-2025-heres-161-security-updates","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2025\/01\/15\/microsoft-happy-2025-heres-161-security-updates\/","title":{"rendered":"Microsoft: Happy 2025. Here\u2019s 161 Security Updates"},"content":{"rendered":"<p>    Microsoft: Happy 2025. Here\u2019s 161 Security Updates<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p><strong>Microsoft<\/strong> today unleashed updates to plug a whopping 161 security vulnerabilities in <strong>Windows<\/strong> and related software, including three \u201czero-day\u201d weaknesses that are already under active attack. Redmond\u2019s inaugural Patch Tuesday of 2025 bundles more fixes than the company has shipped in one go since 2017.<\/p>\n<p><img data-recalc-dims=\"1\" loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-60331\" src=\"https:\/\/i0.wp.com\/krebsonsecurity.com\/wp-content\/uploads\/2022\/07\/winupdatedate.png?resize=749%2C496&#038;ssl=1\" alt=\"\" width=\"749\" height=\"496\" srcset=\"https:\/\/krebsonsecurity.com\/wp-content\/uploads\/2022\/07\/winupdatedate.png 923w, https:\/\/krebsonsecurity.com\/wp-content\/uploads\/2022\/07\/winupdatedate-768x508.png 768w, https:\/\/krebsonsecurity.com\/wp-content\/uploads\/2022\/07\/winupdatedate-782x518.png 782w\" sizes=\"(max-width: 749px) 100vw, 749px\"><\/p>\n<p><strong>Rapid7<\/strong>\u2018s <strong>Adam Barnett<\/strong> says January marks the fourth consecutive month where Microsoft has published zero-day vulnerabilities on Patch Tuesday without evaluating any of them as critical severity at time of publication. Today also saw the publication of nine critical remote code execution (RCE) vulnerabilities.<\/p>\n<p>The Microsoft flaws already seeing active attacks include <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21333\" target=\"_blank\" rel=\"noopener\">CVE-2025-21333<\/a>, <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21334\" target=\"_blank\" rel=\"noopener\">CVE-2025-21334<\/a> and, you guessed it\u2013 <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21335\" target=\"_blank\" rel=\"noopener\">CVE-2025-21335<\/a>. These are sequential because all reside in <strong>Windows Hyper-V<\/strong>, a component that is heavily embedded in modern <strong>Windows 11<\/strong> operating systems and used for security features including device guard and credential guard.<\/p>\n<p>Tenable\u2019s <strong>Satnam Narang<\/strong> says little is known about the in-the-wild exploitation of these flaws, apart from the fact that they are all \u201cprivilege escalation\u201d vulnerabilities. Narang said we tend to see a lot of elevation of privilege bugs exploited in the wild as zero-days in Patch Tuesday because it\u2019s not always initial access to a system that\u2019s a challenge for attackers as they have various avenues in their pursuit.<\/p>\n<p>\u201cAs elevation of privilege bugs, they\u2019re being used as part of post-compromise activity, where an attacker has already accessed a target system,\u201d he said. \u201cIt\u2019s kind of like if an attacker is able to enter a secure building, they\u2019re unable to access more secure parts of the facility because they have to prove that they have clearance. In this case, they\u2019re able to trick the system into believing they should have clearance.\u201d<span id=\"more-70070\"><\/span><\/p>\n<p>Several bugs addressed today earned CVSS (threat rating) scores of 9.8 out of a possible 10, including <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21298\" target=\"_blank\" rel=\"noopener\">CVE-2025-21298<\/a>, a weakness in Windows that could allow attackers to run arbitrary code by getting a target to open a malicious <strong>.rtf<\/strong> file, documents typically opened on Office applications like Microsoft Word. Microsoft has rated this flaw \u201cexploitation more likely.\u201d<\/p>\n<p><strong>Bob Hopkins<\/strong> at <strong>Immersive Labs<\/strong> called attention to the <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21311\" target=\"_blank\" rel=\"noopener\">CVE-2025-21311<\/a>, a 9.8 \u201ccritical\u201d bug in <strong>Windows NTLMv1<\/strong> (NT LAN Manager version 1), an older Microsoft authentication protocol that is still used by many organizations.<\/p>\n<p>\u201cWhat makes this vulnerability so impactful is the fact that it is remotely exploitable, so attackers can reach the compromised machine(s) over the internet, and the attacker does not need significant knowledge or skills to achieve repeatable success with the same payload across any vulnerable component,\u201d Hopkins wrote.<\/p>\n<p><strong>Kev Breen<\/strong> at Immersive points to an interesting flaw (<a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21210\" target=\"_blank\" rel=\"noopener\">CVE-2025-21210<\/a>) that Microsoft fixed in its full disk encryption suite <strong>Bitlocker<\/strong> that the software giant has dubbed \u201cexploitation more likely.\u201d Specifically, this bug holds out the possibility that in some situations the hibernation image created when one closes the laptop lid on an open Windows session may not be fully encrypted and could be recovered in plain text.<\/p>\n<p>\u201cHibernation images are used when a laptop goes to sleep and contains the contents that were stored in RAM at the moment the device powered down,\u201d Breen noted. \u201cThis presents a significant potential impact as RAM can contain sensitive data (such as passwords, credentials and PII) that may have been in open documents or browser sessions and can all be recovered with free tools from hibernation files.\u201d<\/p>\n<p>Tenable\u2019s Narang also highlighted a trio of vulnerabilities in <strong>Microsoft Access<\/strong> fixed this month and credited to Unpatched.ai, a security research effort that is aided by artificial intelligence looking for vulnerabilities in code. Tracked as <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21186\" target=\"_blank\" rel=\"noopener\">CVE-2025-21186<\/a>, <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21366\" target=\"_blank\" rel=\"noopener\">CVE-2025-21366<\/a>, and <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2025-21395\" target=\"_blank\" rel=\"noopener\">CVE-2025-21395<\/a>, these are remote code execution bugs that are exploitable if an attacker convinces a target to download and run a malicious file through social engineering. Unpatched.ai was also credited with discovering a flaw in the December 2024 Patch Tuesday release (<a href=\"https:\/\/msrc.microsoft.com\/update-guide\/en-US\/advisory\/CVE-2024-49142\" target=\"_blank\" rel=\"noopener\">CVE-2024-49142<\/a>).<\/p>\n<p>\u201cAutomated vulnerability detection using AI has garnered a lot of attention recently, so it\u2019s noteworthy to see this service being credited with finding bugs in Microsoft products,\u201d Narang observed. \u201cIt may be the first of many in 2025.\u201d<\/p>\n<p>If you\u2019re a Windows user who has automatic updates turned off and haven\u2019t updated in a while, it\u2019s probably time to play catch up. Please consider backing up important files and\/or the entire hard drive before updating. And if you run into any problems installing this month\u2019s patch batch, drop a line in the comments below, please.<\/p>\n<p>Further reading on today\u2019s patches from Microsoft:<\/p>\n<p><a href=\"https:\/\/www.tenable.com\/blog\/microsofts-january-2025-patch-tuesday-157-cves-cve-2025-21333-cve-2025-21334-cve-2025-21335\" target=\"_blank\" rel=\"noopener\">Tenable blog<\/a><\/p>\n<p><a href=\"https:\/\/isc.sans.edu\/forums\/diary\/Microsoft%20January%202025%20Patch%20Tuesday\/31590\/\" target=\"_blank\" rel=\"noopener\">SANS Internet Storm Center<\/a><\/p>\n<p><a href=\"https:\/\/www.askwoody.com\/\" target=\"_blank\" rel=\"noopener\">Ask Woody<\/a><\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    BrianKrebs<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/krebsonsecurity.com\/2025\/01\/microsoft-happy-2025-heres-161-security-updates\/\">Go to krebsonsecurity<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft: Happy 2025. Here\u2019s 161 Security Updates Microsoft today unleashed updates to plug a whopping 161 security vulnerabilities in Windows and related software, including three \u201czero-day\u201d weaknesses that are already under active attack. Redmond\u2019s inaugural Patch Tuesday of 2025 bundles more fixes than the company has shipped in one go since 2017. Rapid7\u2018s Adam Barnett [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[355,533,534,535,536,537,538,539,540,541,542,543,544,545,55,206,546,547,363,186,207,178,548,549,550,551],"tags":[72],"class_list":["post-1325","post","type-post","status-publish","format-standard","hentry","category-adam-barnett","category-bitlocker","category-bob-hopkins","category-cve-2024-49142","category-cve-2025-21186","category-cve-2025-21210","category-cve-2025-21298","category-cve-2025-21311","category-cve-2025-21333","category-cve-2025-21334","category-cve-2025-21335","category-cve-2025-21366","category-cve-2025-21395","category-kev-breen","category-krebsonsecurity","category-latest-warnings","category-microsoft-access","category-microsoft-patch-tuesday-january-2025","category-rapid7","category-satnam-narang","category-the-coming-storm","category-time-to-patch","category-unpatched-ai","category-windows-11","category-windows-hyper-v","category-windows-ntlmv1","tag-krebsonsecurity"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/1325"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=1325"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/1325\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=1325"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=1325"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=1325"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}