Local data disclosure via stale vector registers
Published Jan 28, 2020 · Updated Aug 4, 2024
Vector register sampling in some Intel Processors allows local users to infer partial vector data from prior software execution. Under specific microarchitectural conditions, data previously read from vector registers propagates into unused store-buffer portions that MDS or TAA methods can sample. Exploitation requires local low-privileged code on an MDS- or TAA-affected processor and exposes only upper vector-register bits from prior software or a sibling hyperthread.
Summary
What happened
Vector register sampling in some Intel Processors allows local users to infer partial vector data from prior software execution. Under specific microarchitectural conditions, data previously read from vector registers propagates into unused store-buffer portions that MDS or TAA methods can sample. Exploitation requires local low-privileged code on an MDS- or TAA-affected processor and exposes only upper vector-register bits from prior software or a sibling hyperthread.
The record
- CVE
- CVE-2020-0548
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Processors
- Classifications
- CWE-404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 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 references
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