Local memory corruption via license configuration overflow
Published Feb 8, 2021 · Updated Aug 3, 2024
A local buffer overflow in HPE Apollo 70 System BMC firmware before 3.0.14.0 allows local users to corrupt process memory. The libifc.so WebSetLicenseCfg function writes license-configuration input beyond a buffer, but HPE has not disclosed the affected field or copy operation. Low-privileged local access is required, and HPE has not specified whether exploitation causes a crash, code execution, or another consequence.
Summary
What happened
A local buffer overflow in HPE Apollo 70 System BMC firmware before 3.0.14.0 allows local users to corrupt process memory. The libifc.so WebSetLicenseCfg function writes license-configuration input beyond a buffer, but HPE has not disclosed the affected field or copy operation. Low-privileged local access is required, and HPE has not specified whether exploitation causes a crash, code execution, or another consequence.
The record
- CVE
- CVE-2021-25171
- Published
- Feb 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Hewlett Packard Enterprise (HPE)
- Product
- BMC Firmware for HPE Apollo 70 HPC Server
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Prior to Version 3.0.14.0
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