CVE-2020-10968

8.8 HIGH

📋 TL;DR

This vulnerability in FasterXML jackson-databind allows remote code execution (RCE) via deserialization of untrusted data, exploiting a gadget chain involving org.aoju.bus.proxy.provider.remoting.RmiProvider. It affects applications using Jackson 2.x before 2.9.10.4 with default polymorphic typing enabled or specific configurations.

💻 Affected Systems

Products:
  • FasterXML jackson-databind
Versions: 2.x before 2.9.10.4
Operating Systems: All operating systems running Java applications with vulnerable Jackson versions
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability requires enabling polymorphic typing (e.g., with @JsonTypeInfo) or using specific deserialization features; default configurations in many frameworks may be vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

RCE allowing attackers to execute arbitrary commands on the server, potentially leading to data breaches or service disruption.

🟢

If Mitigated

Limited impact if input validation and deserialization controls are enforced, but risk persists without patching.

🌐 Internet-Facing: HIGH due to potential for unauthenticated exploitation via web APIs or services processing untrusted JSON.
🏢 Internal Only: MEDIUM as internal systems may still be vulnerable to insider threats or lateral movement.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploits leverage known gadget chains; public proof-of-concept code exists, making attacks straightforward for skilled adversaries.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.9.10.4 or later

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

Restart Required: Yes

Instructions:

1. Update jackson-databind dependency to version 2.9.10.4 or higher in your project's build configuration (e.g., Maven, Gradle). 2. Rebuild and redeploy the application. 3. Restart the application server to apply changes.

🔧 Temporary Workarounds

Disable polymorphic typing

all

Prevent deserialization of polymorphic types by disabling or restricting ObjectMapper configurations.

Configure ObjectMapper with disableDefaultTyping() or use a whitelist for allowed classes.

Block dangerous classes

all

Use Jackson's class blacklisting to block known malicious gadget classes.

Add org.aoju.bus.proxy.provider.remoting.RmiProvider and related classes to the deserialization blacklist in Jackson configuration.

🧯 If You Can't Patch

  • Implement strict input validation and sanitization for all JSON inputs to reject untrusted data.
  • Isolate the vulnerable application in a segmented network to limit potential lateral movement and monitor for anomalous activity.

🔍 How to Verify

Check if Vulnerable:

Check the jackson-databind version in your project dependencies; if it's below 2.9.10.4, you are vulnerable.

Check Version:

For Maven: mvn dependency:tree | grep jackson-databind; For Gradle: gradle dependencies | grep jackson-databind; In Java code: System.out.println(com.fasterxml.jackson.databind.cfg.PackageVersion.VERSION);

Verify Fix Applied:

After updating, verify the version is 2.9.10.4 or higher by checking the dependency manifest or running a version check command.

📡 Detection & Monitoring

Log Indicators:

  • Unusual deserialization errors, stack traces mentioning org.aoju.bus.proxy.provider.remoting.RmiProvider, or unexpected process spawns in application logs.

Network Indicators:

  • Suspicious inbound JSON payloads to APIs, especially with polymorphic type indicators, or outbound connections to unknown RMI services.

SIEM Query:

Example: source="app_logs" AND ("RmiProvider" OR "deserialization error")

🔗 References

📤 Share & Export