Remote code execution via hidden request backdoor
Published Dec 14, 2022 · Updated Apr 21, 2025
Hidden functionality in vSphere_selfuse 2019-07-22 allows remote attackers to execute code through the request package. The request package contains a hidden backdoor that executes attacker-supplied code and exposes sensitive user information and digital-currency keys. The published assessment requires no privileges or user interaction and reports confidentiality, integrity, and availability impact; no fixed version is identified.
Summary
What happened
Hidden functionality in vSphere_selfuse 2019-07-22 allows remote attackers to execute code through the request package. The request package contains a hidden backdoor that executes attacker-supplied code and exposes sensitive user information and digital-currency keys. The published assessment requires no privileges or user interaction and reports confidentiality, integrity, and availability impact; no fixed version is identified.
The record
- CVE
- CVE-2022-46996
- Published
- Dec 14, 2022
- Updated
- Apr 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-912
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- GitHub issue 39proof of concept · unverified
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