CVE-2025-0160
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 FlashSystem (IBM Storage Virtualize (8.5.0.0 through 8.5.0.13, 8.5.1.0, 8.5.2.0 through 8.5.2.3, 8.5.3.0 through 8.5.3.1, 8.5.4.0, 8.6.0.0 through 8.6.0.5, 8.6.1.0, 8.6.2.0 through 8.6.2.1, 8.6.3.0, 8.7.0.0 through 8.7.0.2, 8.7.1.0, 8.7.2.0 through 8.7.2.1) could allow a remote attacker with access to the system to execute arbitrary Java code due to improper restrictions in the RPCAdapter service.
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 FlashSystem (Storage Virtualize) versions 8.5.0.0 through 8.7.2.1 contain a critical vulnerability in the RPCAdapter service where improper input validation and access restrictions allow an authenticated remote attacker to execute arbitrary Java code on the underlying system, achieving full remote code execution with system-level privileges.
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.5, < 8.5.0.14>= 8.5.2.0, <= 8.5.2.3>= 8.6.0.0, < 8.6.0.6>= 8.7.0.0, < 8.7.0.3= 8.5.1.0= 8.5.3.0= 8.5.3.1= 8.5.4.0= 8.6.1.0= 8.6.2.0= 8.6.2.1= 8.6.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.1/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 the installed Storage Virtualize versionUse the IBM Storage Virtualize management interface, CLI (lsversion command), or check the system firmware/machine code version. Compare the installed version number against the affected ranges: 8.5.0.0 through 8.5.0.13, 8.5.2.0 through 8.5.2.3, 8.5.1.0, 8.5.3.0, 8.5.3.1, 8.5.4.0, 8.6.0.0 through 8.6.0.5, 8.6.1.0, 8.6.2.0, 8.6.2.1, 8.6.3.0, 8.7.0.0 through 8.7.0.2Affected if The installed version falls within any of the listed affected version ranges
-
Confirm the RPCAdapter service is enabledAccess the Storage Virtualize management GUI or CLI and verify whether the RPCAdapter service is active. In the GUI, navigate to the services or configuration section. From CLI, use the appropriate command to list enabled services.Affected if RPCAdapter service is enabled and running on the system
-
Determine if RPCAdapter is exposed to the networkReview network configuration settings to check whether the RPCAdapter service port is accessible from external networks or untrusted interfaces. Check firewall rules and service binding configurations.Affected if RPCAdapter is bound to a network-accessible IP address or port and accepts remote connections
-
Audit for indicators of compromiseReview system logs, especially authentication and RPCAdapter service logs, for unexpected user accounts, unusual command executions, or suspicious API calls. Check for new or modified Java class files in the system filesystem.Affected if Unexpected authenticated sessions, arbitrary Java code execution artifacts, or unauthorized configuration changes are found in logs or filesystem
A user is affected if they run an affected version of IBM Storage Virtualize with the RPCAdapter service enabled and network-accessible to authenticated 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 · scoped8.5.0.148.6.0.68.7.0.3
Apply the IBM-provided patch or upgrade to a supported, unaffected version of Storage Virtualize. Restrict network access to the RPCAdapter service and audit for signs of compromise.
Upgrade to the latest version in your current branch: 8.5.0.14+, 8.6.0.6+, or 8.7.0.3+
- Identify the currently installed IBM Storage Virtualize version using the 'lsversion' command or through the management GUI
- Determine which version branch your current installation belongs to (8.5.x, 8.6.x, or 8.7.x)
- For version 8.5.x: Upgrade to 8.5.0.14 or later
- For version 8.6.x: Upgrade to 8.6.0.6 or later
- For version 8.7.x: Upgrade to 8.7.0.3 or later
- Schedule maintenance window as upgrade may require system downtime
- Back up configuration data before initiating upgrade
- Follow IBM's standard upgrade procedure for Storage Virtualize (usually via installable package or SAN Upgrade Wizard)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0160 — 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-0160 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