CVE-2017-1623
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM QRadar 7.2 and 7.3 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 X-Force ID: 133121.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM QRadar 7.2 and 7.3 contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code into the interface, which executes in the context of trusted sessions, potentially allowing credential disclosure or session hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.2.0= 7.2.1= 7.2.2= 7.2.3= 7.2.4= 7.2.5= 7.2.6= 7.2.7= 7.2.8= 7.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed QRadar versionAccess the QRadar admin console or use the command line tool 'qversion' to retrieve the currently installed version of QRadar.Affected if The installed version is 7.2.0 through 7.2.8 or 7.3.0 exactly.
-
Confirm Web UI is enabledVerify that the QRadar Web UI (console) is accessible and operational by attempting to access the login page at the configured QRadar URL.Affected if The Web UI is exposed and active, as this is the attack surface for the stored XSS.
-
Check for recent administrative changesReview QRadar audit logs or event logs for any unexpected or unauthorized changes to Web UI configurations, custom rules, or dashboard widgets that may indicate XSS payload injection.Affected if Suspicious JavaScript-related entries appear in logs, particularly in fields related to dashboard customization or rule configuration.
-
Inspect browser session behaviorIf you have access to a test account, log into the Web UI and navigate to commonly used pages (dashboards, offense management, log activity) to observe if any unexpected script execution or alerts occur.Affected if Arbitrary JavaScript executes in the browser when viewing standard Web UI pages, indicating a stored XSS payload is present.
You are affected if your QRadar installation version is exactly 7.2.0 through 7.2.8 or 7.3.0 AND the Web UI is accessible, as the stored XSS vulnerability exists in the Web UI component of these versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches for QRadar 7.2 and 7.3, or upgrade to a patched version. Implement input validation and output encoding for user-supplied data in the Web UI.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1623 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1623 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data