CVE-2019-16942

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote code execution via Java deserialization in Jackson databind when Default Typing is enabled and commons-dbcp is in the classpath. Attackers can exploit this to execute arbitrary code on vulnerable systems. Affected systems include any application using Jackson databind 2.0.0 through 2.9.10 with commons-dbcp 1.4 and exposed JSON endpoints.

💻 Affected Systems

Products:
  • FasterXML jackson-databind
Versions: 2.0.0 through 2.9.10
Operating Systems: All platforms running Java
Default Config Vulnerable: ✅ No
Notes: Requires Default Typing enabled (globally or per property) AND commons-dbcp 1.4 in classpath AND exposed JSON endpoint

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise with remote code execution leading to data theft, ransomware deployment, or complete system takeover.

🟠

Likely Case

Remote code execution allowing attackers to install backdoors, exfiltrate data, or pivot to other systems.

🟢

If Mitigated

Limited impact if proper network segmentation, input validation, and security controls prevent exploitation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires finding RMI service endpoint and crafting malicious payload

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.9.10.1 or later

Vendor Advisory: https://github.com/FasterXML/jackson-databind/issues/2387

Restart Required: Yes

Instructions:

1. Update jackson-databind to version 2.9.10.1 or later. 2. Update commons-dbcp to version 2.0 or later. 3. Restart affected applications.

🔧 Temporary Workarounds

Disable Default Typing

all

Disable Default Typing globally and for all properties in Jackson configuration

Configure ObjectMapper with disableDefaultTyping()

Remove commons-dbcp

all

Remove or update commons-dbcp library from classpath

Remove commons-dbcp-1.4.jar from application classpath

🧯 If You Can't Patch

  • Implement strict network controls to limit access to JSON endpoints
  • Use application firewalls to filter malicious JSON payloads

🔍 How to Verify

Check if Vulnerable:

Check application dependencies for jackson-databind version 2.0.0-2.9.10 and commons-dbcp 1.4

Check Version:

mvn dependency:tree | grep jackson-databind && mvn dependency:tree | grep commons-dbcp

Verify Fix Applied:

Verify jackson-databind version is 2.9.10.1+ and commons-dbcp is 2.0+

📡 Detection & Monitoring

Log Indicators:

  • Unusual deserialization errors
  • Unexpected RMI connections
  • Class loading exceptions

Network Indicators:

  • Suspicious JSON payloads to endpoints
  • RMI traffic to unexpected destinations

SIEM Query:

source="application.logs" AND ("jackson" OR "deserialization") AND ("error" OR "exception")

🔗 References

📤 Share & Export