CVE-2024-25031: IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.4 uses an inadequate account lockout setting that

Routine

MEDIUM 6.5UPGRADE

CVE-2024-25031 is a medium-severity flaw (CVSS 6.5) affecting storage defender. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.4 uses an inadequate account lockout setting that could allow an attacker on the network to brute force account credentials. IBM X-Force ID: 281678.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 84%)
CISA exploited list	No
Weakness	CWE-307
Published	2024-06-28
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-28 19:15 UTCPublished CVE record published
2026-06-17 07:15 UTCUpdated Record last modified

ibm storage defender UPGRADE

Affected: >= 2.0.0 and <= 2.0.4

Fixed in: newer than 2.0.4

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy storage-defender || rpm -q storage-defender || storage-defender --version

2. UPGRADE to newer than 2.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade storage-defender

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade storage-defender

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison storage-defender sudo apt install storage-defender=<VERSION_BEFORE_2.0.0> sudo apt-mark hold storage-defender

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list storage-defender sudo dnf downgrade storage-defender-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add storage-defender

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-25031?

storage defender: upgrade to newer than 2.0.4. Exact commands for each OS are on this page.

Is CVE-2024-25031 being exploited?

CVE-2024-25031 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-25031 affect?

CVE-2024-25031 affects storage defender. Severity is medium (CVSS 6.5). IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.4 uses an inadequate account lockout setting that could allow an attacker on the network to brute force account credentials. IBM X-Force ID: 281678.

How urgent is CVE-2024-25031?

Priority 27/100. No elevated risk signals yet.

Software pages

Windows Defender vulnerabilities

Related CVEs

CVE-2024-38325 MEDIUM 5.9 UPGRADE IBM Storage Defender 2.0.0 through 2.0.7 on-prem defender-sensor-cmd CLI could allow a remote attacker to ob
CVE-2024-38324 MEDIUM 5.9 UPGRADE IBM Storage Defender 2.0.0 through 2.0.7 on-prem defender-sensor-cmd CLI does not validate server name during

References

← Back to latest CVEs