CVE-2022-36950
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 be able to perform remote command execution through a Java classloader manipulation. 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 · high confidenceVeritas NetBackup OpsCenter contains a critical flaw allowing unauthenticated remote attackers to execute arbitrary commands by manipulating the Java classloader. This indicates a deserialization vulnerability where malicious serialized Java objects can be crafted to achieve RCE without any authentication credentials.
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 OpsCenter is installedLook for Veritas OpsCenter installation directory. On Windows, check C:\Program Files\Veritas\OpsCenter or C:\Program Files\Veritas\NetBackup\OpsCenter. On Linux, check /opt/veritas/opscenter. Also check Windows Services or Linux processes for 'OpsCenter' or 'nbocs' services.Affected if OpsCenter software is present on the system
-
Identify OpsCenter versionCheck the version file. On Windows, look in the installation directory for a version.txt or check the Windows Registry under HKLM\Software\Veritas\OpsCenter\Version. On Linux, run: cat /opt/veritas/opscenter/version.ini or /opt/veritas/opscenter/bin/opsadmin versionAffected if Version matches: 8.0.x through 8.3.0.1, 9.0.x, or 9.1.0.0 (exact version can also be confirmed by comparing to vendor advisory version list)
-
Verify OpsCenter web service is runningCheck if the OpsCenter web console service is running. On Windows, check the 'Veritas OpsCenter Web Server' service status. On Linux, run: ps -ef | grep opscenter | grep -i web. Also check listening ports: netstat -an | grep -E '80|443|8443' or ss -tlnp | grep -E '80|443|8443'Affected if OpsCenter web service (typically port 80, 443, or 8443) is listening and accessible
-
Check network exposure of OpsCenter interfaceReview firewall rules and network accessibility. Determine if OpsCenter ports are exposed to untrusted networks. Query firewall rules: on Windows 'netsh advfirewall firewall show rule name=all', on Linux 'iptables -L' or 'firewall-cmd --list-all'. Identify if the OpsCenter web interface is reachable from outside the local network or from systems outside the trusted zone.Affected if OpsCenter web interface is accessible from untrusted networks or the internet without proper network segmentation
The environment is affected if OpsCenter is installed, runs a version within 8.0 through 8.3.0.1, 9.0.x, or 9.1.0.0, and the OpsCenter web service is network-accessible from untrusted networks.
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.
From vendor data8.3.0.2
Immediately restrict network access to OpsCenter interfaces from untrusted networks and apply vendor-provided patches or upgrade to a patched version (8.3.0.3, 9.0.0.2, 9.1.0.2, or 10.0 and later).
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36950 — 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-36950 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