Skip to content

Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Jan 30, 2023

Package

maven org.jboss.resteasy:resteasy-yaml-provider (Maven)

Affected versions

< 3.0.26.Final
>= 3.1.0, < 3.6.0.Final

Patched versions

3.0.26.Final
3.6.0.Final

Description

It was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was incomplete and Yaml unmarshalling in Resteasy is still possible via Yaml.load() in YamlProvider.

Mitigation:

If the YamlProvider is enabled it's recommended to add authentication, and authorization to the endpoint expecting Yaml content to prevent exploitation of this vulnerability.

References

Published by the National Vulnerability Database Jan 25, 2018
Published to the GitHub Advisory Database May 13, 2022
Reviewed Nov 1, 2022
Last updated Jan 30, 2023

Severity

High

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
High
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.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.151%
(52nd percentile)

Weaknesses

CVE ID

CVE-2018-1051

GHSA ID

GHSA-m2fv-3rqm-g7p5

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.