UBUNTU-CVE-2017-15095: Critical severity ubuntu/jackson-databind vulnerability
A deserialization flaw was discovered in the jackson-databind in versions before 2.8.10 and 2.9.1, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525 by blacklisting more classes that could be used maliciously.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/jackson-databindto a version that resolves this vulnerability.Fixed in 2.2.2-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libjackson-json-javato a version that resolves this vulnerability.Fixed in 1.9.2-3+deb8u1build0.14.04.1~esm1 - Upgrade
Upgrade
ubuntu/libjackson-json-javato a version that resolves this vulnerability.Fixed in 1.9.2-7ubuntu0.2 - Upgrade
Upgrade
ubuntu/jackson-databindto a version that resolves this vulnerability.Fixed in 2.4.2-3ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libjackson-json-javato a version that resolves this vulnerability.Fixed in 1.9.13-1~18.04.1~esm1 - Upgrade
Upgrade
ubuntu/libjackson-json-javato a version that resolves this vulnerability.Fixed in 1.9.13-1ubuntu0.1~esm1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.8.10 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.9.1
Event History
Frequently Asked Questions
What application paths are exposed to this issue?
Any path that accepts attacker-controlled input and passes it to ObjectMapper.readValue is exposed. The affected component can be exploited remotely without authentication when such input reaches that method.
What conditions must an attacker meet to achieve code execution?
The attacker needs to send maliciously crafted serialized input to ObjectMapper.readValue. No privileges or user interaction are required according to the severity vector.
Which jackson-databind versions address this flaw?
Versions 2.8.10 and 2.9.1 address the issue; versions before those releases are affected.