dbcve.org
NetbackupApplication · Veritas

CVE-2022-36952

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 8.3.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Veritas NetBackup OpsCenter, a hard-coded credential exists that could be used to exploit the underlying VxSS subsystem. 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

Veritas NetBackup OpsCenter contains a hard-coded credential (backdoor) that can be used to authenticate to the underlying VxSS (Veritas Security Services) subsystem. An attacker with knowledge of this credential can potentially gain unauthorized access to the system without needing valid user credentials.

MitigationApply vendor patches for CVE-2022-36952 or upgrade to a patched version. If immediate patching is not possible, restrict network access to OpsCenter services and implement monitoring for unauthorized access attempts.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 OpsCenter version
    Run command: /opt/VRTSopscenter/bin/opscenter -version or check /opt/VRTSopscenter/version file
    Affected if Version falls within >= 8.0 and < 8.3.0.2, or equals 9.0, or equals 9.1.0.0
  2. Confirm OpsCenter service is running
    Run command: ps -ef | grep -i opscenter or systemctl status VRTSopscenter
    Affected if OpsCenter process is running on affected version
  3. Review authentication logs for unauthorized access
    Examine log files in /opt/VRTSopscenter/logs/ for failed login attempts or suspicious VxSS authentication events
    Affected if Logs show authentication activity from unknown sources or unusual VxSS authentication patterns
  4. Check for presence of hard-coded credential account
    Inspect /opt/VRTSopscenter/conf/opscenter.conf or examine VxSS configuration files for embedded credentials
    Affected if Hard-coded credentials are found in configuration files

Environment is affected if OpsCenter version is 8.0 through 8.3.0.1, or exactly 9.0 or 9.1.0.0, and the VxSS subsystem with hard-coded credential 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 patches for CVE-2022-36952 or upgrade to a patched version. If immediate patching is not possible, restrict network access to OpsCenter services and implement monitoring for unauthorized access attempts.

Recommended fix Moderate confidence

NetBackup OpsCenter 8.3.0.2 or later (for 8.x); 9.0.0.2 or later (for 9.0.x); 9.1.0.1 or later (for 9.1.x); or latest 10.x release

  1. 1. Identify the currently installed NetBackup OpsCenter version using the About menu or version check command.
  2. 2. For NetBackup 8.x versions below 8.3.0.2, upgrade to version 8.3.0.2 or later.
  3. 3. For NetBackup 9.0.x versions, upgrade to version 9.0.0.2 or later (which contains the fix).
  4. 4. For NetBackup 9.1.x versions below 9.1.0.1, upgrade to version 9.1.0.1 or later.
  5. 5. Obtain the upgrade from Veritas download site or your Veritas account.
  6. 6. Apply the upgrade following standard Veritas upgrade procedures, including backing up configuration data before upgrade.
  7. 7. After upgrade, verify the OpsCenter services are running correctly and the version has been updated.
Caveat Review Veritas upgrade guides for any compatibility requirements or migration steps; ensure adequate downtime window for upgrade procedure

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

Fix this in Netbackup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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