dbcve.org
Storage Defender Resiliency ServiceApplication · Ibm

CVE-2024-27261

MEDIUM · 6.8 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 2.0.3 or later.
See remediation →
70/100
Remediation priority · Elevated
Zero-click

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 · unedited
IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.2 could allow a privileged user to install a potentially dangerous tar file, which could give them access to subsequent systems where the package was installed. IBM X-Force ID: 283986.

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 confidence

IBM Storage Defender Resiliency Service versions 2.0.0-2.0.2 lacks proper validation on tar file installations, allowing a privileged authenticated user to install a malicious tar archive that can execute code or escalate privileges to subsequent systems where the package is deployed.

MitigationUpgrade to IBM Storage Defender Resiliency Service version 2.0.3 or later. Until patched, restrict administrative access and monitor for unauthorized package installations.

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
Storage Defender Resiliency ServiceApplication
Affected:>= 2.0, < 2.0.3

CVSS 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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if IBM Storage Defender Resiliency Service is installed
    Check the installed version of IBM Storage Defender Resiliency Service using the product's version command or check the installed packages on the system. Compare your version against the affected range 2.0.0-2.0.2.
    Affected if The installed version is 2.0.0, 2.0.1, or 2.0.2 (any version from 2.0 through 2.0.2 inclusive).
  2. Determine if tar file package installation is in use
    Review the product configuration or logs to see if tar archive package installation features are enabled or have been used. Check for any installed packages or deployment configurations.
    Affected if Tar file installation capability is available or has been used in the environment.
  3. Review installation logs for unauthorized tar archives
    Examine product installation or deployment logs for any tar archive installations. Look for timestamps, usernames, and source locations of installed packages.
    Affected if There are log entries showing installation of tar archives from untrusted or unexpected sources, or installations performed by unauthorized users.
  4. Check for suspicious newly installed packages or scripts
    Inspect the file system where packages are deployed after installation. Look for unexpected executables, scripts, or modified system components that may have been installed via a malicious tar archive.
    Affected if Unexpected executables, scripts, or modified binaries are found in the deployment directories.

You are affected if IBM Storage Defender Resiliency Service version 2.0.0-2.0.2 is installed and the tar file installation feature is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.0.3 or later
Fixed in 2.0.3
Interim mitigation

Upgrade to IBM Storage Defender Resiliency Service version 2.0.3 or later. Until patched, restrict administrative access and monitor for unauthorized package installations.

Recommended fix High confidence

IBM Storage Defender Resiliency Service 2.0.3

  1. 1. Back up the current IBM Storage Defender Resiliency Service configuration and data
  2. 2. Consult IBM's official documentation for upgrading Storage Defender Resiliency Service
  3. 3. Download IBM Storage Defender Resiliency Service version 2.0.3 from IBM Fix Central or authorized distribution channels
  4. 4. Stop the Storage Defender Resiliency Service following IBM's recommended shutdown procedure
  5. 5. Install version 2.0.3 following the IBM installation guide
  6. 6. Verify the installation was successful and the service starts correctly
  7. 7. Validate that the vulnerability is resolved by checking the service version
Caveat Review IBM's release notes for version 2.0.3 to check for any compatibility or configuration changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storage Defender Resiliency Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27261 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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