Some Lenovo System x server BIOS/UEFI versions, when Secure Boot mode is enabled by a system administrator, do not properly authenticate sig
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.
- Published
- May 4, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 17th percentile
- CWE
- CWE-287
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| lenovo | flex system x240 m5 bios | cpe:2.3:o:lenovo:flex_system_x240_m5_bios |
| lenovo | flex system x240 m5 | cpe:2.3:h:lenovo:flex_system_x240_m5 |
| lenovo | flex system x280 x6 bios | cpe:2.3:o:lenovo:flex_system_x280_x6_bios |
| lenovo | flex system x280 x6 | cpe:2.3:h:lenovo:flex_system_x280_x6 |
| lenovo | flex system x480 x6 bios | cpe:2.3:o:lenovo:flex_system_x480_x6_bios |
| lenovo | flex system x480 x6 | cpe:2.3:h:lenovo:flex_system_x480_x6 |
| lenovo | flex system x880 bios | cpe:2.3:o:lenovo:flex_system_x880_bios |
| lenovo | flex system x880 | cpe:2.3:h:lenovo:flex_system_x880 |
| lenovo | nextscale nx360 m5 bios | cpe:2.3:o:lenovo:nextscale_nx360_m5_bios |
| lenovo | nextscale nx360 m5 | cpe:2.3:h:lenovo:nextscale_nx360_m5 |
| lenovo | system x3250 m6 bios | cpe:2.3:o:lenovo:system_x3250_m6_bios |
| lenovo | system x3250 m6 | cpe:2.3:h:lenovo:system_x3250_m6 |
and 10 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo flex system x240 m5 biosbefore 2.61
- lenovo flex system x280 x6 biosbefore 4.21
- lenovo flex system x480 x6 biosbefore 4.21
- lenovo flex system x880 biosbefore 4.21
- lenovo nextscale nx360 m5 biosbefore 2.61
- lenovo system x3250 m6 biosbefore 2.23
- lenovo system x3500 m5 biosbefore 2.61
- lenovo system x3550 m5 biosbefore 2.61
- lenovo system x3650 m5 biosbefore 2.61
- lenovo system x3850 x6 biosbefore 4.3
- lenovo system x3950 x6 biosbefore 4.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.
Lenovo Group Ltd. Some Lenovo Flex System and Lenovo System x products
- Affected BIOS version varies by productaffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-8226The BIOS in Lenovo System X M5, M6, and X6 systems allows administrators to cause a denial of service via updating a UEFI data structure.19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.