dbcve.org
Data InsightApplication · Veritas

CVE-2024-47854

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to 7.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 XSS vulnerability was discovered in Veritas Data Insight before 7.1. It allows a remote attacker to inject an arbitrary web script into an HTTP request that 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 XSS vulnerability in Veritas Data Insight before version 7.1 allows remote attackers to inject arbitrary JavaScript into HTTP request parameters. These parameters reflect back to the authenticated user without sanitization, causing the malicious script to execute in the user's browser session.

MitigationUpgrade to Veritas Data Insight 7.1 or later to obtain the vendor patch. As a compensating control, implement output encoding/sanitization on affected endpoints and educate users to avoid clicking untrusted links.

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
Data InsightApplication
Affected:>= 6.0, < 7.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Veritas Data Insight installation
    Check common installation paths (e.g., C:\Program Files\Veritas\Data Insight or /opt/veritas/data_insight) and look for the installation directory. Also check for the Data Insight service in Windows Services or running processes.
    Affected if Veritas Data Insight is found on the system
  2. Determine installed version
    Check the version of Data Insight by inspecting the application GUI login page footer, or check the installer/version file in the installation directory (often in a file named version.info, about.html, or in the Windows registry under HKLM\Software\Veritas\Data Insight).
    Affected if Version cannot be determined or is not visible, but product is present in version range 6.0 to < 7.1
  3. Compare version against affected range
    Review the installed version number. Affected versions are >= 6.0 and < 7.1. Any version in this range (including 6.0, 6.0.1, 6.1, 6.2, 6.3, 7.0) is vulnerable.
    Affected if Installed version falls within 6.0 <= version < 7.1
  4. Verify web interface is accessible
    Confirm the Data Insight web interface is running by accessing the login URL (typically https://hostname:8080 or https://hostname/idi). The presence of the unauthenticated or authenticated web portal confirms the attack surface.
    Affected if Web interface is accessible and version is in affected range

If Veritas Data Insight version is 6.0 or higher but lower than 7.1, the environment is vulnerable to this reflected XSS and the user is affected.

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

Upgrade to Veritas Data Insight 7.1 or later to obtain the vendor patch. As a compensating control, implement output encoding/sanitization on affected endpoints and educate users to avoid clicking untrusted links.

Recommended fix High confidence

Data Insight 7.1

  1. Verify current Data Insight version by checking the About section in the administration console
  2. Review Veritas Data Insight 7.1 release notes and upgrade documentation for your current version
  3. Take a complete backup of the Data Insight database and configuration
  4. Schedule a maintenance window to minimize business impact
  5. Download Data Insight 7.1 from Veritas Support website
  6. Follow Veritas upgrade documentation to install version 7.1
  7. After upgrade, verify the application is running correctly
  8. Log in and confirm the XSS vulnerability is no longer present by testing the previously vulnerable parameter
Caveat Review 7.1 release notes for any configuration or feature changes from your current 6.x version; some settings may need adjustment

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

Fix this in Data Insight 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-2024-47854 — 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-47854 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