First published: Tue Mar 07 2017(Updated: )
IBM QRadar 7.2 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM Reference #: 1999534.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security QRadar Incident Forensics | =7.2.0 | |
IBM Security QRadar Incident Forensics | =7.2.1 | |
IBM Security QRadar Incident Forensics | =7.2.2 | |
IBM Security QRadar Incident Forensics | =7.2.3 | |
IBM Security QRadar Incident Forensics | =7.2.4 | |
IBM Security QRadar Incident Forensics | =7.2.5 | |
IBM Security QRadar Incident Forensics | =7.2.6 | |
IBM Security QRadar Incident Forensics | =7.2.7 | |
IBM Security QRadar Incident Forensics | =7.2.8 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9723 has a medium severity rating due to its potential to allow cross-site scripting attacks.
To fix CVE-2016-9723, update IBM QRadar Incident Forensics or Security Information and Event Manager to a version that patches the cross-site scripting vulnerability.
CVE-2016-9723 affects IBM QRadar versions 7.2.0 through 7.2.8.
The impact of CVE-2016-9723 is the potential disclosure of user credentials through the execution of malicious JavaScript in the Web UI.
IBM is responsible for addressing CVE-2016-9723, and users should follow their guidance for updates related to this vulnerability.