Firmware compromise via Self Boot Engine code injection
Published May 26, 2021 · Updated Sep 16, 2024
Code injection in IBM Power Systems Power9 Self Boot Engine allows remote authenticated users to compromise host firmware integrity. The Self Boot Engine accepts malicious code from a compromised service processor without enforcing the host firmware signature verification boundary. Root access to the service processor is required, and the resulting firmware compromise is not detectable through TPM attestation.
Summary
What happened
Code injection in IBM Power Systems Power9 Self Boot Engine allows remote authenticated users to compromise host firmware integrity. The Self Boot Engine accepts malicious code from a compromised service processor without enforcing the host firmware signature verification boundary. Root access to the service processor is required, and the resulting firmware compromise is not detectable through TPM attestation.
The record
- CVE
- CVE-2021-20487
- Published
- May 26, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Power Systems
- Classifications
- CWE-347, T1542.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 26, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=FW930
- Affected versionversion=FW940
- Affected versionversion=FW941
- Affected versionversion=OP940
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