dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2019-10172

HIGH · 7.5 CVSS v3.1 Published 2019-11-18
Fix available
A fix is available. Upgrade to after 1.9.13 or later.
See remediation →
84/100
Remediation priority · High
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 flaw was found in org.codehaus.jackson:jackson-mapper-asl:1.9.x libraries. XML external entity vulnerabilities similar CVE-2016-3720 also affects codehaus jackson-mapper-asl libraries but in different classes.

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 confidence

This is an XML External Entity (XXE) injection vulnerability in jackson-mapper-asl 1.9.x libraries, similar to CVE-2016-3720 but affecting different classes. When parsing XML input, the library does not properly disable external entity processing, allowing attackers to access local files or internal resources via crafted XML documents.

MitigationUpgrade from jackson-mapper-asl 1.9.x to a patched version (2.x series or later), or configure the XML parser to disable external entity and DTD processing.

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.0
Jboss FuseApplication
Affected:= 7.0.0
Debian LinuxOperating system
Affected:= 8.0= 9.0
SparkApplication
Affected:= 3.0.1
Jackson Mapper AslApplication
Affected:>= 1.9.0, <= 1.9.13

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Locate jackson-mapper-asl library
    Search for jackson-mapper-asl-*.jar in your application directory, build dependencies (Maven pom.xml, Gradle build.gradle), or Java classpath. Use: find . -name 'jackson-mapper-asl*.jar' or grep -r 'jackson-mapper-asl' pom.xml build.gradle
    Affected if The library is present in your environment
  2. Determine installed version
    Inspect the filename or the MANIFEST.MF inside the JAR for the version number. For Maven/Gradle projects, check the dependency declaration. Compare against the affected range: 1.9.0 through 1.9.13 inclusive
    Affected if Version is 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.10, 1.9.11, 1.9.12, or 1.9.13
  3. Verify XML deserialization is used
    Search code for XmlMapper usage, @XmlElement annotations, or ObjectMapper readValue() calls with XML content. Check if application accepts XML input via REST endpoints, file uploads, or message queues
    Affected if Application parses XML documents using Jackson XML functionality
  4. Inspect XML parser security configuration
    Review code that creates XmlMapper or XmlParser. Check if factory features like XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES or DISALLOW_DOCTYPE_DECL are explicitly configured. Search for calls to setFeature() or property setters on the XML parser
    Affected if XML parser has no explicit disabling of external entities or DTD processing (XXE protection not configured)

You are affected if jackson-mapper-asl version 1.9.x is present AND your application parses XML input with default parser settings that do not explicitly disable external entity processing.

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
Upgrade available Upgrade to a release after 1.9.13
Interim mitigation

Upgrade from jackson-mapper-asl 1.9.x to a patched version (2.x series or later), or configure the XML parser to disable external entity and DTD processing.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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