dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2019-3872

MEDIUM · 5.4 CVSS v3.0 Published 2019-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
It was found that a SAMLRequest containing a script could be processed by Picketlink versions shipped in Jboss Application Platform 7.2.x and 7.1.x. An attacker could use this to send a malicious script to achieve cross-site scripting and obtain unauthorized information or 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 confidence

Picketlink (an identity and access management library for JBoss) fails to properly sanitize or validate script content in SAMLRequest parameters during SAML authentication processing. This allows stored XSS attacks where malicious JavaScript can be injected and executed in the context of legitimate users' sessions when they authenticate via SAML.

MitigationUpgrade Picketlink to a patched version or migrate to the newer Keycloak-based identity solution. Until patched, implement input validation filters on SAML endpoints to reject requests containing script tags or dangerous characters.

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
Affected:= 7.2.0
Single Sign OnApplication
Affected:= 7.0

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Picketlink deployment
    Search for picketlink-core.jar or picketlink-idm*.jar files in the JBoss application server installation directories (typically under $JBOSS_HOME/modules or within deployed applications). Also check for PicketLink references in server logs during startup.
    Affected if Picketlink libraries are present in the JBoss environment
  2. Confirm JBoss EAP or RH SSO version
    Run 'rpm -q jboss-enterprise-application-platform' or check the manifest file (MANIFEST.MF) within the jboss-modules.jar or check the version displayed in the admin console. For RH SSO, check 'rpm -q rh-sso7' or examine the product version in the server banner.
    Affected if Version equals 7.2.0 for JBoss EAP or 7.0 for RH SSO
  3. Verify SAML authentication is enabled
    Inspect the JBoss configuration files (standalone.xml or domain.xml) for <identity-provider> or SAML-related configuration under the security subsystems. Also check for any deployed applications using PicketLink's SAML functionality.
    Affected if SAML identity provider or service provider configuration exists and is active
  4. Check SAML endpoint exposure
    Examine web.xml files in deployed applications for SAML-related servlet mappings (typically endpoints containing 'SAML' or 'saml' in the URL pattern). Review reverse proxy or load balancer configurations for SAML endpoint routing.
    Affected if SAML endpoints that process SAMLRequest parameters are publicly accessible
  5. Inspect for suspicious SAML content in logs
    Review JBoss server logs (server.log) and HTTP access logs for SAML authentication attempts. Search for unusual patterns in SAMLRequest parameter values, particularly those containing '<script>', 'javascript:', or encoded script tags.
    Affected if Log entries show SAMLRequest values with script injection patterns or evidence of XSS attempts

A defender is affected if Picketlink is deployed within JBoss EAP 7.2.0 or RH SSO 7.0 and SAML authentication processing is enabled, exposing SAML endpoints that handle the SAMLRequest parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Picketlink to a patched version or migrate to the newer Keycloak-based identity solution. Until patched, implement input validation filters on SAML endpoints to reject requests containing script tags or dangerous characters.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3872 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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