CVE-2022-36954
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 · uneditedIn Veritas NetBackup OpsCenter, under specific conditions, an authenticated remote attacker may be able to create or modify OpsCenter user accounts. 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 confidenceThis is an authorization vulnerability in Veritas NetBackup OpsCenter where an authenticated remote attacker can create new or modify existing OpsCenter user accounts under specific conditions. The issue affects versions 8.x through 8.3.0.2, 9.x through 9.0.0.1, 9.1.x through 9.1.0.1, and 10. The specific conditions enabling exploitation are not detailed in the advisory.
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>= 8.0, < 8.3.0.2= 9.0= 9.1.0.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpsCenter versionCheck the installed NetBackup OpsCenter version via the web interface (Help > About) or by running: /opt/VRTSpb/web/nbwebservices.sh -version or checking the installation log files in /var/VRTSpb/logs/Affected if The installed version is 8.x through 8.3.0.2, 9.x through 9.0.0.1, 9.1.x through 9.1.0.1, or 10.0 (any version before the patched release within these ranges)
-
Confirm OpsCenter web service is enabledVerify the OpsCenter web service (nbwebservices) is running and accessible. Check via: systemctl status nbwebservices or by attempting to access the OpsCenter web console at https://<hostname>:8443 or http://<hostname>:8181Affected if The OpsCenter web service is running and remotely accessible on the network
-
Verify OpsCenter user authentication is enabledCheck that OpsCenter user authentication is configured. Review the OpsCenter security settings through the web interface under Administration > Security > User Management, or check the opscenter.conf file for authentication settings.Affected if OpsCenter user authentication is enabled (this is required for the authenticated attacker to exploit the vulnerability)
-
Check for existing unauthorized user accountsReview the OpsCenter user list under Administration > Security > User Accounts for any unexpected or unauthorized users that may have been created. Compare against known legitimate accounts.Affected if There are unexpected user accounts present that were not created by legitimate administrators
A user is affected if they are running any Veritas NetBackup OpsCenter version in the ranges 8.x-8.3.0.2, 9.x-9.0.0.1, 9.1.x-9.1.0.1, or 10.x with the OpsCenter web service accessible and user authentication enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.3.0.2
Apply vendor-provided patches when available; restrict OpsCenter administrative access to trusted personnel only and follow least-privilege principles for user accounts.
Upgrade to NetBackup OpsCenter 8.3.0.2 or later for 8.x versions; 9.0.0.2 or later for 9.0.x versions; 9.1.0.2 or later for 9.1.x versions; or 10.x (latest available)
- 1. Identify the current installed version of NetBackup OpsCenter using the About section in the OpsCenter console or by running: /usr/openv/netbackup/version on the OpsCenter server
- 2. Determine the appropriate upgrade path based on your current major version (8.x, 9.0.x, or 9.1.x)
- 3. Download the appropriate NetBackup OpsCenter upgrade package from Veritas Support (https://www.veritas.com/support/en_US/article.100052839.html)
- 4. Back up the OpsCenter database and configuration before upgrading
- 5. Apply the upgrade following Veritas documentation for your specific version upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36954 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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