CVE-2017-8858
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 · uneditedIn Veritas NetBackup 8.0 and earlier and NetBackup Appliance 3.0 and earlier, there is unauthenticated privileged remote file write using the 'bprd' process.
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 confidenceVeritas NetBackup versions 8.0 and earlier and NetBackup Appliance 3.0 and earlier contain an unauthenticated remote file write vulnerability in the bprd (NetBackup Request Daemon) process. An unauthenticated remote attacker can write files to the filesystem with elevated privileges, potentially achieving remote code execution by writing to startup locations or overwriting system binaries.
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<= 8.0<= 3.0CVSS 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.
-
Verify NetBackup installationCheck for NetBackup installation directories (e.g., /usr/openv/netbackup, /opt/VRTSnetbp) or query installed packages using system package managerAffected if NetBackup is found installed on the system
-
Determine NetBackup versionRun 'bp_get_config -version' or check version files in /usr/openv/netbackup/version or /opt/VRTSnetbp/VERSIONAffected if Installed version is 8.0 or earlier for NetBackup, or 3.0 or earlier for NetBackup Appliance
-
Check if bprd service is runningQuery service status using 'bpps -a' or system service manager (systemctl, init.d) for bprd processAffected if bprd daemon is actively running on the system
-
Verify bprd network exposureCheck if port 13782 is listening and exposed by running 'netstat -anp | grep 13782' or 'ss -tlnp | grep 13782'Affected if Port 13782 is open and accessible from untrusted networks
A system is affected if it runs NetBackup version 8.0 or earlier (or Appliance 3.0 or earlier) with the bprd service enabled and port 13782 exposed to network attackers.
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 version 8.0.1 or later and NetBackup Appliance 3.1 or later. If immediate upgrading is not feasible, restrict network access to bprd ports (typically 13782) via firewall rules and disable the bprd service if not required.
NetBackup 8.1+ / NetBackup Appliance 3.1+
- Upgrade NetBackup to version 8.1 or later to remediate the vulnerability
- If using NetBackup Appliance, upgrade to version 3.1 or later
- After upgrading, verify the bprd process configuration to ensure no unauthorized access is possible
- Review NetBackup access controls and network exposure to minimize attack surface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation16.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8858 — 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-8858 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