Skip to content
OpenAdvisories
Critical USN-4813-1 39 CVEs

jackson-databind vulnerabilities

Published Mar 15, 2021 · Updated Oct 12, 2026

Summary

It was discovered that Jackson Databind incorrectly handled
deserialization. An attacker could possibly use this issue to obtain
sensitive information. (CVE-2018-11307, CVE-2019-12086, CVE-2019-12814)

It was discovered that Jackson Databind incorrectly handled
deserialization. An attacker could possibly use this issue to execute
arbitrary code or other unspecified impact. (CVE-2018-12022,
CVE-2018-12023, CVE-2018-14718, CVE-2018-14719, CVE-2018-19360,
CVE-2018-19361, CVE-2018-19362, CVE-2019-12384, CVE-2019-14379,
CVE-2019-14439, CVE-2019-14540, CVE-2019-16335, CVE-2019-16942,
CVE-2019-16943, CVE-2019-17267, CVE-2019-17531, CVE-2019-20330,
CVE-2020-10672, CVE-2020-10673, CVE-2020-10968, CVE-2020-10969,
CVE-2020-11111, CVE-2020-11112, CVE-2020-11113, CVE-2020-11619,
CVE-2020-11620, CVE-2020-14060, CVE-2020-14061, CVE-2020-14062,
CVE-2020-14195, CVE-2020-8840, CVE-2020-9546, CVE-2020-9547, CVE-2020-9548)

It was discovered that Jackson Databind incorrectly handled
deserialization. An attacker could possibly use this issue to execute XML
entity (XXE) attacks. (CVE-2018-14720)

It was discovered that Jackson Databind incorrectly handled
deserialization. An attacker could possibly use this issue to execute
server-side request forgery (SSRF). (CVE-2018-14721)

Fixed packages 1

ReleasePackageFixed in
Ubuntu · Pro 16.04 LTS Pro:16.04:LTS jackson-databind 2.4.2-3ubuntu0.1~esm2

Vulnerabilities 39

References

  • report
    https://ubuntu.com/security/CVE-2018-11307
  • report
    https://ubuntu.com/security/CVE-2018-12022
  • report
    https://ubuntu.com/security/CVE-2018-12023
  • report
    https://ubuntu.com/security/CVE-2018-14718
  • report
    https://ubuntu.com/security/CVE-2018-14719
  • report
    https://ubuntu.com/security/CVE-2018-14720
  • report
    https://ubuntu.com/security/CVE-2018-14721
  • report
    https://ubuntu.com/security/CVE-2018-19360
  • report
    https://ubuntu.com/security/CVE-2018-19361
  • report
    https://ubuntu.com/security/CVE-2018-19362
  • report
    https://ubuntu.com/security/CVE-2019-12086
  • report
    https://ubuntu.com/security/CVE-2019-12384
  • report
    https://ubuntu.com/security/CVE-2019-12814
  • report
    https://ubuntu.com/security/CVE-2019-14379
  • report
    https://ubuntu.com/security/CVE-2019-14439
  • report
    https://ubuntu.com/security/CVE-2019-14540
  • report
    https://ubuntu.com/security/CVE-2019-16335
  • report
    https://ubuntu.com/security/CVE-2019-16942
  • report
    https://ubuntu.com/security/CVE-2019-16943
  • report
    https://ubuntu.com/security/CVE-2019-17267
  • report
    https://ubuntu.com/security/CVE-2019-17531
  • report
    https://ubuntu.com/security/CVE-2019-20330
  • report
    https://ubuntu.com/security/CVE-2020-8840
  • report
    https://ubuntu.com/security/CVE-2020-9546
  • report
    https://ubuntu.com/security/CVE-2020-9547
  • report
    https://ubuntu.com/security/CVE-2020-9548
  • report
    https://ubuntu.com/security/CVE-2020-10672
  • report
    https://ubuntu.com/security/CVE-2020-10673
  • report
    https://ubuntu.com/security/CVE-2020-10968
  • report
    https://ubuntu.com/security/CVE-2020-10969
  • report
    https://ubuntu.com/security/CVE-2020-11111
  • report
    https://ubuntu.com/security/CVE-2020-11112
  • report
    https://ubuntu.com/security/CVE-2020-11113
  • report
    https://ubuntu.com/security/CVE-2020-11619
  • report
    https://ubuntu.com/security/CVE-2020-11620
  • report
    https://ubuntu.com/security/CVE-2020-14060
  • report
    https://ubuntu.com/security/CVE-2020-14061
  • report
    https://ubuntu.com/security/CVE-2020-14062
  • report
    https://ubuntu.com/security/CVE-2020-14195