CVE-2024-38324: IBM Storage Defender 2.0.0 through 2.0.7 on-prem defender-sensor-cmd CLI does not validate server name during

Routine

MEDIUM 5.9REMOTEUPGRADE

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

IBM Storage Defender 2.0.0 through 2.0.7 on-prem defender-sensor-cmd CLI does not validate server name during registration and unregistration operations which could expose sensitive information to an attacker with access to the system.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-297, CWE-295
Published	2024-09-25
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-09-25 01:15 UTCPublished CVE record published
2026-06-17 07:39 UTCUpdated Record last modified

ibm storage defender UPGRADE

Affected: >= 2.0.0 and < 2.0.8

Fixed in: 2.0.8

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 2.0.8 (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-38324?

storage defender: upgrade to 2.0.8. Exact commands for each OS are on this page.

Is CVE-2024-38324 being exploited?

CVE-2024-38324 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-38324 affect?

CVE-2024-38324 affects storage defender. Severity is medium (CVSS 5.9). IBM Storage Defender 2.0.0 through 2.0.7 on-prem defender-sensor-cmd CLI does not validate server name during registration and unregistration operations which could expose sensitive information to an attacker with access to the system.

How urgent is CVE-2024-38324?

Priority 33/100. Remotely exploitable, no login, no user action

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-25031 MEDIUM 6.5 UPGRADE IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.4 uses an inadequate account lockout setting that

References

← Back to latest CVEs