Local privilege escalation via improper buffer restrictions
Published Mar 12, 2020 · Updated Aug 4, 2024
Buffer overflow in Intel NUC Firmware allows local users to escalate privileges through local access to an affected device. Intel identifies only improper buffer restrictions in the system firmware and does not disclose the affected firmware component, buffer operation, or attacker-controlled input. Exploitation requires existing local low-privileged access and can cross a security boundary to compromise confidentiality, integrity, and availability.
Summary
What happened
Buffer overflow in Intel NUC Firmware allows local users to escalate privileges through local access to an affected device. Intel identifies only improper buffer restrictions in the system firmware and does not disclose the affected firmware component, buffer operation, or attacker-controlled input. Exploitation requires existing local low-privileged access and can cross a security boundary to compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2020-0530
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Intel
- Product
- Intel NUC Firmware
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2020CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See advisory https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00343.html
What conditions does exploitation require?
What is affected?
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