Intel Confirms Alder Lake UEFI Code Leak

intel-alder-lake

BIOS hardware code for Intel Alder Lake processors was posted on 4chan

A few days ago , news broke online about the leak of Intel's Alder Lake UFEI code on 4chan, and that a copy was later published on GitHub.

Regarding the Intel case, it didn't immediately respond, but it has now confirmed the authenticity of the UEFI and BIOS firmware source code published by an unknown individual on GitHub. In total, 5,8 GB of code, utilities, documentation, blobs, and configurations related to firmware creation for systems with processors based on the Alder Lake microarchitecture, released in November 2021, were published.

Intel mentions that the related files have been in circulation for a few days and as such the news is being confirmed directly from Intel, which mentions that it wishes to point out that the matter does not imply new risks for the security of the chips and the systems in which are used, so it calls for not being alarmed about the case.

According to Intel, the leak occurred due to a third party and not as a result of a compromise in the company's infrastructure.

“Our proprietary UEFI code appears to have been leaked by a third party. We do not believe this will expose any new security vulnerabilities, as we do not rely on information obfuscation as a security measure. This code is covered by our bug bounty program within Project Circuit Breaker, and we encourage any researcher who can identify potential vulnerabilities to bring it to our attention through this program. We are reaching out to both customers and the security research community to keep them informed about this situation." — Intel spokesperson.

As such it is not specified who exactly became the source of the leak (since for example OEM equipment manufacturers and companies developing custom firmware had access to the tools to compile the firmware).

Regarding the case , it is mentioned that the analysis of the published file's contents revealed some specific Lenovo product tests and services ("Lenovo Feature Tag Test Information", "Lenovo String Service", "Lenovo Secure Suite", "Lenovo Cloud Service"), but Lenovo's involvement in the information leak also revealed utilities and libraries from Insyde Software, which develops firmware for OEMs, and the git log contains an email from one of the employees of LC Future Center , which produces laptops for various OEMs.

According to Intel, the open-source code does not contain confidential data or components that could contribute to the disclosure of new vulnerabilities. However, Mark Yermolov, who specializes in investigating the security of Intel platforms, revealed in the published file information about undocumented MSR logs (model-specific logs used for managing, tracking, and debugging microcode), information which falls under a non-disclosure agreement.

Additionally, a private key was found in the file, which is used to digitally sign the firmware , which can potentially be used to bypass Intel Boot Guard protection (the functionality of the key has not been confirmed, it may be a test key).

It is also mentioned that the code that went into open access covers the Project Circuit Breaker program, which involves the payment of rewards ranging from $500 to $100,000 for identifying security problems in firmware and Intel products (it is understood that researchers can receive rewards to report vulnerabilities discovered by using the contents of the leak).

"This code is covered by our bug bounty program within the Project Circuit Breaker campaign, and we encourage any researcher who can identify potential vulnerabilities to report them to us through this program," Intel added.

Finally, it is worth mentioning that regarding the data leak, the most recent change in the published code is dated September 30, 2022, so the information released is updated.


Add as preferred source in Google