dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2019-10202

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.

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

CVE-2019-10202 addresses multiple deserialization vulnerabilities in FasterXML jackson-databind used in JBoss EAP 7. Attackers can exploit unsafe deserialization through specially crafted JSON payloads to achieve remote code execution. The fix implements a whitelist-based approach that restricts which classes can be deserialized, mitigating both the known vulnerabilities and potential future deserialization flaws.

MitigationUpgrade jackson-databind to a version with the whitelist deserialization protection enabled, or configure the existing installation with explicit class whitelisting to prevent unsafe deserialization of arbitrary classes.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

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

  1. Identify JBoss EAP installation and version
    Check for JBoss EAP 7.2.0 installation by examining the product.conf file (typically in /etc/jboss-eap/ or the EAP installation's bin/standalone.conf) or by querying the JBoss management interface with: /opt/jboss-eap-7.2/bin/jboss-cli.sh --connect --command='/core-service=server-environment:read-attribute(name=product-version)'
    Affected if The installed version is exactly 7.2.0 (note: other versions like 7.1.x or 7.3.x are NOT affected by this specific CVE)
  2. Locate jackson-databind library in use
    Search for jackson-databind JAR files in the JBoss deployment directories: find /opt/jboss-eap-7.2 -name 'jackson-databind*.jar' 2>/dev/null. Also check module dependencies in $JBOSS_HOME/modules/ for jackson-databind references.
    Affected if jackson-databind library is present in the JBoss EAP 7.2.0 installation
  3. Check for deserialization blacklist/whitelist configuration
    Examine the JBoss configuration files (standalone.xml, domain.xml) for deserialization security settings. Search for keywords: 'jackson', 'deserialization', 'whitelist', 'blacklist', 'PolymorphicTypeValidator', 'DefaultTyping' in configuration files under $JBOSS_HOME/standalone/configuration/ or $JBOSS_HOME/domain/configuration/
    Affected if No whitelist-based class restriction is configured for Jackson deserialization (the vulnerability exists if unchecked deserialization is allowed)
  4. Inspect deployed applications using Jackson
    Review deployed WAR/JAR applications for direct use of ObjectMapper with default typing enabled. Check application WEB-INF/web.xml and MANIFEST.MF files for Jackson dependencies, and examine application logs for deserialization-related error messages or known gadget chain usage.
    Affected if Applications deployed on JBoss EAP 7.2.0 use Jackson ObjectMapper with DefaultTyping enabled without explicit class restrictions

A system is affected by CVE-2019-10202 only if it is running JBoss EAP 7.2.0 with jackson-databind in use AND without whitelist-based deserialization protection configured for Jackson.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade jackson-databind to a version with the whitelist deserialization protection enabled, or configure the existing installation with explicit class whitelisting to prevent unsafe deserialization of arbitrary classes.

Recommended fix Moderate confidence

JBoss EAP 7.2 with CVE-2019-10202 patch applied (check Red Hat Security Advisory RHSA for specific patch version)

  1. 1. Identify all applications and services running on JBoss EAP 7.2.0 that use FasterXML Jackson-databind for deserialization.
  2. 2. Review application dependencies to confirm usage of vulnerable Jackson-databind versions (1.9.x).
  3. 3. Back up all configuration files and application data before performing any upgrade.
  4. 4. Apply the appropriate JBoss EAP 7.2 security patch or upgrade to a version that includes the CVE-2019-10202 fix.
  5. 5. Verify that the whitelist approach for deserialization is properly configured per Red Hat guidance.
  6. 6. Restart JBoss EAP services after applying the patch or upgrade.
  7. 7. Test all applications that utilize JSON deserialization to ensure functionality is intact.
  8. 8. Monitor logs for any deserialization-related errors or security events post-patch.
Caveat Whitelist approach may break existing applications that rely on deserialization of types not included in the whitelist; review and update type allowlists as needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10202 — 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-10202 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