{"id":34726,"date":"2024-08-07T00:03:48","date_gmt":"2024-08-06T22:03:48","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=34726"},"modified":"2024-08-07T00:16:40","modified_gmt":"2024-08-06T22:16:40","slug":"attention-microsofts-uefi-certificate-expires-on-oct-19-2026-secure-boot-affected","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2024\/08\/07\/attention-microsofts-uefi-certificate-expires-on-oct-19-2026-secure-boot-affected\/","title":{"rendered":"Attention: Microsoft's UEFI certificate expires on Oct. 19, 2026 – Secure Boot affected"},"content":{"rendered":"

\"Windows\"[German<\/a>]I'm posting a topic here in the blog that still has \"a few days to go\" but could have very unpleasant consequences. In the fall of 2026, a certificate in Windows will expire, which ensures that Secure Boot can be executed in the UEFI. At that time, the certificate was valid for 15 years, but all machines that are not updated will no longer be able to start in Secure Boot mode by the deadline.<\/p>\n

<\/p>\n

Windows and the Secure Boot CA<\/h2>\n

\"\"I came across the following tweet<\/a> by Gunnar Haslinger a few days ago and am posting it here on the blog today for your information.<\/p>\n

\"Microsoft<\/a><\/p>\n

The issue at hand is described in a few words. Microsoft uses a UEFI certificate that is stored in a database. The Secure Boot propagated by Microsoft in Windows accesses this certificate to check its integrity. Secure Boot therefore depends on the validity of this certificate. If the certificate in the bootmgfw.efi<\/em> file on the UEFI partition is invalid, the machine can no longer start in Secure Boot.<\/p>\n

The Windows Production PCA 2011<\/h3>\n

However, the certificate used so far was issued a long time ago, specifically in 2011, and will expire on Monday, October 19, 2026, after 15 years of validity. Machines that use Secure Boot and have not been updated by this date will no longer be able to start. This is likely to affect Windows systems in particular, which do not receive updates via the internet.<\/p>\n

The Black Lotus problem<\/h3>\n

With the May 2023 security updates, Microsoft has attempted to close the vulnerability in Secure Boot that is being exploited by the hacker group BlackLotus and its UEFI bootkit. The vulnerability CVE-2023-24932<\/a> relates to a vulnerability in the Secure Boot used in Windows operating systems, which allows untrusted software to be executed during the boot process.<\/p>\n

I wrote about this topic in the blog post BlackLotus UEFI bootkit bypasses Secure Boot in Windows 11<\/a>. And in the German article Windows und das (BlackLotus) Secure Boot-Desaster: Wie ist bei euch der Status?<\/a> I discussed the problem of administrators having to intervene manually to secure the Secure Boot.<\/p>\n

New Windows UEFI CA 2023<\/h2>\n

To solve the problem with the expiring certificate, Microsoft has provided the update KB5025885 for protection (see KB5025885: Secure boot hardening against vulnerability CVE-2023-24932 (Black Lotus)<\/a> from May 2023). There is also a support article on update KB5025885<\/a>, which contains the advice to install the Windows security update of July 9, 2024 or a later cumulative security update under Windows in order to provide the required safeguards against Black Lotus.<\/p>\n

This blog post also contains a note that a new certificate (Windows UEFI CA 2023) will be provided with the update to replace the old Windows Production PCA 2011. Administrators in enterprise environments will find corresponding instructions in the support article for KB5025885<\/a> as to which additional steps need to be carried out. Anyone who provides their Windows systems with protection against Black Lotus and the Secure Boot vulnerability CVE-2023-24932<\/a> is also prepared for the scenario of an expiring UEFI certificate outlined above.<\/p>\n

In 2024, Microsoft then carry out various hardening measures, which I outlined in the blog post Update on Windows hardening in 2024\/2025 \u2013 March 2024<\/a>.<\/p>\n

Similar articles:
\n<\/strong>BlackLotus UEFI bootkit bypasses Secure Boot in Windows 11<\/a>
\nKB5025885: Secure boot hardening against vulnerability CVE-2023-24932 (Black Lotus)<\/a>
\nUpdate on Windows hardening in 2024\/2025 \u2013 March 2024<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]I'm posting a topic here in the blog that still has \"a few days to go\" but could have very unpleasant consequences. In the fall of 2026, a certificate in Windows will expire, which ensures that Secure Boot can be … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[580,2],"tags":[69,194],"class_list":["post-34726","post","type-post","status-publish","format-standard","hentry","category-security","category-windows","tag-security","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34726","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=34726"}],"version-history":[{"count":3,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34726\/revisions"}],"predecessor-version":[{"id":34730,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34726\/revisions\/34730"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=34726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=34726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=34726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}