CVE-2015-7425
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 Data Protection component in the VMware vSphere GUI in IBM Tivoli Storage Manager for Virtual Environments: Data Protection for VMware (aka Spectrum Protect for Virtual Environments) 6.3 before 6.3.2.5, 6.4 before 6.4.3.1, and 7.1 before 7.1.4 and Tivoli Storage FlashCopy Manager for VMware (aka Spectrum Protect Snapshot) 3.1 before 3.1.1.3, 3.2 before 3.2.0.6, and 4.1 before 4.1.4 allows remote attackers to obtain administrative privileges via a crafted URL that triggers back-end function execution.
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 Data Protection component in the VMware vSphere GUI of IBM Tivoli Storage Manager for Virtual Environments and Tivoli Storage FlashCopy Manager for VMware contains a privilege escalation vulnerability. Remote attackers can obtain administrative privileges by sending crafted URLs that trigger arbitrary back-end function execution, bypassing authentication controls.
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= 3.1= 3.1.1= 3.2= 6.3= 6.4= 6.4.2= 6.4.3= 4.1.0= 4.1.1= 4.1.2= 4.1.3= 6.3.1= 6.3.2= 6.4.1= 7.1.0= 7.1.1= 7.1.2= 7.1.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 installed productLocate the IBM Tivoli Storage Manager for Virtual Environments or Tivoli Storage FlashCopy Manager installation directory and check for existence of the software. Common paths include /opt/tivoli/tsm/ or check program files on Windows. Look for directories named 'Tivoli' or 'TSM' and specifically 'Data Protection for VMware' components.Affected if The software is not installed - then not affected. If installed, proceed to version check.
-
Determine installed versionCheck the version of IBM Tivoli Storage Manager for Virtual Environments Data Protection for VMware or Tivoli Storage FlashCopy Manager for VMware. Typically found in version files, About dialogs, or installer logs. Common locations: installation_directory/version.txt, or run 'dsmversion' command if available.Affected if Version matches any of these affected versions: FlashCopy Manager 3.1, 3.1.1, 3.2, 6.3, 6.4, 6.4.2, 6.4.3; Data Protection for VMware 4.1.0-4.1.3, 6.3.1-6.3.2, 6.4.1, or 7.1.0-7.1.3. If version is in these ranges, potentially affected.
-
Verify vSphere GUI interface statusDetermine if the vSphere GUI web interface is enabled and accessible. Check configuration files (such as web.config or dsmwebui.config) in the installation directory for the Data Protection component. Look for settings related to HTTP/HTTPS listener or web server configuration.Affected if The vSphere GUI interface is enabled and exposed on network. This component must be accessible for the vulnerability to be exploitable.
-
Review access controls and network exposureCheck if the vSphere GUI management interface is exposed to untrusted networks. Review firewall rules, access control lists, or reverse proxy configurations that allow access to the Data Protection web interface ports (typically 8443, 9080, or similar).Affected if The interface is accessible from untrusted networks without proper access restrictions. The vulnerability can be exploited remotely if the interface is network-accessible.
Your environment is affected if you have IBM Tivoli Storage Manager for Virtual Environments Data Protection for VMware or Tivoli Storage FlashCopy Manager for VMware installed with an affected version (4.1.0-4.1.3, 6.3.1-6.3.2, 6.4.1, 7.1.0-7.1.3, or 3.1, 3.1.1, 3.2, 6.3, 6.4, 6.4.2, 6.4.3) AND the vSphere GUI interface is enabled and network-accessible.
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 the patched versions: 6.3.2.5 or later for version 6.3, 6.4.3.1 or later for version 6.4, 7.1.4 or later for version 7.1; or 3.1.1.3 or later for version 3.1, 3.2.0.6 or later for version 3.2, 4.1.4 or later for version 4.1. If patching is not immediately possible, restrict network access to the vSphere GUI management interface.
IBM Tivoli Storage Manager for Virtual Environments 6.3.2.5+/6.4.3.1+/7.1.4+ or Tivoli Storage FlashCopy Manager for VMware 3.1.1.3+/3.2.0.6+/4.1.4+ (depending on your product line)
- 1. Identify the currently installed version of IBM Tivoli Storage Manager for Virtual Environments (Data Protection for VMware) or Tivoli Storage FlashCopy Manager for VMware
- 2. For Tivoli Storage Manager for Virtual Environments: If running version 6.3.x, upgrade to version 6.3.2.5 or later
- 3. For Tivoli Storage Manager for Virtual Environments: If running version 6.4.x, upgrade to version 6.4.3.1 or later
- 4. For Tivoli Storage Manager for Virtual Environments: If running version 7.1.x, upgrade to version 7.1.4 or later
- 5. For Tivoli Storage FlashCopy Manager for VMware: If running version 3.1.x, upgrade to version 3.1.1.3 or later
- 6. For Tivoli Storage FlashCopy Manager for VMware: If running version 3.2.x, upgrade to version 3.2.0.6 or later
- 7. For Tivoli Storage FlashCopy Manager for VMware: If running version 4.1.x, upgrade to version 4.1.4 or later
- 8. After upgrade, verify the Data Protection component is functioning correctly and review administrative access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7425 — 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-7425 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