NetbackupApplication · Veritas

CVE-2017-6407

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. Privileged remote command execution on NetBackup Server and Client (on the server or a connected client) 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 privileged remote command execution vulnerability in Veritas NetBackup Server (versions before 7.7.2) and NetBackup Appliance (versions before 2.7.2) allows authenticated attackers to execute arbitrary commands with elevated privileges on the NetBackup server or connected clients.

MitigationUpgrade to NetBackup 7.7.2 or NetBackup Appliance 2.7.2 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to NetBackup management interfaces and monitor for unauthorized privileged access.

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
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 NetBackup installation
    Locate Veritas NetBackup Server or NetBackup Appliance in your environment. Check for processes named 'nbevtmgr', 'nbdisco', 'nbjm', or look for Veritas installation directories. On Appliances, check the management interface or console.
    Affected if NetBackup Server or Appliance is present in the environment
  2. Determine NetBackup Server version
    Run 'bp_get_config -version' or check the NetBackup installation directory for version files. On Windows, check 'C:\Program Files\Veritas\NetBackup\version.txt' or similar. On Unix/Linux, check '/usr/openv/netbackup/version' or '/opt/VRTSnb/bin/nbversion' if those paths exist in your environment.
    Affected if The installed version is 7.7.1 or earlier (any version below 7.7.2)
  3. Determine NetBackup Appliance version
    Access the Appliance web console or run 'version' command via SSH to the appliance management interface. Check the Appliance UI under 'Support > About' or run 'nbacdiag --version' if available.
    Affected if The installed Appliance version is 2.7.1 or earlier (any version below 2.7.2)
  4. Verify authentication is required for exploitation
    Confirm whether external or less-trusted users have access to NetBackup management interfaces or API endpoints. Review user roles and authentication configuration in NetBackup Administration Console or bp.conf (Unix) / registry (Windows).
    Affected if Untrusted or low-privilege authenticated users can access NetBackup interfaces or APIs

You are affected if NetBackup Server version is 7.7.1 or lower, or NetBackup Appliance version is 2.7.1 or lower, AND untrusted users have any authentication access to the NetBackup management interfaces.

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 or NetBackup Appliance 2.7.2 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to NetBackup management interfaces and monitor for unauthorized privileged access.

Fix this in Netbackup Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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