<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: security guardium key lifecycle manager</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-49820: 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</title><link>https://patchthecve.com/cve/CVE-2024-49820.html</link><guid>https://patchthecve.com/cve/CVE-2024-49820.html</guid><pubDate>Wed, 17 Jun 2026 08:00:29 +0000</pubDate><description>LOW 3.7: 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, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in t</description></item><item><title>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</title><link>https://patchthecve.com/cve/CVE-2024-49819.html</link><guid>https://patchthecve.com/cve/CVE-2024-49819.html</guid><pubDate>Wed, 17 Jun 2026 08:00:29 +0000</pubDate><description>MEDIUM 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.</description></item><item><title>CVE-2024-49818: 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</title><link>https://patchthecve.com/cve/CVE-2024-49818.html</link><guid>https://patchthecve.com/cve/CVE-2024-49818.html</guid><pubDate>Wed, 17 Jun 2026 08:00:29 +0000</pubDate><description>MEDIUM 4.3: 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 when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.</description></item><item><title>CVE-2024-49817: IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores user credentials in configurat</title><link>https://patchthecve.com/cve/CVE-2024-49817.html</link><guid>https://patchthecve.com/cve/CVE-2024-49817.html</guid><pubDate>Wed, 17 Jun 2026 08:00:28 +0000</pubDate><description>MEDIUM 4.4: IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores user credentials in configuration files which can be read by a local privileged user.</description></item><item><title>CVE-2024-49816: IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores potentially sensitive informat</title><link>https://patchthecve.com/cve/CVE-2024-49816.html</link><guid>https://patchthecve.com/cve/CVE-2024-49816.html</guid><pubDate>Wed, 17 Jun 2026 08:00:28 +0000</pubDate><description>MEDIUM 4.9: IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores potentially sensitive information in log files that could be read by a local privileged user.</description></item></channel></rss>