Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-31706 is a critical-severity Path Traversal (CWE-22) vulnerability in Vmware Vrealize Log Insight. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vRealize Log Insight appliance is affected by a directory traversal vulnerability tracked as CVE-2022-31706. The flaw, assigned CWE-22, permits an unauthenticated remote actor to inject arbitrary files onto the underlying operating system, which can be leveraged for remote code execution. It carries a CVSS 3.1 base score of 9.8 reflecting network-accessible attack complexity with no required credentials or user interaction.
An attacker can send specially crafted requests to the affected appliance to write malicious files and subsequently execute code, resulting in full compromise of the system confidentiality, integrity, and availability. The vulnerability is exploitable over the network without authentication, enabling any remote adversary to achieve these outcomes.
VMware’s advisory VMSA-2023-0001 addresses the issue and provides remediation guidance for impacted versions of vRealize Log Insight. Public exploit code demonstrating unauthenticated remote code execution has been published, and the CVE maintains an EPSS score of 0.9018, indicating sustained exploitation interest since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-53126
Vulnerability Data
The vRealize Log Insight contains a Directory Traversal Vulnerability. An unauthenticated, malicious actor can inject files into the operating system of an impacted appliance which can result in remote code execution.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Requires identification and authentication of users before allowing access to the vRealize Log Insight appliance, directly blocking the unauthenticated remote actor described in the CVE.
Validates all input to the appliance to reject path traversal sequences, preventing the malicious file injection that leads to RCE.
Performs integrity verification on files and software to detect unauthorized modifications resulting from successful directory traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.