CVE-2020-4929
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 SIEM 7.3 and 7.4 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: 191706.
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 SIEM 7.3 and 7.4 contains a cross-site scripting (XSS) vulnerability in the Web UI that allows authenticated users to embed arbitrary JavaScript code. This stored XSS can execute within browsers of other users viewing the affected interface, potentially allowing credential disclosure through a trusted session.
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.3.0, < 7.3.3>= 7.4.0, < 7.4.2= 7.3.3= 7.4.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 QRadar installation versionLog into the QRadar Console as admin, navigate to the Admin tab, and click 'System Information' to view the installed version. Alternatively, run the command 'rpm -qqradar' on the console host to retrieve the package version.Affected if The displayed version falls within 7.3.0 to 7.3.3 inclusive or 7.4.0 to 7.4.2 inclusive.
-
Verify Web UI access is enabledConfirm that the QRadar Web UI is accessible by attempting to reach the console login page at https://<console_ip> or checking via the admin panel that the HTTP/HTTPS service is active.Affected if The Web UI is exposed and the QRadar version is in the affected range.
-
Confirm user authentication capabilityVerify that user accounts exist and authentication to the QRadar Web UI is possible. The vulnerability requires an authenticated user session to embed malicious JavaScript.Affected if Users can authenticate to the Web UI and the QRadar version is in the affected range.
A user is affected if their QRadar installation is version 7.3.0 through 7.3.3 or 7.4.0 through 7.4.2 and the Web UI is accessible for authenticated users.
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 data7.3.37.4.2
Apply IBM's security patch for CVE-2020-4929 to QRadar. Implement output encoding and input validation for user-supplied content in the web interface. Consider deploying Content Security Policy headers to mitigate XSS execution.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4929 — 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-2020-4929 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