CVE-2017-15517
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 · uneditedAltaVault OST Plug-in versions prior to 1.2.2 may allow attackers to obtain sensitive information via unspecified vectors. All users are urged to move to a fixed version and change passwords used by Veritas NetBackup to access the OST shares on the NetApp AltaVault as a precaution.
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 · moderate confidenceAltaVault OST Plug-in versions prior to 1.2.2 contain an information disclosure vulnerability that allows attackers to obtain sensitive data via unspecified vectors. The issue affects the interface between Veritas NetBackup and NetApp AltaVault storage. This is a confidentiality-focused flaw with low complexity exploitation potential.
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.2.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 AltaVault OST Plug-in installationLocate the NetApp AltaVault OST Plug-in installation directory on the system running Veritas NetBackup. This is typically found where NetBackup plug-ins or agents are installed.Affected if The plug-in is present on the system
-
Determine the installed versionUse the system's standard method for checking installed software version - this may be via the plug-in's About dialog, a version file within the installation directory, or the NetBackup administration console if it displays plug-in versions.Affected if The version displayed is lower than 1.2.2 or cannot be determined to be 1.2.2 or higher
-
Verify the NetBackup-AltaVault interface is configuredCheck whether Veritas NetBackup is configured to use NetApp AltaVault storage through the OST (Open Storage Technology) interface. This is typically visible in NetBackup storage configuration or OST plug-in settings.Affected if NetBackup is actively configured to communicate with AltaVault via the OST interface
-
Confirm the vulnerability scopeReview any NetBackup logs or audit records for unusual access patterns to the OST plug-in or AltaVault storage that could indicate the vulnerability has been exploited.Affected if Unexpected or unauthorized access to OST data is observed
A user is affected if the NetApp AltaVault OST Plug-in installed with Veritas NetBackup is version 1.2.1 or lower and the NetBackup-AltaVault OST interface is actively configured.
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 data1.2.2
Upgrade AltaVault OST Plug-in to version 1.2.2 or later. As a precautionary measure, change all passwords used by Veritas NetBackup to access OST shares on the NetApp AltaVault appliance.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15517 — 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-15517 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