Physical code execution via unsafe OpenSSL configuration
Published Apr 29, 2022 · Updated Aug 3, 2024
Code execution in NVIDIA Omniverse Nucleus before 2021.3.2 and Cache before 2021.3.0 allows physically proximate attackers to run code. The public record identifies an unsafe OpenSSL configuration but does not disclose the affected setting or how attacker-controlled input reaches code execution. Exploitation requires physical access and user interaction on an affected Windows installation; successful execution can read or alter data and interrupt the service.
Summary
What happened
Code execution in NVIDIA Omniverse Nucleus before 2021.3.2 and Cache before 2021.3.0 allows physically proximate attackers to run code. The public record identifies an unsafe OpenSSL configuration but does not disclose the affected setting or how attacker-controlled input reaches code execution. Exploitation requires physical access and user interaction on an affected Windows installation; successful execution can read or alter data and interrupt the service.
The record
- CVE
- CVE-2022-28198
- Published
- Apr 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA Omniverse Cache
- Classifications
- CWE-706
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2022CVE 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=All versions prior to 2021.3.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