dbcve.org
Debian LinuxOperating system · Debian

CVE-2019-16942

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-01
Fix available
A fix is available. Upgrade to 2.6.7.3 / 2.8.11.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the commons-dbcp (1.4) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of org.apache.commons.dbcp.datasources.SharedPoolDataSource and org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.

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
How this class of weakness works · CWE-502

The application rebuilds objects from attacker-supplied serialized data, and the act of rebuilding can trigger dangerous code paths. In many runtimes this leads straight to remote code execution. The durable fix is to avoid deserializing untrusted input — or to use a strict, type-limited format with integrity checks.

General guidance for the deserialization of untrusted data class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Debian LinuxOperating system
Affected:= 8.0= 9.0= 10.0
FedoraOperating system
Affected:= 30= 31
Jboss Enterprise Application PlatformApplication
Affected:= 7.2.0= 7.3
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
Jackson DatabindApplication
Affected:>= 2.0.0, < 2.6.7.3>= 2.8.0, < 2.8.11.5>= 2.9.0, < 2.9.10.1
Oncommand Api ServicesApplication
Affected:all versions
Oncommand Workflow AutomationApplication
Affected:all versions
Service Level ManagerApplication
Affected:all versions

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

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
Upgrade available Upgrade to 2.6.7.3 / 2.8.11.5 / 2.9.10.1 or later
Fixed in 2.6.7.32.8.11.52.9.10.1
Vendor patch github.com →
Recommended fix High confidence

Jackson Databind 2.9.10.1 (or latest 2.x stable release)

  1. 1. Identify all applications and services that use jackson-databind in your environment
  2. 2. Determine the current version of jackson-databind in use by checking your dependency management (Maven pom.xml, Gradle build.gradle, or JAR file metadata)
  3. 3. Upgrade jackson-databind to version 2.9.10.1 or later (recommended: latest 2.x stable release such as 2.10.x or 2.11.x)
  4. 4. For Maven projects, update the dependency in pom.xml: <groupId>com.fasterxml.jackson.core</groupId><artifactId>jackson-databind</artifactId><version>2.9.10.1</version>
  5. 5. For Gradle projects, update: implementation 'com.fasterxml.jackson.core:jackson-databind:2.9.10.1'
  6. 6. Rebuild and redeploy all affected applications
  7. 7. Verify the upgrade by checking that the new version is loaded at runtime
  8. 8. Test that all JSON serialization/deserialization functionality works correctly after the upgrade
Caveat Minimal risk - this is a patch release fixing a security vulnerability; however, always test in a staging environment before production deployment as minor API behavior changes may occur between minor versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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