Skip to content

jackson-databind polymorphic typing issue

Critical severity GitHub Reviewed Published Nov 13, 2019 to the GitHub Advisory Database • Updated Sep 14, 2023

Package

maven com.fasterxml.jackson.core:jackson-databind (Maven)

Affected versions

>= 2.9.0, < 2.9.10.1
>= 2.7.0, < 2.8.11.5
< 2.6.7.3

Patched versions

2.9.10.1
2.8.11.5
2.6.7.3

Description

A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 prior to 2.9.10.1, 2.8.11.5, and 2.6.7.3. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the p6spy (3.8.6) jar in the classpath, and an attacker can find an RMI service endpoint to access, it is possible to make the service execute a malicious payload. This issue exists because of com.p6spy.engine.spy.P6DataSource mishandling.

References

Published by the National Vulnerability Database Oct 1, 2019
Reviewed Nov 13, 2019
Published to the GitHub Advisory Database Nov 13, 2019
Last updated Sep 14, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.404%
(74th percentile)

Weaknesses

CVE ID

CVE-2019-16943

GHSA ID

GHSA-fmmc-742q-jg75

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.