CVE-2017-3775: Medium severity Lenovo Flex System X240 M5 Bios vulnerability

Published May 4, 2018
·
Updated

Some Lenovo System x server BIOS/UEFI versions, when Secure Boot mode is enabled by a system administrator, do not properly authenticate signed code before booting it. As a result, an attacker with physical access to the system could boot unsigned code.

Affected Software

22 affected components
Lenovo Flex System X240 M5 Bios<2.61
Lenovo Flex System X240 M5
Lenovo Flex System X280 X6 Bios<4.21
Lenovo Flex System X280 X6
Lenovo Flex System X480 X6 Bios<4.21
Lenovo Flex System X480 X6
Lenovo Flex System X880 Bios<4.21
Lenovo Flex System X880
Lenovo Nextscale Nx360 M5 Bios<2.61
Lenovo Nextscale Nx360 M5
Lenovo System X3250 M6 Bios<2.23
Lenovo System X3250 M6
Lenovo System X3500 M5 Bios<2.61
Lenovo System X3500 M5
Lenovo System X3550 M5 Bios<2.61
Lenovo System X3550 M5
Lenovo System X3650 M5 Bios<2.61
Lenovo System X3650 M5
Lenovo System X3850 X6 Bios<4.3
Lenovo System X3850 X6
Lenovo System X3950 X6 Bios<4.3
Lenovo System X3950 X6

Event History

May 4, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-3775?

CVE-2017-3775 has a medium severity due to its potential for an attacker to boot unsigned code with physical access.

2

How do I fix CVE-2017-3775?

To fix CVE-2017-3775, update the BIOS/UEFI to a version that addresses the issue and ensures proper authentication of signed code.

3

Which Lenovo products are affected by CVE-2017-3775?

CVE-2017-3775 affects several Lenovo System x server BIOS/UEFI versions including Flex System X240 M5, X280 X6, X480 X6, and others.

4

Is physically accessing the system necessary to exploit CVE-2017-3775?

Yes, exploiting CVE-2017-3775 requires physical access to the system to boot unsigned code.

5

What security risk does CVE-2017-3775 pose?

CVE-2017-3775 poses a risk of an attacker executing unauthorized code in a secured environment, compromising the integrity of the system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203