CVE-2017-3775 : What You Need to Know

A vulnerability in certain Lenovo System x server BIOS/UEFI versions could allow an attacker to boot unsigned code when Secure Boot mode is enabled.

Understanding CVE-2017-3775

In instances where a system administrator activates the Secure Boot mode on certain Lenovo System x server BIOS/UEFI versions, there may be a flaw in authenticating signed code before its booting process. Consequently, if an attacker gains physical access to the system, they could potentially boot unsigned code.

What is CVE-2017-3775?

This CVE refers to a security flaw in Lenovo System x server BIOS/UEFI versions that fail to properly authenticate signed code when Secure Boot mode is enabled, potentially allowing unauthorized booting of unsigned code.

The Impact of CVE-2017-3775

The vulnerability could be exploited by an attacker with physical access to the system, enabling them to boot unsigned code, bypassing security measures and potentially leading to unauthorized system access or control.

Technical Details of CVE-2017-3775

This section provides detailed technical information about the vulnerability.

Vulnerability Description

Certain Lenovo System x server BIOS/UEFI versions do not authenticate signed code correctly when Secure Boot mode is activated, allowing potential booting of unsigned code by attackers with physical access.

Affected Systems and Versions

Affected products: Some Lenovo Flex System and Lenovo System x products
Vendor: Lenovo Group Ltd.
Affected versions: BIOS version varies by product

Exploitation Mechanism

The vulnerability arises when a system administrator enables Secure Boot mode on affected Lenovo System x server BIOS/UEFI versions, leading to the improper authentication of signed code and potential booting of unsigned code by unauthorized individuals.

Mitigation and Prevention

Protecting systems from CVE-2017-3775 requires immediate actions and long-term security practices.

Immediate Steps to Take

Disable Secure Boot mode on affected Lenovo System x servers to prevent unauthorized booting of unsigned code.
Implement physical security measures to restrict access to server hardware.

Long-Term Security Practices

Regularly update BIOS/UEFI firmware to patched versions that address the authentication flaw.
Conduct security audits to identify and mitigate vulnerabilities in server firmware.

Patching and Updates

Lenovo may release firmware updates addressing the authentication issue. Stay informed about security advisories and apply patches promptly.