CVE-2018-1051

Publication date 25 January 2018

Last updated 24 July 2024

Ubuntu priority

Low

Why this priority?

Cvss 3 Severity Score

8.1 · High

Score breakdown

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.

Read the notes from the security team

Status

Package Ubuntu Release Status
resteasy 24.10 oracular
Not affected
24.04 LTS noble
Not affected
23.10 mantic
Not affected
23.04 lunar
Not affected
22.10 kinetic
Not affected
22.04 LTS jammy
Not affected
21.10 impish
Not affected
21.04 hirsute
Not affected
20.10 groovy
Not affected
20.04 LTS focal
Not affected
19.10 eoan
Not affected
19.04 disco Ignored end of life
18.10 cosmic Not in release
18.04 LTS bionic Not in release
17.10 artful Ignored end of life
16.04 LTS xenial
Vulnerable
14.04 LTS trusty Not in release
resteasy3.0 24.10 oracular
Not affected
24.04 LTS noble
Not affected
23.10 mantic
Not affected
23.04 lunar
Not affected
22.10 kinetic
Not affected
22.04 LTS jammy
Not affected
21.10 impish
Not affected
21.04 hirsute
Not affected
20.10 groovy
Not affected
20.04 LTS focal
Not affected
19.10 eoan
Not affected
19.04 disco Ignored end of life
18.10 cosmic Ignored end of life
18.04 LTS bionic
Not affected
17.10 artful Not in release
16.04 LTS xenial Not in release
14.04 LTS trusty Not in release

Notes

msalvatore

Incomplete fix for CVE-2016-9606 not applied. That fix just disables the YamlProvider by default. There is no fix for this issue other than to mitigate it by requiring authentication and authorization on endpoints expecting YAML input.

Severity score breakdown

Parameter Value
Base score 8.1 · High
Attack vector Network
Attack complexity High
Privileges required None
User interaction None
Scope Unchanged
Confidentiality High
Integrity impact High
Availability impact High
Vector CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H