CVE-2017-6399
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 · uneditedAn 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 confidenceThis vulnerability allows privileged remote command execution on NetBackup servers and connected clients. Attackers can execute arbitrary commands with elevated privileges without authentication on affected versions of NetBackup (before 7.7.2) and NetBackup Appliance (before 2.7.2). The high CVSS score reflects network-exploitable, low-complexity attacks with high confidentiality and integrity impact.
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<= 7.2.1<= 7.7.1<= 2.7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Veritas productRun 'vxlsit' or check /opt/veritas for product directories. Common paths: /opt/veritas/netbackup for NetBackup, /opt/veritas/access for Veritas Access, /opt/veritas/nbu for Appliance componentsAffected if The product is Veritas NetBackup, Veritas NetBackup Appliance, or Veritas Access and the version is at or below the affected threshold
-
Determine NetBackup versionRun 'nbhubd -version' or check /usr/openv/netbackup/version.txt. Alternatively, use the NetBackup Administration Console or 'bpgetconfig' commandAffected if Version is 7.7.1 or earlier (e.g., 7.5.x, 7.6.x, 7.7.0, 7.7.1)
-
Determine NetBackup Appliance versionRun 'umscli -version' or check /etc/nbu_version file. The Appliance web console also displays the version under Support > AboutAffected if Version is 2.7.1 or earlier (e.g., 2.5.x, 2.6.x, 2.7.0, 2.7.1)
-
Determine Veritas Access versionCheck /opt/VRTSnas version file or run 'vxiVersion' if available. The管理界面also shows version informationAffected if Version is 7.2.1 or earlier (e.g., 7.0.x, 7.1.x, 7.2.0, 7.2.1)
-
Check if NetBackup services are network-exposedRun 'netstat -tlnp | grep -E "(13722|13724|13782|1556)" or use 'bpps -a' to list running NetBackup processes. Verify if port 1556 (bpcd) or other NetBackup ports are listening on non-loopback interfacesAffected if NetBackup services listen on 0.0.0.0 or external interfaces rather than 127.0.0.1 only
You are affected if you have NetBackup <= 7.7.1, NetBackup Appliance <= 2.7.1, or Veritas Access <= 7.2.1 running with network-accessible services.
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.
From vendor dataUpgrade to NetBackup 7.7.2 or later, or NetBackup Appliance 2.7.2 or later. Prior to patching, restrict network access to NetBackup services and implement additional monitoring for the affected components.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6399 — 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-2017-6399 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