CVE-2024-45671
BaseFortify
Publication date: 2025-09-10
Last updated on: 2025-09-17
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ibm | security_verify_information_queue | From 10.0.5 (inc) to 10.0.11 (exc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-327 | The product uses a broken or risky cryptographic algorithm or protocol. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in IBM Security Verify Information Queue versions 10.0.5 through 10.0.8 involves the use of weaker than expected cryptographic algorithms. This weakness could allow an attacker to decrypt highly sensitive information that should otherwise be protected by strong encryption. [1]
How can this vulnerability impact me? :
The impact of this vulnerability is that an attacker could potentially decrypt highly sensitive information, leading to a loss of confidentiality. This could expose private or critical data to unauthorized parties, increasing the risk of data breaches and compromising the security of your systems. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability could negatively affect compliance with standards and regulations such as GDPR and HIPAA, which require strong protection of sensitive data. The use of weaker cryptographic algorithms that allow decryption of sensitive information may lead to violations of data protection requirements, potentially resulting in legal and regulatory consequences. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2024-45671 in IBM Security Verify Information Queue, you should apply the latest patches and updates provided by IBM that address the use of weaker cryptographic algorithms. Additionally, review and upgrade any third-party libraries related to cryptography used by ISIQ to versions that fix this issue. Follow IBM's security bulletin recommendations to ensure all components are updated to secure versions. [1]