dbcve.org
NetbackupApplication · Veritas

CVE-2022-36948

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 8.3.0.2 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
In Veritas NetBackup OpsCenter, a DOM XSS attack can occur. This affects 8.x through 8.3.0.2, 9.x through 9.0.0.1, 9.1.x through 9.1.0.1, and 10.

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 DOM-based Cross-Site Scripting (XSS) vulnerability exists in Veritas NetBackup OpsCenter's web interface. This client-side vulnerability allows attackers to inject malicious scripts through manipulation of the Document Object Model, which executes in victims' browsers when they interact with specially crafted URLs or content.

MitigationApply vendor-supplied patches for the affected versions (8.x-8.3.0.2, 9.x-9.0.0.1, 9.1.x-9.1.0.1, 10). Until patched, restrict network access to the OpsCenter web interface and consider implementing WAF rules to filter malicious request patterns.

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.0, < 8.3.0.2= 9.0= 9.0.0.1= 9.1.0.0

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 OpsCenter installation
    Locate the NetBackup OpsCenter installation directory or check running services for 'OpsCenter' or 'Veritas' processes
    Affected if OpsCenter software is not present on the system, the system is not affected by this specific OpsCenter vulnerability
  2. Determine OpsCenter version
    Access the OpsCenter web interface and navigate to 'Help' > 'About', or check the installation directory for a version file. Typical locations include /opt/opscenter or the installation root folder.
    Affected if The installed version falls within these ranges: 8.0 through 8.3.0.1, or exactly version 9.0, 9.0.0.1, or 9.1.0.0
  3. Confirm web interface is enabled
    Check if the OpsCenter web server service is running and accessible on the default ports (usually 80, 443, or 8443). Verify the /opscenter endpoint responds.
    Affected if The OpsCenter web interface is exposed and operational, making the DOM XSS exploitable through crafted URLs
  4. Verify current patch level
    Check the OpsCenter console or release notes for any installed patches. Compare your full version string including any patch numbers against the fixed versions (8.3.0.2, 9.0.0.2, 9.1.0.1, or 10.x)
    Affected if No vendor patches have been applied and the base version matches the affected ranges listed above

Your environment is affected if OpsCenter is installed with a version of 8.0-8.3.0.1, 9.0, 9.0.0.1, or 9.1.0.0 and the web interface is accessible.

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

Apply vendor-supplied patches for the affected versions (8.x-8.3.0.2, 9.x-9.0.0.1, 9.1.x-9.1.0.1, 10). Until patched, restrict network access to the OpsCenter web interface and consider implementing WAF rules to filter malicious request patterns.

Recommended fix Moderate confidence

Veritas NetBackup OpsCenter 10.0 or later

  1. 1. Review the current NetBackup OpsCenter installation and confirm the exact version by checking the About or version information in the OpsCenter console
  2. 2. Plan for upgrade during a maintenance window with appropriate backups of configuration data
  3. 3. Download Veritas NetBackup OpsCenter version 10.0 or later from Veritas Support (https://www.veritas.com/support)
  4. 4. Follow Veritas upgrade documentation for OpsCenter, ensuring proper backup of existing configuration
  5. 5. Apply the upgrade package following standard Veritas upgrade procedures
  6. 6. After upgrade, verify the OpsCenter web console is accessible and functional
  7. 7. Test that the DOM XSS vulnerability is remediated by confirming the fix addresses the reflected XSS in the OpsCenter web interface
Caveat Review Veritas compatibility lists and upgrade guide for any compatibility changes between 8.x/9.x and 10.x; ensure any custom scripts or integrations are tested

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

Fix this in Netbackup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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