dbcve.org
Ediscovery PlatformApplication · Veritas

CVE-2024-27283

HIGH · 7.2 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 10.2.5 or later.
See remediation →
78/100
Remediation priority · High
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
A vulnerability was discovered in Veritas eDiscovery Platform before 10.2.5. The application administrator can upload potentially malicious files to arbitrary locations on the server on which the application is installed.

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

This is an authenticated path traversal vulnerability in Veritas eDiscovery Platform's file upload functionality. An application administrator can bypass path validation to upload files to arbitrary server locations, potentially placing malicious files in web-accessible directories for remote code execution.

MitigationApply vendor patch to version 10.2.5 or later. Restrict administrative access and monitor for suspicious upload activity in audit logs.

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
Ediscovery PlatformApplication
Affected:< 10.2.5

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the installed Veritas eDiscovery Platform version
    Access the platform's administrative interface or check the installation directory for version information. Typically found in the system settings, About section, or installation logs.
    Affected if The installed version is lower than 10.2.5 (e.g., 10.2.4, 10.2.3, earlier versions)
  2. Confirm file upload functionality is enabled
    Navigate to the eDiscovery Platform administrative console and locate the document/file upload or import feature used for evidence collection.
    Affected if File upload modules are accessible to application administrators
  3. Verify administrative access exists
    Check user account permissions within the platform to determine if any accounts have Application Administrator privileges.
    Affected if Any administrative-level accounts exist in the system (required for authenticated exploitation)
  4. Review audit logs for anomalous upload activity
    Access the platform's audit or logging subsystem and search for file upload events, particularly those involving paths outside expected upload directories.
    Affected if Audit logs show uploads to unexpected directory paths or unusual file placements

You are affected if your Veritas eDiscovery Platform version is below 10.2.5 and the file upload functionality is accessible to administrators.

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

Apply vendor patch to version 10.2.5 or later. Restrict administrative access and monitor for suspicious upload activity in audit logs.

Recommended fix High confidence

10.2.5

  1. Verify current eDiscovery Platform version through the administration console or system information
  2. Schedule a maintenance window for the upgrade process
  3. Review Veritas eDiscovery Platform upgrade documentation for 10.2.5
  4. Backup the current installation including database and configuration files
  5. Upgrade the eDiscovery Platform installation to version 10.2.5
  6. Verify the upgrade was successful by checking the version in the administration console
  7. Test core functionality to ensure the platform operates correctly after upgrade

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

Fix this in Ediscovery Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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