dbcve.org
Flex ApplianceApplication · Veritas

CVE-2022-36985

HIGH · 7.8 CVSS v3.1 Published 2022-07-28
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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
An issue was discovered in Veritas NetBackup 8.1.x through 8.1.2, 8.2, 8.3.x through 8.3.0.2, 9.x through 9.0.0.1, and 9.1.x through 9.1.0.1 (and related NetBackup products). An attacker with unprivileged local access to a Windows NetBackup Primary server could potentially escalate their privileges.

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

A detailed technical summary for this CVE is being prepared.

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
Flex ApplianceApplication
Affected:= 1.2= 1.3= 2.0= 2.0.1= 2.0.2= 2.1
Flex ScaleApplication
Affected:= 1.3.1= 2.1
NetbackupApplication
Affected:= 8.1.1= 8.1.2= 8.2= 8.3= 8.3.0.1= 8.3.0.2= 9.0= 9.0.0.1= 9.1= 9.1.0.1
Netbackup ApplianceApplication
Affected:= 3.1.1= 3.1.2= 3.2= 4.0= 4.1= 3.3.0.1= 3.3.0.2= 4.0.0.1= 4.1.0.1

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
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

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
Patch available Apply the vendor patch
Vendor patch www.veritas.com →
Recommended fix Moderate confidence
  1. 1. Review the Veritas security advisory VTS22-004 at https://www.veritas.com/content/support/en_US/security/VTS22-004#h7 for the specific patch or hotfix for your product and version.
  2. 2. Identify your exact NetBackup/Flex Appliance/Flex Scale version from the affected versions list (8.1.1, 8.1.2, 8.2, 8.3, 3.1.1, 3.1.2, 3.2, 4.0, 1.2, 1.3, 2.0, 2.0.1, 1.3.1, 2.1).
  3. 3. Download and apply the corresponding patch or hotfix provided in the security advisory for your affected product.
  4. 4. After patching, verify the fix by confirming the patch version is applied and testing that privilege escalation is no longer possible.
  5. 5. For NetBackup versions 9.x through 9.0.0.1 and 9.1.x through 9.1.0.1 (as noted in the official description), also apply the appropriate patch from the advisory.

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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