dbcve.org
Enterprise VaultApplication · Veritas

CVE-2024-52942

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-24696. 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 · moderate confidence

A reflected Cross-Site Scripting (XSS) vulnerability in Veritas Enterprise Vault versions prior to 15.1 UPD882911 allows an authenticated remote attacker to inject malicious script into an HTTP request parameter when viewing archived content, which reflects back to the authenticated user without sanitization.

MitigationApply vendor patch 15.1 UPD882911 to all affected Enterprise Vault installations. As a temporary control, restrict access to the vulnerable archived content viewing functionality and implement input validation at the application or WAF level until patching is complete.

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. Check the installed Enterprise Vault version
    Use the Veritas Enterprise Vault Administration Console or run 'evversion.exe' from the Enterprise Vault installation directory to obtain the exact version number. Alternatively, check the Windows Programs and Features list for the installed version.
    Affected if The version is any release prior to 15.1 (for example, 14.x, 14.0, 14.1, 14.2, 14.3, or earlier) or if the version cannot be determined but is known to be an older installation.
  2. Confirm access to the archived content viewing functionality
    Log into the Enterprise Vault web interface (typically accessed via Outlook Web App integration or the Enterprise Vault Compliance Accelerator/Discovery Accelerator web portals) and navigate to the section where users view archived emails, documents, or other stored content.
    Affected if The user has an authenticated session and can access the archived content viewer interface, as this is where the vulnerable HTTP request parameter is processed.
  3. Identify if the HTTP parameter injection point is reachable
    While authenticated, observe the HTTP requests made when accessing archived content through the web interface. Look for URL parameters that contain user-supplied input (such as content IDs, folder IDs, or search parameters) that get reflected back in the response without encoding.
    Affected if The application reflects any portion of the HTTP request parameter back to the user's browser without proper HTML encoding, indicating the XSS vulnerability is present.
  4. Review Enterprise Vault configuration for the web components
    Check the Enterprise Vault configuration through the Administration Console to confirm which web components (EVOutlook, EVOfficeMail, Discovery Accelerator, or Compliance Accelerator) are installed and enabled.
    Affected if Any of the web-facing archived content viewing components are enabled and the version is prior to 15.1.

A user is affected if the installed Veritas Enterprise Vault version is prior to 15.1 and the archived content viewing functionality is accessible to authenticated users through the web interface.

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 vendor patch 15.1 UPD882911 to all affected Enterprise Vault installations. As a temporary control, restrict access to the vulnerable archived content viewing functionality and implement input validation at the application or WAF level until patching is complete.

Recommended fix High confidence

15.1 UPD882911

  1. Ensure you have a complete backup of your Enterprise Vault database and configuration before proceeding
  2. Download Enterprise Vault version 15.1 UPD882911 from the Veritas Support portal at www.veritas.com
  3. Review the Enterprise Vault 15.1 release notes and upgrade guide for any prerequisites
  4. Apply the upgrade to your Enterprise Vault installation following Veritas standard upgrade procedures
  5. After upgrade, verify the version shows 15.1 UPD882911 in the Enterprise Vault Administration Console
  6. Test that archived content viewing functions correctly post-upgrade

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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