CVE-2020-24353
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 · uneditedPega Platform before 8.4.0 has a XSS issue via stream rule parameters used in the request header.
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 confidencePega Platform before version 8.4.0 contains a Cross-Site Scripting (XSS) vulnerability in stream rule parameters that are processed through the request header. This reflected XSS flaw allows attackers to inject malicious scripts through crafted header values that are rendered without proper sanitization.
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< 8.4CVSS 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.1/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.
-
Determine installed Pega Platform versionAccess the Pega Platform administration console or check the prengine.xml/logs for the version number. Typically found in the System Upgrade page or by querying the system via the Designer Studio (Help > About Pega Platform).Affected if The installed version is any release before 8.4.0 (for example, 8.3.x, 8.2.x, 8.1.x, or earlier)
-
Identify if stream rules are deployedIn Pega Designer Studio, navigate to Records > Technical > Stream Rule or search for rules with Rule-Stream type. Check the application inventory for any custom or out-of-the-box stream rules.Affected if Stream rules exist and are actively used by the application
-
Verify if stream rules accept header parametersExamine the stream rule configuration and any associated data transforms or activities that pass request header values (such as HTTP_USER_AGENT, HTTP_REFERER, or custom headers) into stream rule parameters. Review the stream rule XML or use the Rule Inspector.Affected if Request header values are passed into stream rule parameters without sanitization
-
Check for custom header processing logicSearch the Pega codebase (via Search > Technical > Activity or Data Transform) for activities that reference pxRequest or pyRequest parameters containing header data and feed them into stream processing.Affected if Custom activities or data transforms pass unsanitized header data to stream rules
-
Review web tier exposureConfirm that the Pega web tier (Pega API, Pega Web Mashup, or custom servlets) is accessible over HTTP/HTTPS and can receive arbitrary request headers from external users.Affected if The platform accepts external HTTP requests and forwards headers to stream rule processing
A user is affected if their Pega Platform installation version is before 8.4.0 AND stream rules that process request header parameters are in use and accessible to external 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 data8.4
Upgrade Pega Platform to version 8.4.0 or later to obtain the patch for this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24353 — 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-24353 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