CVE-2025-13855
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 · uneditedIBM Storage Protect Server 8.2.0 IBM Storage Protect Plus Server is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
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 confidenceIBM Storage Protect Server 8.2.0 and Plus Server contain unsanitized SQL query inputs that allow remote attackers to inject malicious SQL statements via specially crafted requests. This can lead to unauthorized database access enabling view, add, modification, or deletion of data.
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.2.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 IBM Storage Protect Server installationLocate the IBM Storage Protect Server installation and determine its installed version using system inventory tools, product-specific commands, or by querying the installed packages/components. Common locations include /opt/tivoli/tsm or similar IBM product directories.Affected if The product IBM Storage Protect Server is installed and running on the system
-
Verify installed version matches 8.2.0Check the exact version number of the installed IBM Storage Protect Server instance. Use product-specific commands such as 'dsmadmc -v', 'dsmcmd query status', or consult the product's version information file in the installation directory.Affected if The installed version is exactly 8.2.0, as this is the specific version affected by this CVE
-
Determine network exposure of the serverReview network configuration to assess whether the IBM Storage Protect Server administrative interfaces or database ports are exposed to untrusted networks. Check firewall rules, listening ports (typically 1550, 1551, or custom DB ports), and access control lists.Affected if The server's administrative or database interfaces are accessible from untrusted or external networks, enabling remote attackers to send malicious SQL statements
-
Assess database interaction accessibilityExamine the server configuration to determine if the back-end database accepts direct SQL inputs or if web-facing interfaces allow SQL statement submission. Review any exposed APIs, administrative consoles, or query interfaces.Affected if The database layer accepts user-supplied input that could be manipulated with specially crafted SQL statements, as this is the attack vector for the vulnerability
A user is affected if they have IBM Storage Protect Server version 8.2.0 installed with its database or administrative interfaces accessible to potential attackers who could inject malicious SQL statements.
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 dataApply vendor-supplied patches for IBM Storage Protect. Until then, implement parameterized queries/prepared statements for all database operations, validate and sanitize all user inputs, and restrict database account privileges to minimum necessary.
- 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-2025-13855 — 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-2025-13855 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