CVE-2015-6552
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 · uneditedThe management-services protocol implementation 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 make arbitrary RPC calls via unspecified vectors.
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 confidenceThe management-services protocol implementation in Veritas NetBackup versions 7.x through 7.7.1 and NetBackup Appliance versions through 2.7.1 contains a critical vulnerability allowing remote unauthenticated attackers to make arbitrary RPC calls, potentially achieving remote code execution on the affected system.
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= 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= 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.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetBackup software versionRun 'nbconsole -get_all_versions' or check the version via the NetBackup Administration Console under Help > About NetBackup. On Linux/Unix, also check '/usr/openv/netbackup/VERSION' or run 'bpgetconfig'Affected if The installed version matches 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, or any 7.x version through 7.7.1 (the exact version can be confirmed with 'bpgetconfig | grep -i version')
-
Identify NetBackup Appliance versionAccess the Appliance Console or use the command 'appliance version' via SSH or console login. The version is also visible in the Appliance web UI on the DashboardAffected if The installed version matches 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, or 2.6, or any version through 2.7.1
-
Verify management services RPC port exposureCheck if the NetBackup management service port (typically TCP 13701, 13711, 13724, or the bpcd port 13782) is listening on external interfaces. Run 'netstat -an | grep -E "13701|13711|13724|13782"' or 'ss -tlnp | grep -E "13701|13711|13724|13782"'Affected if The management RPC ports are bound to 0.0.0.0 or an externally accessible IP address rather than localhost only
-
Confirm if nbws service is running and exposedCheck for the NetBackup Web Service process with 'ps aux | grep -i nbws' or 'bpps -a | grep -i ws'. Verify listening ports with 'netstat -tlnp' and look for web service ports (often 8080, 8443, or custom ports)Affected if The NetBackup web/management service is running and bound to a reachable network interface
Your environment is affected if NetBackup version is 7.x through 7.7.1, NetBackup Appliance is through 2.7.1, and management services ports are network-accessible without authentication.
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.
dbcve · scopedUpgrade to NetBackup 7.7.2 or NetBackup Appliance 2.7.2 or later. If immediate patching is not possible, restrict network access to management services ports and implement additional monitoring for suspicious RPC activity.
NetBackup: 7.7.2 or later (or appropriate branch fix: 7.5.0.7, 7.6.0.4, 7.6.1.2); NetBackup Appliance: 2.7.2 or later (or appropriate branch fix: 2.5.4, 2.6.0.4, 2.6.1.2)
- 1. Identify the exact NetBackup or NetBackup Appliance version currently installed
- 2. For NetBackup versions 7.0-7.5.0.7: upgrade to version 7.5.0.7 or later
- 3. For NetBackup versions 7.6.0.x: upgrade to version 7.6.0.4 or later
- 4. For NetBackup versions 7.6.1.x: upgrade to version 7.6.1.2 or later
- 5. For NetBackup versions 7.7.x: upgrade to version 7.7.2 or later
- 6. For NetBackup Appliance versions up to 2.5.4: upgrade to version 2.5.4 or later
- 7. For NetBackup Appliance versions 2.6.0.x: upgrade to version 2.6.0.4 or later
- 8. For NetBackup Appliance versions 2.6.1.x: upgrade to version 2.6.1.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6552 — 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-2015-6552 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