dbcve.org
Infoscale Operations ManagerApplication · Veritas

CVE-2023-38404

HIGH · 8.8 CVSS v3.1 Published 2023-07-17
Fix available
A fix is available. Upgrade to 8.0.0.410 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The XPRTLD web application in Veritas InfoScale Operations Manager (VIOM) before 8.0.0.410 allows an authenticated attacker to upload all types of files to the server. An authenticated attacker can then execute the malicious file to perform command execution on the remote server.

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 · high confidence

The XPRTLD web application in Veritas InfoScale Operations Manager (VIOM) versions prior to 8.0.0.410 contains an unrestricted file upload vulnerability. An authenticated attacker can upload files of any type to the server and subsequently execute them to achieve remote command execution.

MitigationUpgrade Veritas InfoScale Operations Manager to version 8.0.0.410 or later. If immediate patching is not possible, restrict the authenticated user permissions and implement strict file type validation (allowlist approach) on the upload functionality.

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
Infoscale Operations ManagerApplication
Affected:>= 7.0.0, < 8.0.0.410

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Veritas InfoScale Operations Manager installation
    Locate the VIOM installation directory or check installed programs/services for Veritas InfoScale Operations Manager. Common locations include /opt/VRTSvcs or Windows Program Files directories.
    Affected if VIOM is installed on the system
  2. Determine installed VIOM version
    Check the version of Veritas InfoScale Operations Manager using the product's built-in version information utility, About dialog, or by examining version files in the installation directory.
    Affected if The installed version is 7.0.0 or higher but lower than 8.0.0.410
  3. Verify XPRTLD web application status
    Check if the XPRTLD web service is running and accessible. This is typically a web component on ports 14171 or similar admin ports. Attempt to access the web interface or check service status.
    Affected if The XPRTLD web application is running and accepts connections
  4. Confirm authentication is enabled for the web interface
    Verify that the web-based management interface allows user authentication. Check whether local or remote authentication providers (LDAP, Active Directory) are configured and active.
    Affected if User authentication is enabled for the VIOM web console

The environment is affected if the installed VIOM version falls within 7.0.0 to before 8.0.0.410 and the XPRTLD web interface is accessible with authentication enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.0.0.410 or later
Fixed in 8.0.0.410
Interim mitigation

Upgrade Veritas InfoScale Operations Manager to version 8.0.0.410 or later. If immediate patching is not possible, restrict the authenticated user permissions and implement strict file type validation (allowlist approach) on the upload functionality.

Recommended fix High confidence

8.0.0.410 or later

  1. 1. Identify all Veritas InfoScale Operations Manager installations in the environment running versions 7.0.0 through 8.0.0.409.
  2. 2. Download Veritas InfoScale Operations Manager version 8.0.0.410 or later from the official Veritas download site.
  3. 3. Review the Veritas upgrade documentation for VIOM before performing the upgrade.
  4. 4. Schedule a maintenance window to minimize business impact.
  5. 5. Perform a full backup of the current VIOM configuration and data.
  6. 6. Execute the upgrade following Veritas official upgrade procedures.
  7. 7. Verify the upgrade was successful by checking the version number in the administration console.
  8. 8. Validate that the XPRTLD web application is functioning correctly after the upgrade.
Caveat Review Veritas release notes for version 8.0.0.410 for any configuration or compatibility changes from previous versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Infoscale Operations Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38404 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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