CVE-2021-20380
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 Advisor With Watson App 1.1 through 2.5 as used on IBM QRadar SIEM 7.4 could allow a remote user to obtain sensitive information from HTTP requests that could aid in further attacks against the system. IBM X-Force ID: 195712.
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 · moderate confidenceIBM QRadar Advisor With Watson App versions 1.1 through 2.5 contains a vulnerability that allows remote users to obtain sensitive information from HTTP requests. The exposed information could provide attackers with credentials, session tokens, or other data useful for further exploitation of the QRadar SIEM 7.4 system.
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>= 1.1.0, < 2.6.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 if QRadar Advisor With Watson app is installedIn the QRadar console, navigate to the App Management interface or use the command line to list installed apps. Look for an app named 'Advisor With Watson' in the list of installed applications.Affected if The app is present in the list of installed apps
-
Determine the installed version of QRadar Advisor With WatsonIn the QRadar App Management interface, click on the Advisor With Watson app to view its details, including the version number. Alternatively, examine the app's metadata file or configuration if accessible via command line.Affected if The version displayed is 1.1.0 through 2.5.x (anything >= 1.1.0 and < 2.6.1)
-
Compare your version against the vulnerable rangeRecord the exact version number identified in the previous step. Compare it to the affected range: versions 1.1.0 up to but not including 2.6.1 are vulnerable.Affected if Your version falls within >= 1.1.0 and < 2.6.1
-
Review HTTP request logs for sensitive data exposureExamine QRadar audit logs and HTTP access logs for any unusual or unauthorized requests to the Advisor With Watson application endpoints. Look for patterns indicating credentials, session tokens, or other sensitive data may have been exposed in request parameters or headers.Affected if Logs show unexpected requests accessing sensitive data or unauthorized access patterns to the app
You are affected if the QRadar Advisor With Watson app is installed and its version is 1.1.0 or higher but lower than 2.6.1.
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 data2.6.1
Upgrade IBM QRadar Advisor With Watson App to a version beyond 2.5 or apply the applicable IBM patch. Review HTTP request logs for signs of unauthorized access to sensitive data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20380 — 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-2021-20380 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