dbcve.org
NetbackupApplication · Veritas

CVE-2021-41570

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to 9.0.0.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
Veritas NetBackup OpsCenter Analytics 9.1 allows XSS via the NetBackup Master Server Name, Display Name, NetBackup User Name, or NetBackup Password field during a Settings/Configuration Add operation.

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 NetBackup OpsCenter Analytics 9.1 contains a stored Cross-Site Scripting (XSS) vulnerability. The application fails to properly sanitize user input in the NetBackup Master Server Name, Display Name, NetBackup User Name, and NetBackup Password fields during Settings/Configuration Add operations, allowing authenticated users to inject malicious JavaScript code that executes in the browsers of other users viewing this data.

MitigationImplement proper input validation and output encoding for all user-supplied fields in the affected configuration forms. Apply context-appropriate encoding when displaying these values to prevent script execution.

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
NetbackupApplication
Affected:>= 8.2.0, < 9.0.0.1= 9.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. Identify NetBackup OpsCenter Analytics version
    Check the installed version of NetBackup OpsCenter Analytics component. On the server, you can typically find version information in the About section of the OpsCenter web interface, or by checking installed packages using the system package manager. Look for files or registry entries related to OpsCenter Analytics.
    Affected if The installed version is 8.2.0 through 9.0.0.0 (inclusive), or exactly version 9.1.
  2. Confirm OpsCenter Analytics is deployed
    Verify that the OpsCenter Analytics component is installed and running. Access the OpsCenter web console and navigate to the Analytics section to confirm the component is active.
    Affected if OpsCenter Analytics is installed and accessible.
  3. Check for Settings/Configuration access
    Determine if your user account has permissions to access the Settings or Configuration menu options in OpsCenter Analytics where Add operations can be performed.
    Affected if You have authenticated access to Settings/Configuration Add operations.
  4. Inspect stored configuration data
    Examine the NetBackup Master Server Name, Display Name, NetBackup User Name, and NetBackup Password fields in the configuration. These fields are typically found in Settings/Configuration > Add NetBackup Master Server or similar menu paths. Review the stored values for any unexpected characters or patterns that could indicate injected script tags (such as <script>, javascript:, onload, onerror).
    Affected if The configuration fields contain unsanitized user-supplied input including script tags or event handlers.

You are affected if OpsCenter Analytics is installed and your version falls within 8.2.0 to 9.0.0.0 or equals 9.1, AND the vulnerable configuration fields contain unsanitized input.

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.

From vendor data
Upgrade available Upgrade to 9.0.0.1 or later
Fixed in 9.0.0.1
Interim mitigation

Implement proper input validation and output encoding for all user-supplied fields in the affected configuration forms. Apply context-appropriate encoding when displaying these values to prevent script execution.

Fix this in Netbackup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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