Sensitive data disclosure via shader register name read
Published Apr 15, 2020 · Updated Sep 30, 2024
Information disclosure in Oracle VM VirtualBox Core before 5.2.40, 6.0.20, or 6.1.6 allows local users to read sensitive data. The shader_glsl_get_register_name function fails to validate user-supplied data and reads past the end of an allocated buffer. Exploitation requires high-privileged code in a guest; the read can disclose sensitive information and can be combined with other flaws for hypervisor code execution.
Summary
What happened
Information disclosure in Oracle VM VirtualBox Core before 5.2.40, 6.0.20, or 6.1.6 allows local users to read sensitive data. The shader_glsl_get_register_name function fails to validate user-supplied data and reads past the end of an allocated buffer. Exploitation requires high-privileged code in a guest; the read can disclose sensitive information and can be combined with other flaws for hypervisor code execution.
The record
- CVE
- CVE-2020-2741
- Published
- Apr 15, 2020
- Updated
- Sep 30, 2024
- Vendor
- Oracle Corporation
- Product
- Oracle VM VirtualBox
- Classifications
- T1203
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Sep 30, 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=unspecified <5.2.40
- Affected versionversion=unspecified <6.0.20
- Affected versionversion=unspecified <6.1.6
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