CVE-2016-9606
published 2018-01-25CVE-2016-9606: 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()`…
PriorityP351high8.1CVSS 3.0
AVNACHPRNUINSUCHIHAH
EPSS
6.06%
92.6th percentile
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.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | resteasy | < resteasy 3.1.4-1 (sid) | resteasy 3.1.4-1 (sid) |
| debian | resteasy | — | — |
| debian | resteasy3.0 | < resteasy 3.1.4-1 (sid) | resteasy 3.1.4-1 (sid) |
| debian | resteasy3.0 | — | — |
| red_hat_inc | resteasy | — | — |
| red_hat_inc | resteasy | — | — |
| redhat | resteasy | <= 3.1.1 | — |
| redhat | resteasy | — | — |
| redhat | resteasy | — | — |
CVSS provenance
nvdv3.08.1HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
ghsa8.1HIGH
osv8.1HIGH
vendor_debian8.1HIGH
vendor_redhat8.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
JBoss RESTEasy vulnerable to Improper Input Validation
osv·2022-05-14
CVE-2016-9606 [HIGH] JBoss RESTEasy vulnerable to Improper Input Validation
JBoss RESTEasy vulnerable to Improper Input Validation
JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.
GHSA
JBoss RESTEasy vulnerable to Improper Input Validation
ghsa·2022-05-14
CVE-2016-9606 [HIGH] CWE-20 JBoss RESTEasy vulnerable to Improper Input Validation
JBoss RESTEasy vulnerable to Improper Input Validation
JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.
OSV
Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider
osv·2022-05-13·CVSS 8.1
CVE-2018-1051 [HIGH] Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider
Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider
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.
GHSA
Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider
ghsa·2022-05-13·CVSS 8.1
CVE-2018-1051 [HIGH] CWE-502 Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider
Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider
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.
OSV
CVE-2016-9606: JBoss RESTEasy before version 3
osv·2018-03-09·CVSS 8.1
CVE-2016-9606 [HIGH] CVE-2016-9606: JBoss RESTEasy before version 3
JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.
OSV
CVE-2018-1051: It was found that the fix for CVE-2016-9606 in versions 3
osv·2018-01-25·CVSS 8.1
CVE-2018-1051 [HIGH] CVE-2018-1051: It was found that the fix for CVE-2016-9606 in versions 3
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.
Red Hat
resteasy: Unsafe unmarshalling in YamlProvider allows code execution
vendor_redhat·2018-01-18·CVSS 8.1
CVE-2018-1051 [HIGH] CWE-20 resteasy: Unsafe unmarshalling in YamlProvider allows code execution
resteasy: Unsafe unmarshalling in YamlProvider allows code execution
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.
Statement: This issue only affects applications which have the YamlProvider explicitly enabled by adding or appending a file with the name 'META-INF/services/javax.ws.rs.ext.Providers' to your WAR, or JAR with the contents 'org.jboss.resteasy.plugins.providers.YamlProvider'
resteasy-base as shipped in Red Hat Enterprise Linux 7 does not include YamlProvider.
Red Hat Subscription Asset Manager version 1 is now in a reduced support phase receiving only Critical impact security fixes. This issue has been rated as having Moderate security impact and i
Debian
CVE-2018-1051: resteasy - It was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was inc...
vendor_debian·2018·CVSS 8.1
CVE-2018-1051 [HIGH] CVE-2018-1051: resteasy - It was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was inc...
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.
Scope: local
sid: resolved
Red Hat
Resteasy: Yaml unmarshalling vulnerable to RCE
vendor_redhat·2016-12-15·CVSS 8.1
CVE-2016-9606 [HIGH] CWE-20 Resteasy: Yaml unmarshalling vulnerable to RCE
Resteasy: Yaml unmarshalling vulnerable to RCE
JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.
It was discovered that under certain conditions RESTEasy could be forced to parse a request with YamlProvider, resulting in unmarshalling of potentially untrusted data. An attacker could possibly use this flaw execute arbitrary code with the permissions of the application using RESTEasy.
Statement: YamlProvider was removed the default list of providers to prevent a malicous user from requesting a payload be marshalled with Yaml. If marshalling of Yaml content is desired, add, or append a file with t
Debian
CVE-2016-9606: resteasy - JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with ...
vendor_debian·2016·CVSS 8.1
CVE-2016-9606 [HIGH] CVE-2016-9606: resteasy - JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with ...
JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions.
Scope: local
sid: resolved (fixed in 3.1.4-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-1051 resteasy: Unsafe unmarshalling in YamlProvider allows code execution
bugzilla·2018-01-17·CVSS 8.1
CVE-2018-1051 [HIGH] CVE-2018-1051 resteasy: Unsafe unmarshalling in YamlProvider allows code execution
CVE-2018-1051 resteasy: Unsafe unmarshalling in YamlProvider allows code execution
It was found that fix for CVE-2016-9606 was incomplete and Yaml unmarshalling in Resteasy is still possible via `Yaml.load()` in YamlProvider.
Discussion:
resteasy-yaml-provider is marked as unsupported here. Marking EAP 7 as not affected
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/paged/7.0.0_release_notes/release_notes_unsupported_and_deprecated_functionality
---
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.
---
This won't be fixed in JBoss EAP 6.4, or 7.1 as the YamlProvider in RESTEasy is unsupported.
---
Bugzilla
CVE-2016-9606 Resteasy: Yaml unmarshalling vulnerable to RCE [fedora-all]
bugzilla·2016-12-15·CVSS 8.1
CVE-2016-9606 [HIGH] CVE-2016-9606 Resteasy: Yaml unmarshalling vulnerable to RCE [fedora-all]
CVE-2016-9606 Resteasy: Yaml unmarshalling vulnerable to RCE [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedo
Bugzilla
CVE-2016-9606 Resteasy: Yaml unmarshalling vulnerable to RCE
bugzilla·2016-12-01·CVSS 8.1
CVE-2016-9606 [HIGH] CVE-2016-9606 Resteasy: Yaml unmarshalling vulnerable to RCE
CVE-2016-9606 Resteasy: Yaml unmarshalling vulnerable to RCE
It was found that SnakeYAML unmarshalling is exploitable for code execution. As RESTeasy enables the yaml provider by default, therefore this is exploitable for JAX-RS applications specifiying either a yaml content type @Consumes or one without type specifiction.
Discussion:
Acknowledgments:
Name: Moritz Bechler (AgNO3 GmbH & Co. KG)
---
For Resteasy, it's a requirement that the @Consumes() annotation doesn't define a mime type, or defines a multipart mime type. Explicitly defining 'text/x-yaml', would also make that endpoint vulnerable. If the @Consumes annotation explicitly defines a 'application/json', or 'application/xml' it is not vulnerable.
---
Resteasy versions from 3.0-beta-1 up to and including 3.1.0.CR3 are pot
2018-01-25
Published