First published: Fri Feb 15 2019(Updated: )
IBM QRadar SIEM 7.2 and 7.3 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 134177.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM QRadar Security Information and Event Manager | >=7.2.0<=7.2.8 | |
IBM QRadar Security Information and Event Manager | >=7.3.0<=7.3.1 | |
IBM QRadar Security Information and Event Manager | =7.2.8 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p1 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p10 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p11 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p2 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p3 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p4 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p5 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p6 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p7 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p8 | |
IBM QRadar Security Information and Event Manager | =7.2.8-p9 | |
IBM QRadar Security Information and Event Manager | =7.3.1 | |
IBM QRadar Security Information and Event Manager | =7.3.1-p1 | |
IBM QRadar Security Information and Event Manager | =7.3.1-p2 | |
IBM QRadar Security Information and Event Manager | =7.3.1-p3 | |
IBM QRadar Security Information and Event Manager | =7.3.1-p4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2017-1695 is considered to be high due to the potential for sensitive data decryption.
To fix CVE-2017-1695, you should upgrade IBM QRadar SIEM to the latest version that addresses this vulnerability.
IBM QRadar SIEM versions 7.2.x and 7.3.0 to 7.3.1 are affected by CVE-2017-1695.
CVE-2017-1695 puts highly sensitive information at risk due to weaker than expected cryptographic algorithms.
There are no official workarounds for CVE-2017-1695; the best action is to upgrade to a secure version.