dbcve.org
Netbackup ApplianceApplication · Veritas

CVE-2015-6550

CRITICAL · 9.8 CVSS v3.0 Published 2016-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
bpcd in Veritas NetBackup 7.x through 7.5.0.7, 7.6.0.x through 7.6.0.4, 7.6.1.x through 7.6.1.2, and 7.7.x before 7.7.2 and NetBackup Appliance through 2.5.4, 2.6.0.x through 2.6.0.4, 2.6.1.x through 2.6.1.2, and 2.7.x before 2.7.2 allows remote attackers to execute arbitrary commands via crafted input.

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

bpcd (Backup Catalog Daemon) in Veritas NetBackup 7.x through 7.7.x and NetBackup Appliance 2.x through 2.7.x contains a command injection vulnerability allowing remote attackers to execute arbitrary commands via crafted input. This is a critical RCE vulnerability exploitable over the network without authentication.

MitigationApply vendor-supplied patches to reach fixed versions (NetBackup 7.7.2+, 7.6.1.3, 7.6.0.5, 7.5.0.8; Appliance 2.7.2+, 2.6.1.3, 2.6.0.5, 2.5.5). Until patched, consider network segmentation to restrict access to bpcd ports and disable bpcd if not required.

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
Netbackup ApplianceApplication
Affected:= 1.1.0.1= 1.1.0.2= 1.2= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.5= 2.5.1= 2.5.2= 2.5.3= 2.6
NetbackupApplication
Affected:= 7.0= 7.0.1= 7.1.0.1= 7.1.0.2= 7.1.0.3= 7.1.0.4= 7.5.0.1= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6= 7.5.0.7

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

CVSS:3.0/AV:N/AC:L/PR:N/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 NetBackup installation and version
    Run 'bpgetconfig -L' or check the installation directory for version file. On appliance, run 'nbac --version' or check /etc/release file.
    Affected if Installed version matches any of these: NetBackup 7.0, 7.0.1, 7.1.0.1-7.1.0.4, 7.5.0.1, 7.5.0.3-7.5.0.7; or Appliance 1.1.0.1, 1.1.0.2, 1.2, 2.0-2.0.3, 2.5-2.5.3, 2.6
  2. Confirm bpcd service is running
    Run 'bpps -a' or check process list for 'bpcd' daemon. On appliance, use 'ps -ef | grep bpcd'.
    Affected if The bpcd process is active and visible in process list
  3. Check if bpcd is listening on network ports
    Run 'netstat -an | grep -E "13782|13783"' or 'ss -tlnp | grep bpcd' to verify bpcd is bound to network interfaces.
    Affected if bpcd is listening on TCP ports 13782 or 13783 (or both) and accessible over network
  4. Verify bpcd is not restricted to localhost
    Check bpcd configuration in bp.conf or registry for 'BROKER_HOST' setting. Run 'bpconfig -l' to review daemon bindings.
    Affected if bpcd is bound to 0.0.0.0 or a non-loopback interface rather than localhost only

Environment is affected if NetBackup version falls within the listed affected ranges AND bpcd service is running and accessible over the network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches to reach fixed versions (NetBackup 7.7.2+, 7.6.1.3, 7.6.0.5, 7.5.0.8; Appliance 2.7.2+, 2.6.1.3, 2.6.0.5, 2.5.5). Until patched, consider network segmentation to restrict access to bpcd ports and disable bpcd if not required.

Recommended fix High confidence

NetBackup: 7.7.2 or later (latest 7.x); NetBackup Appliance: 2.7.2 or later (latest 2.7.x or migrate to 3.x)

  1. Identify current NetBackup or NetBackup Appliance version using bpgetconfig or the administration console
  2. Schedule a maintenance window for the upgrade procedure
  3. Back up the current NetBackup configuration using nbemmcmd or the appliance web UI
  4. For NetBackup: Upgrade to version 7.7.2 or later (recommended: latest 7.x release)
  5. For NetBackup Appliance: Upgrade to version 2.7.2 or later (recommended: latest 2.7.x or 3.x release)
  6. After upgrade, verify the bpcd service is running and responding correctly
  7. Confirm the version upgrade was successful via bpgetconfig or appliance CLI: 'nbgetconfig' or 'version' command
  8. Apply any additional security hardening per Veritas best practices (restrict bpcd access via bp.conf or firewall rules)
Caveat Major version upgrades may require configuration migration; test in non-production environment first; some legacy bpcd client configurations may need updating

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

Fix this in Netbackup Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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