Information disclosure via hard-coded BMC key
Published Feb 17, 2021 · Updated Aug 4, 2024
Use of a hard-coded key in Intel BMC firmware before 2.47 allows local users to disclose protected information. Intel identifies a hard-coded BMC key but has not disclosed where the key is stored, what it protects, or how its use exposes data. Exploitation requires authenticated local access and affects confidentiality only, with no reported integrity or availability impact.
Summary
What happened
Use of a hard-coded key in Intel BMC firmware before 2.47 allows local users to disclose protected information. Intel identifies a hard-coded BMC key but has not disclosed where the key is stored, what it protects, or how its use exposes data. Exploitation requires authenticated local access and affects confidentiality only, with no reported integrity or availability impact.
The record
- CVE
- CVE-2020-12376
- Published
- Feb 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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