Privilege escalation via undisclosed BMC buffer overflow
Published Jun 9, 2021 · Updated Aug 4, 2024
Buffer overflow in Intel BMC firmware before 2.48.ce3e3bd2 allows remote authenticated users to escalate privileges via adjacent access. Intel identifies BMC firmware as the locus but has not disclosed the input, handler, buffer, or unchecked copy that triggers the overflow. Exploitation requires low-privileged authentication and adjacency to the management interface, and successful exploitation grants higher privileges while affecting BMC integrity or availability.
Summary
What happened
Buffer overflow in Intel BMC firmware before 2.48.ce3e3bd2 allows remote authenticated users to escalate privileges via adjacent access. Intel identifies BMC firmware as the locus but has not disclosed the input, handler, buffer, or unchecked copy that triggers the overflow. Exploitation requires low-privileged authentication and adjacency to the management interface, and successful exploitation grants higher privileges while affecting BMC integrity or availability.
The record
- CVE
- CVE-2020-24474
- Published
- Jun 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1068
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 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