CVE-2016-9738: High severity ibm qradar security information and event manager vulnerability

Published Jun 27, 2017
·
Updated

IBM QRadar 7.2 and 7.3 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 119783.

Affected Software

17 affected components
IBM QRadar Security Information and Event Manager=7.2.0
IBM QRadar Security Information and Event Manager=7.2.1
IBM QRadar Security Information and Event Manager=7.2.2
IBM QRadar Security Information and Event Manager=7.2.3
IBM QRadar Security Information and Event Manager=7.2.4
IBM QRadar Security Information and Event Manager=7.2.5
IBM QRadar Security Information and Event Manager=7.2.6
IBM QRadar Security Information and Event Manager=7.2.7
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-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.3.0
IBM QRadar Security Information and Event Manager=7.3.0-p1

Event History

Jun 27, 2017
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2016-9738?

The severity of CVE-2016-9738 is classified as medium due to the potential for account compromise from weak password policies.

2

How do I fix CVE-2016-9738?

To fix CVE-2016-9738, enforce strong password policies and configure user account controls in IBM QRadar.

3

Which versions of IBM QRadar are affected by CVE-2016-9738?

CVE-2016-9738 affects IBM QRadar versions 7.2.0 through 7.3.0, including all interim releases.

4

What are the risk implications of CVE-2016-9738?

The risk implications of CVE-2016-9738 include unauthorized access to sensitive information and potential data breaches.

5

Are there any recommended mitigations for CVE-2016-9738?

Recommended mitigations for CVE-2016-9738 include implementing password complexity requirements and regular account monitoring.

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