CVE-2022-36951
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, an unauthenticated remote attacker may compromise the host by exploiting an incorrectly patched vulnerability. 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 confidenceUnauthenticated remote code execution vulnerability in Veritas NetBackup OpsCenter stemming from an incorrectly patched prior flaw. 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. Allows remote attackers to compromise the host without authentication.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NetBackup OpsCenter installationLocate the OpsCenter installation directory or running service. Common locations include /opt/veritas/ on Linux or C:\Program Files\Veritas\ on Windows. Check for the 'opscenter' directory or the 'NetBackup OpsCenter' service.Affected if OpsCenter is not installed on the system
-
Identify OpsCenter versionRun the version command for OpsCenter. On Linux, typically: /opt/veritas/opscenter/bin/opscenter --version or check the version file in the installation directory. On Windows, check via the GUI or registry.Affected if The installed version cannot be determined or is not visible
-
Compare version against affected rangesCompare the identified OpsCenter version to the affected ranges: 8.0 through versions less than 8.3.0.2; version 9.0; version 9.1.0.0 through 9.1.0.1; and any version 10.x.Affected if The installed version falls within any of these ranges: >= 8.0 and < 8.3.0.2, or = 9.0, or 9.1.0.0 through 9.1.0.1, or 10.x
-
Verify OpsCenter web interface is network-accessibleDetermine if the OpsCenter web service is listening on its HTTP/HTTPS port and accessible from network locations. Check firewall rules and network exposure.Affected if The OpsCenter web interface is exposed to untrusted networks
A system is affected if NetBackup OpsCenter is installed with a version matching 8.0 through less than 8.3.0.2, exactly 9.0, 9.1.0.0 through 9.1.0.1, or any 10.x release, and the web interface is network-accessible.
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-supplied patches to upgrade NetBackup OpsCenter to a corrected version beyond the affected releases.
NetBackup OpsCenter 9.1.0.2 or later (or latest 10.x release with security patch)
- 1. Identify the current NetBackup OpsCenter version by running: /usr/openv/netbackup/bin/version or checking the OpsCenter console About section
- 2. Download the appropriate fixed version from Veritas Support (https://www.veritas.com/support/article/TECH242242)
- 3. Review Veritas Emergency Security Bulletin for CVE-2022-36951 to confirm the exact patch or version required
- 4. Schedule a maintenance window and create a full system backup/snapshot of the OpsCenter server
- 5. For NetBackup 8.x: Upgrade to version 8.3.0.2 or later
- 6. For NetBackup 9.0.x: Upgrade to version 9.0.0.2 or later (or migrate to 9.1.x)
- 7. For NetBackup 9.1.x: Upgrade to version 9.1.0.2 or later
- 8. For NetBackup 10.x: Apply the vendor-supplied patch or upgrade to the latest 10.x release that includes the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.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 $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36951 — 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-36951 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