IBM Security Guardium Key Lifecycle Manager vulnerabilities
29 vulnerabilities
Known vulnerabilities in IBM Security Guardium Key Lifecycle Manager, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2021-38976ibmsecurity_guardium_key_lifecycle_manager+1
EPSS score0.24%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 stores user credentials in plain clear text which can be read by a local user. X-Force ID: 212781.CVE-2021-38983ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.91%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 212792.CVE-2021-38977ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.53%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 212782.CVE-2021-38975ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.97%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 could allow an authenticated user to to obtain sensitive information from a specially crafted HTTP request. IBM X-Force ID: 212780.CVE-2021-38974ibmsecurity_guardium_key_lifecycle_manager+1EPSS score1.00%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 could allow an authenticated user to cause a denial of service using specially crafted HTTP requests. IBM X-Force ID: 212779.CVE-2021-38980ibmsecurity_guardium_key_lifecycle_manager+1EPSS score1.23%
IBM Tivoli Key Lifecycle Manager (IBM Security Guardium Key Lifecycle Manager) 3.0, 3.0.1, 4.0, and 4.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. IBM X-Force ID: 212786.CVE-2021-38972ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.63%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.CVE-2021-38985ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.63%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.CVE-2021-38978ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.89%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.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 the middle techniques. IBM X-Force ID: 212783.CVE-2021-38982ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.53%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 212791.CVE-2021-38984ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.63%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 212793.CVE-2021-38981ibmsecurity_guardium_key_lifecycle_manager+1EPSS score1.37%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.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. IBM X-Force ID: 212788.CVE-2021-38979ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.71%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the software does not also use a salt as part of the input. IBM X-Force ID: 212785.CVE-2021-38973ibmsecurity_guardium_key_lifecycle_manager+1EPSS score0.59%
IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.CVE-2024-49818ibmsecurity_guardium_key_lifecycle_managerEPSS score0.47%
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.CVE-2024-49820ibmsecurity_guardium_key_lifecycle_managerEPSS score0.25%
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 the middle techniques.CVE-2024-49819ibmsecurity_guardium_key_lifecycle_managerEPSS score0.26%
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.CVE-2024-49817ibmsecurity_guardium_key_lifecycle_managerEPSS score0.19%
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.CVE-2024-49816ibmsecurity_guardium_key_lifecycle_managerEPSS score0.35%
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.CVE-2023-47707ibmsecurity_guardium_key_lifecycle_managerEPSS score0.44%
IBM Security Guardium Key Lifecycle Manager 4.3 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 271522.