AccessApplication · Veritas

CVE-2017-6406

HIGH · 8.8 CVSS v3.0 Published 2017-03-02
Fix available
A fix is available. Upgrade to after 7.7.1 or later.
See remediation →
90/100
Remediation priority · Urgent
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 Before 7.7.2 and NetBackup Appliance Before 2.7.2. Arbitrary privileged command execution, using whitelist directory escape with "../" substrings, can occur.

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 confidence

A path traversal vulnerability in Veritas NetBackup (before 7.7.2) and NetBackup Appliance (before 2.7.2) allows attackers to escape whitelisted directories using '../' sequences, enabling arbitrary privileged command execution.

MitigationUpgrade to NetBackup 7.7.2/NetBackup Appliance 2.7.2 or later to obtain the patched version that properly validates and sanitizes directory path inputs.

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
AccessApplication
Affected:<= 7.2.1
NetbackupApplication
Affected:<= 7.7.1
Netbackup ApplianceApplication
Affected:<= 2.7.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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 the Veritas product installed
    Determine whether your system runs Veritas NetBackup, NetBackup Appliance, or Veritas Access. Check installed packages, product documentation, or the main application name visible in your environment.
    Affected if The product is Veritas NetBackup, NetBackup Appliance, or Veritas Access
  2. Check the installed version of NetBackup
    Run the version command for NetBackup (such as 'nbversion' or consult the version file in the NetBackup installation directory) or use the NetBackup administration interface to retrieve the version number.
    Affected if The version is 7.7.1 or earlier (before 7.7.2)
  3. Check the installed version of NetBackup Appliance
    Use the Appliance console or command line (such as 'nbac --version' or similar appliance management commands) to retrieve the appliance software version.
    Affected if The version is 2.7.1 or earlier (before 2.7.2)
  4. Check the installed version of Veritas Access
    Query the Veritas Access installation for its version number using the product's management interface or version checking utilities.
    Affected if The version is 7.2.1 or earlier (before the fixed version)
  5. Verify if the web service or API is accessible
    Confirm whether the NetBackup or Veritas Access web interface, REST API, or related network service is exposed and enabled. Check configuration files and running services for components that handle file path inputs.
    Affected if The vulnerable path traversal component is accessible via the web interface or API, allowing unauthenticated or low-privileged users to submit requests with '../' sequences

You are affected if you have Veritas NetBackup <= 7.7.1, NetBackup Appliance <= 2.7.1, or Veritas Access <= 7.2.1, and the web service or API endpoint that processes directory paths is enabled and accessible.

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 7.7.1
Interim mitigation

Upgrade to NetBackup 7.7.2/NetBackup Appliance 2.7.2 or later to obtain the patched version that properly validates and sanitizes directory path inputs.

Fix this in Access Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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