Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Security_guardium_key_lifecycle_manager
(Ibm)| Repositories |
Unknown: This might be proprietary software. |
| #Vulnerabilities | 29 |
| Date | Id | Summary | Products | Score | Patch | Annotated |
|---|---|---|---|---|---|---|
| 2024-12-17 | 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 obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors. | Security_guardium_key_lifecycle_manager | 7.5 | ||
| 2024-12-17 | 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 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. | Security_guardium_key_lifecycle_manager | 3.7 | ||
| 2024-12-17 | 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 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. | Security_guardium_key_lifecycle_manager | 4.3 | ||
| 2024-12-17 | CVE-2024-49816 | 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. | Security_guardium_key_lifecycle_manager | 4.4 | ||
| 2024-12-17 | 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 configuration files which can be read by a local privileged user. | Security_guardium_key_lifecycle_manager | 4.4 | ||
| 2024-02-28 | CVE-2023-25922 | IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. IBM X-Force ID: 247621. | Security_guardium_key_lifecycle_manager | 8.8 | ||
| 2024-02-28 | CVE-2023-25925 | IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 could allow a remote authenticated attacker to execute arbitrary commands on the system by sending a specially crafted request. IBM X-Force ID: 247632. | Security_guardium_key_lifecycle_manager | 8.8 | ||
| 2024-02-29 | CVE-2023-25921 | IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. IBM X-Force ID: 247620. | Security_guardium_key_lifecycle_manager | 8.8 | ||
| 2024-02-29 | CVE-2023-25926 | IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 247599. | Security_guardium_key_lifecycle_manager | 8.2 | ||
| 2021-11-12 | CVE-2021-38973 | 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. | Security_guardium_key_lifecycle_manager, Security_key_lifecycle_manager | 2.7 |