Vrealize Log InsightApplication · VMware
CVE-2022-31703
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencevRealize Log Insight versions prior to the patch contain a directory traversal vulnerability. An unauthenticated, remote attacker can inject arbitrary files into the operating system of the affected appliance, potentially achieving remote code execution by writing malicious scripts or executables to locations where they will be invoked.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Vrealize Log InsightApplication
<= 8.10.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if vRealize Log Insight is deployedLocate the vRealize Log Insight virtual appliance or installation in your environment. Check for processes named 'log-insight' or services listening on typical vRLI ports (443, 9543).Affected if vRealize Log Insight is installed and running in your environment.
-
Determine the installed versionAccess the vRealize Log Insight web interface and navigate to the About page, or run 'vli-version' or similar version command from the appliance console. Compare the version number to 8.10.1.Affected if The installed version is 8.10.1 or any version prior to the patched release.
-
Verify if unauthenticated access is permittedConfirm whether the vRealize Log Insight web interface or API endpoints are accessible to unauthenticated network attackers. Check firewall rules and access control lists governing the appliance.Affected if The management interface is exposed to untrusted networks without authentication restrictions.
-
Inspect for suspicious uploaded filesReview the /storage/var/loginsight/upload/ directory and other writable paths on the appliance for unexpected or malicious files, particularly scripts or executables that were not intentionally deployed.Affected if Unexpected files exist in upload directories or system paths that were not placed by legitimate administrators.
If vRealize Log Insight version 8.10.1 or earlier is running and its interface is network-accessible to unauthenticated users, the environment is vulnerable to directory traversal and arbitrary file injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor-supplied patch for CVE-2022-31703. As an interim measure, restrict network access to vRealize Log Insight interfaces using network segmentation or a WAF to limit unauthenticated attack surface.
vRealize Log Insight 8.10.2
- Download vRealize Log Insight 8.10.2 or later from the VMware Customer Connect portal
- Ensure you have a valid backup of the vRealize Log Insight appliance and its data
- Schedule a maintenance window as the upgrade may require brief downtime
- Review VMware documentation for upgrade prerequisites specific to your deployment type (embedded or external)
- Deploy the upgrade following VMware's standard upgrade procedures for vRealize Log Insight
- After upgrade, verify the appliance is operational and the web interface is accessible
- Confirm the version shows 8.10.2 or later to verify the patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vrealize Log Insight
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31703 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data