CVE-2024-49819: IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 could allow a remote attacker to obta

Routine

MEDIUM 4.1DOWNGRADE

CVE-2024-49819 is a medium-severity flaw (CVSS 4.1) affecting security guardium key lifecycle manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 could allow a remote attacker to obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.1 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-319
Published	2024-12-17
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-12-17 18:15 UTCPublished CVE record published
2026-06-17 08:00 UTCUpdated Record last modified

ibm security guardium key lifecycle manager DOWNGRADE

Affected: 4.1.0 · 4.1.1 · 4.2.0 · 4.2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.1.0

1. Check installed version

apt-cache policy security-guardium-key-lifecycle-manager || rpm -q security-guardium-key-lifecycle-manager || security-guardium-key-lifecycle-manager --version

2. No fixed release: DOWNGRADE to a release before 4.1.0 (Debian / Ubuntu)

apt-cache madison security-guardium-key-lifecycle-manager sudo apt install security-guardium-key-lifecycle-manager=<VERSION_BEFORE_4.1.0> sudo apt-mark hold security-guardium-key-lifecycle-manager

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list security-guardium-key-lifecycle-manager sudo dnf downgrade security-guardium-key-lifecycle-manager-<VERSION_BEFORE_4.1.0> sudo dnf versionlock add security-guardium-key-lifecycle-manager

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-49819?

security guardium key lifecycle manager: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-49819 being exploited?

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

CVE-2024-49819 affects security guardium key lifecycle manager. Severity is medium (CVSS 4.1). IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 could allow a remote attacker to obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors.

How urgent is CVE-2024-49819?

Priority 19/100. No elevated risk signals yet.

Related CVEs

CVE-2024-49820 LOW 3.7 DOWNGRADE IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 could allow a remote attacker to obta
CVE-2024-49818 MEDIUM 4.3 DOWNGRADE IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 could allow a remote attacker to ob
CVE-2024-49817 MEDIUM 4.4 DOWNGRADE IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores user credentials in configurat
CVE-2024-49816 MEDIUM 4.9 DOWNGRADE IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores potentially sensitive informat

References

← Back to latest CVEs