Jackson applications that deserialize attacker-controlled JSON with insecure polymorphic type handling can be coerced into instantiating dangerous classes. Research tracked as CVE-2019-12384 showed that ch.qos.logback.core.db.DriverManagerConnectionSource can be used as a gadget to initiate attacker-selected JDBC connections, creating server-side request forgery (SSRF) and denial-of-service exposure.
Where the H2 JDBC driver is available, a crafted JDBC URL using H2's INIT=RUNSCRIPT capability can load a remote SQL script and escalate the condition to remote code execution. Jackson's historic reliance on a denylist of known gadget classes means newly identified gadgets may remain exploitable until blocked; organizations should avoid unsafe polymorphic/default typing for untrusted input, update Jackson and dependent Java libraries, and review applications for exposed deserialization endpoints.

See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
Andrea Brancaleoni published Doyensec research describing CVE-2019-12384, in which unsafe Jackson polymorphic deserialization can be exploited with the Logback DriverManagerConnectionSource gadget. The research demonstrated SSRF and denial-of-service effects, with H2's JDBC INIT=RUNSCRIPT feature enabling remote code execution when the H2 driver is available.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
medium.com
Open sourcegithub.com
Open sourceblog.doyensec.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.