Jboss Enterprise Application PlatformApplication · Redhat
CVE-2019-3873
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 · uneditedIt was found that Picketlink as shipped with Jboss Enterprise Application Platform 7.2 would accept an xinclude parameter in SAMLresponse XML. An attacker could use this flaw to send a URL to achieve cross-site scripting or possibly conduct further attacks.
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 confidencePicketlink as shipped with JBoss EAP 7.2 fails to properly restrict XInclude processing in SAML response XML parsing, allowing injection of external XML content that can trigger cross-site scripting (XSS).
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
Jboss Enterprise Application PlatformApplication
= 7.2.0
Single Sign OnApplication
= 7.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 JBoss EAP installationRun 'jboss-cli.sh --version' or check the installed product version from the JBoss EAP installation directory, typically found in $JBOSS_HOME/bin/jboss-cli.sh or through the management console.Affected if The installed version is exactly JBoss EAP 7.2.0
-
Identify Red Hat Single Sign On versionCheck the RH SSO installation for its version, typically found in the product manifest or version files within the RH SSO distribution.Affected if The installed version is RH SSO 7.0
-
Determine if SAML authentication is in useReview the JBoss configuration files (standalone.xml or domain.xml) for SAML-based identity provider (IdP) or service provider (SP) configurations, looking for Picketlink or Keycloak SAML-related security domains.Affected if SAML authentication is configured and enabled in the JBoss environment
-
Inspect XML parser configuration for SAML processingExamine the JBoss XML parser configuration or the Picketlink/Keycloak SAML parser settings to verify whether XInclude processing is enabled. This may be in XML transformerFactory settings or in the SAML valve/processor configuration files.Affected if XInclude processing is enabled in the XML parser configuration used for SAML response parsing
A user is affected if they are running JBoss EAP 7.2.0 or RH SSO 7.0 with SAML authentication enabled and XInclude processing is not explicitly disabled in the XML parser configuration for SAML responses.
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 the vendor patch or upgrade JBoss EAP to a version with the fixed Picketlink release, and configure XML parsers to disable XInclude processing for SAML responses.
Fix this in Jboss Enterprise Application Platform
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3873 — 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-2019-3873 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