Access ApplianceApplication · Veritas

CVE-2022-46413

HIGH · 8.8 CVSS v3.1 Published 2022-12-04
Fix available
A fix is available. Upgrade to after 8.0.100 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Flex Scale through 3.0 and Access Appliance through 8.0.100. Authenticated remote command execution can occur via the management portal.

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 confidence

This vulnerability allows an authenticated user to execute arbitrary commands on the underlying operating system through the NetBackup Flex Scale (up to 3.0) or Access Appliance (up to 8.0.100) management web portal. The attack vector is remote and requires valid authentication credentials, but once authenticated, the attacker can inject and execute OS-level commands with the privileges of the web application service.

MitigationRestrict network access to the management portal to trusted IP ranges via firewall rules or VPN, enforce strong multi-factor authentication for portal accounts, and apply available vendor patches to upgrade beyond the affected versions.

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
Access ApplianceApplication
Affected:<= 8.0.100
Netbackup Flex Scale ApplianceApplication
Affected:<= 3.0

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Access the appliance console or use the command line interface (e.g., 'vxdctl -version' or check the web UI login page footer) to determine if the system is running Veritas Access Appliance or NetBackup Flex Scale and note the exact version number.
    Affected if The product is Veritas Access Appliance version 8.0.100 or earlier, or NetBackup Flex Scale version 3.0 or earlier.
  2. Check management portal network exposure
    Review firewall rules or network configuration to determine if the management web portal (typically HTTPS on port 443 or 8443) is exposed to untrusted networks or the public internet.
    Affected if The management portal is accessible from networks outside the trusted internal environment.
  3. Verify web service is running
    Check if the NetBackup or Access web management service is active by running system commands like 'ps -ef | grep -i web' or checking service status through the appliance CLI.
    Affected if The web management service is running and accessible.

A system is affected if it is running Access Appliance <= 8.0.100 or NetBackup Flex Scale <= 3.0, the management portal is network-accessible, and the web application service is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 8.0.100
Interim mitigation

Restrict network access to the management portal to trusted IP ranges via firewall rules or VPN, enforce strong multi-factor authentication for portal accounts, and apply available vendor patches to upgrade beyond the affected versions.

Fix this in Access Appliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46413 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