CVE-2021-20361
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 Cloud Pak for Applications 4.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: 195032.
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 Cloud Pak for Applications 4.3 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed malicious JavaScript code that executes within a trusted user session, potentially leading to 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= 4.3CVSS 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 installed IBM Cloud Pak for Applications versionRun 'ibmcloud cr app-list' or check the operator deployment version via 'oc get operandrequest -A' to retrieve the exact version of Cloud Pak for Applications installed in your clusterAffected if The version returned is exactly 4.3 (not a later patched version)
-
Confirm Web UI component is accessibleAttempt to access the Cloud Pak for Applications Web UI at its expected route (typically through the OpenShift console or via 'oc get routes' looking for application-related routes)Affected if The Web UI is reachable and accepts user input without additional authentication layers that would prevent the stored XSS attack path
-
Review application logs for XSS injection attemptsSearch container logs for the Web UI pods (found via 'oc get pods -A | grep -i app') using 'oc logs <pod-name>' and grep for suspicious script tags, JavaScript event handlers, or encoded payloadsAffected if Logs contain evidence of script injection attempts or unusual HTML/script content in user input fields
-
Audit stored user content in the Web UI databaseIf you have database access, query the application backing store for user-generated content fields (such as descriptions, names, or comments) that may contain stored script tagsAffected if Stored content contains unsanitized script tags or JavaScript event handlers (onerror, onload, etc.) that would execute when rendered in a browser
You are affected if your IBM Cloud Pak for Applications installation is exactly version 4.3 and the Web UI is enabled and accessible to 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 dataUpgrade to an IBM Cloud Pak for Applications version that includes the security fix for CVE-2021-20361. Implement robust input validation and output encoding for all user-supplied content rendered in the Web UI.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20361 — 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-20361 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