dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-52943

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 15.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
An issue was discovered in Veritas Enterprise Vault before 15.1 UPD882911, ZDI-CAN-24697. It allows an authenticated remote attacker to inject a parameter into an HTTP request, allowing for Cross-Site Scripting (XSS) while viewing archived content. This could reflect back to an authenticated user without sanitization if executed by that user.

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

Veritas Enterprise Vault before version 15.1 UPD882911 contains a reflected Cross-Site Scripting (XSS) vulnerability. An authenticated attacker can inject malicious parameters into HTTP requests when viewing archived content, which then reflects back unsanitized to the authenticated user, allowing arbitrary JavaScript execution in the user's browser context.

MitigationApply the vendor patch (15.1 UPD882911) to remediate the XSS vulnerability. As a temporary control, restrict administrative access to the Enterprise Vault web interface and monitor for suspicious parameter injection patterns in HTTP requests.

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
Enterprise VaultApplication
Affected:< 15.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

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

  1. Determine Enterprise Vault version
    Locate the installed Enterprise Vault version through the Veritas installed programs list, EVAbout.exe utility, or the Vault Administration Console (VAC) under Server Properties. Compare the version number to 15.1.
    Affected if The installed version is below 15.1 (for example, 14.x, 14.3, 14.4, etc.) or version 15.0/15.0.x without patch UPD882911.
  2. Verify patch UPD882911 is applied
    Check the installed updates or patch level for Enterprise Vault. This can be verified through the VAC under Server Properties > Updates, or by reviewing the installed hotfixes/patches on the server.
    Affected if Patch UPD882911 is not listed among installed updates, indicating the vulnerability remains unpatched.
  3. Confirm web interface is accessible
    Verify that the Enterprise Vault web interface (EVDashboard, Outlook Web App integration, or the main EV web portal) is reachable via HTTP/HTTPS. Check IIS site bindings and firewall rules.
    Affected if The web interface is accessible and the server is network-reachable, providing the attack surface for XSS injection.
  4. Check if external or untrusted authentication is possible
    Review the authentication configuration for the Enterprise Vault web applications. Determine if the web interface permits login from users outside the trusted internal network.
    Affected if The web interface allows authentication by users who are not fully trusted, or the EV web portal accepts user-supplied parameters when rendering archived content.

You are affected if Enterprise Vault is installed with a version below 15.1 and patch UPD882911 has not been applied, with the web interface accessible to authenticated users who can view archived content.

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 15.1 or later
Fixed in 15.1
Interim mitigation

Apply the vendor patch (15.1 UPD882911) to remediate the XSS vulnerability. As a temporary control, restrict administrative access to the Enterprise Vault web interface and monitor for suspicious parameter injection patterns in HTTP requests.

Recommended fix High confidence

Enterprise Vault 15.1 with update UPD882911

  1. 1. Identify the current Enterprise Vault version by checking the version in the Administration Console or running the version check command
  2. 2. Download Enterprise Vault version 15.1 with update UPD882911 from the Veritas Support website (www.veritas.com)
  3. 3. Review the Veritas Enterprise Vault Upgrade Guide for version 15.1 to understand prerequisites and compatibility requirements
  4. 4. Create a complete backup of the Enterprise Vault database and configuration
  5. 5. Execute the upgrade installer for version 15.1 following the documented upgrade procedures
  6. 6. After upgrade, verify that the version shows 15.1 with UPD882911 applied

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

Fix this in Enterprise Vault Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52943 — 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-2024-52943 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