CVE-2018-1648: Weak Encryption

Published Dec 5, 2018
·
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: 144653.

Affected Software

21 affected components
IBM QRadar Incident Forensics>=7.2.0<7.2.8
IBM QRadar Incident Forensics>=7.3.0<7.3.1
IBM QRadar Incident Forensics=7.2.8
IBM QRadar Incident Forensics=7.2.8-p1
IBM QRadar Incident Forensics=7.2.8-p10
IBM QRadar Incident Forensics=7.2.8-p11
IBM QRadar Incident Forensics=7.2.8-p12
IBM QRadar Incident Forensics=7.2.8-p13
IBM QRadar Incident Forensics=7.2.8-p3
IBM QRadar Incident Forensics=7.2.8-p4
IBM QRadar Incident Forensics=7.2.8-p5
IBM QRadar Incident Forensics=7.2.8-p6
IBM QRadar Incident Forensics=7.2.8-p7
IBM QRadar Incident Forensics=7.2.8-p8
IBM QRadar Incident Forensics=7.2.8-p9
IBM QRadar Incident Forensics=7.3.1
IBM QRadar Incident Forensics=7.3.1-p1
IBM QRadar Incident Forensics=7.3.1-p2
IBM QRadar Incident Forensics=7.3.1-p3
IBM QRadar Incident Forensics=7.3.1-p4
IBM QRadar Incident Forensics=7.3.1-p5

Event History

Dec 5, 2018
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-1648?

CVE-2018-1648 has a medium severity rating due to the use of weaker than expected cryptographic algorithms.

2

How do I fix CVE-2018-1648?

To fix CVE-2018-1648, update IBM QRadar Incident Forensics to version 7.2.9 or 7.3.2 or later.

3

What products are affected by CVE-2018-1648?

CVE-2018-1648 affects IBM QRadar Incident Forensics versions 7.2.0 to 7.2.8 and 7.3.0 to 7.3.1.

4

What kind of data could be exposed due to CVE-2018-1648?

Due to CVE-2018-1648, highly sensitive information could potentially be decrypted by attackers.

5

Is there a workaround for CVE-2018-1648?

There is no official workaround for CVE-2018-1648; the recommended solution is to apply the latest software updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203