CVE-2022-36949
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 attacker with local access to a NetBackup OpsCenter server could potentially escalate their privileges. 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 a local privilege escalation vulnerability in Veritas NetBackup OpsCenter. An attacker with existing local access to the OpsCenter server can potentially elevate their privileges beyond the permissions they were initially granted. The vulnerability affects multiple version branches (8.x, 9.x, 9.1.x, and 10.x) indicating a systemic security flaw in privilege handling.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 installationLook for the Veritas NetBackup OpsCenter service or process running on the system. On Windows, check Services.msc for 'Veritas NetBackup OpsCenter' or run 'sc query' to list services. On Linux/Unix, run 'ps -ef | grep -i opscenter' or check for /opt/opscenter directory.Affected if OpsCenter service or process is not found on the system, meaning the product is not installed and the system is not affected.
-
Identify OpsCenter versionLocate the version file or executable. Common methods include: check the installation directory (typically /opt/veritas/opscenter or C:\Program Files\Veritas\NetBackup OpsCenter), look for a 'version' file, or run 'nbocs -version' if the command-line tool is available.Affected if Unable to determine the installed version - further investigation needed to assess exposure.
-
Compare against affected version rangesMatch the identified version against: 8.0 <= version < 8.3.0.2, or version equals 9.0, or version equals 9.1.0.0. Any version matching these ranges is vulnerable.Affected if The installed version falls within 8.0 to 8.3.0.1, is exactly 9.0, or is exactly 9.1.0.0 - the system is potentially affected by this privilege escalation vulnerability.
-
Verify service is running and accessible locallyConfirm the OpsCenter service is currently running and accepting connections. On Windows, use 'sc query' or check the service status in Services. On Linux, use 'systemctl status opscenter' or 'ps' to verify the process is active.Affected if The service is running and the server is accessible to untrusted local users, the privilege escalation vulnerability could be exploited by those users.
The system is affected if Veritas NetBackup OpsCenter is installed and the running version matches any of the affected ranges: 8.0 through 8.3.0.1, exactly 9.0, or exactly 9.1.0.0.
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 the vendor-supplied patches for NetBackup OpsCenter to upgrade to a version beyond the affected ranges (8.3.0.2, 9.0.0.1, 9.1.0.1, or 10.x). In the interim, strictly limit physical and logical access to the OpsCenter server to trusted administrative personnel only.
NetBackup OpsCenter 8.3.0.2 or later for 8.x; 9.0.0.2 or later for 9.0.x; 9.1.0.2 or later for 9.1.x; latest 10.x release for version 10
- 1. Identify the current installed version of NetBackup OpsCenter by running: /usr/openv/opscenter/bin/opscenter -version or checking the About section in the OpsCenter console
- 2. If running version 8.x (< 8.3.0.2), upgrade to NetBackup OpsCenter 8.3.0.2 or later
- 3. If running version 9.0.x (including 9.0 and 9.0.0.1), upgrade to NetBackup OpsCenter 9.0.0.2 or later
- 4. If running version 9.1.x (including 9.1.0.0 and 9.1.0.1), upgrade to NetBackup OpsCenter 9.1.0.1 or later (note: 9.1.0.1 may itself be affected per some references, so consider 9.1.0.2 or later if available)
- 5. If running version 10.0, upgrade to the latest available NetBackup OpsCenter 10.x release that includes the security fix
- 6. After upgrade, verify the new version is running and confirm the vulnerability is resolved by checking /usr/openv/opscenter/bin/opscenter -version
- 7. Apply the principle of least privilege for any local accounts on the OpsCenter server to limit the impact of potential privilege escalation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36949 — 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-36949 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