Firmware protection bypass via retained manufacturing mode
Published Feb 16, 2024 · Updated Jul 23, 2025
Improper manufacturing configuration in Lenovo ThinkSystem SR670 V2 before U8E126I-2.20 allows attackers to alter firmware protections. Intel SPS End of Manufacturing was not executed, leaving Manufacturing Mode enabled and permitting changes to Boot Guard integrity and SPS settings. Exploitation requires privileged logical host access or physical access to server internals, while Platform Firmware Resiliency limits the resulting firmware tampering.
Summary
What happened
Improper manufacturing configuration in Lenovo ThinkSystem SR670 V2 before U8E126I-2.20 allows attackers to alter firmware protections. Intel SPS End of Manufacturing was not executed, leaving Manufacturing Mode enabled and permitting changes to Boot Guard integrity and SPS settings. Exploitation requires privileged logical host access or physical access to server internals, while Platform Firmware Resiliency limits the resulting firmware tampering.
The record
- CVE
- CVE-2024-23591
- Published
- Feb 16, 2024
- Updated
- Jul 23, 2025
- Vendor
- Lenovo
- Product
- ThinkSystem SR670 V2
- Classifications
- CWE-1269, T1562.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 16, 2024CVE publishedPublication date reported by the CVE source.
- Jul 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <U8E126I-2.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo