CVE-2018-12022

jackson-databind Deserialization of Untrusted Data vulnerability

An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2018-12022 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.6, 2.7.9.4, 2.8.11.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2018-12022? CVE-2018-12022 is a high-severity insecure deserialization vulnerability in com.fasterxml.jackson.core:jackson-databind (maven), affecting versions >= 2.9.0, < 2.9.6. It is fixed in 2.9.6, 2.7.9.4, 2.8.11.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2018-12022? CVE-2018-12022 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.fasterxml.jackson.core:jackson-databind are affected by CVE-2018-12022? com.fasterxml.jackson.core:jackson-databind (maven) versions >= 2.9.0, < 2.9.6 is affected.
4. Is there a fix for CVE-2018-12022? Yes. CVE-2018-12022 is fixed in 2.9.6, 2.7.9.4, 2.8.11.2. Upgrade to this version or later.
5. Is CVE-2018-12022 exploitable, and should I be worried? Whether CVE-2018-12022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2018-12022 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2018-12022?
   • Upgrade com.fasterxml.jackson.core:jackson-databind to 2.9.6 or later
   • Upgrade com.fasterxml.jackson.core:jackson-databind to 2.7.9.4 or later
   • Upgrade com.fasterxml.jackson.core:jackson-databind to 2.8.11.2 or later

Other vulnerabilities in com.fasterxml.jackson.core:jackson-databind