# CVE-2016-9606: JBoss RESTEasy vulnerable to Improper Input Validation

> Attackers can execute arbitrary code by sending malicious YAML data to JBoss RESTEasy applications using the YamlProvider.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** CVE-2016-9571, DEBIAN-CVE-2016-9606, GHSA-hgjr-xwj3-jfvw, OESA-2021-1073, RHSA-2017:1253, RHSA-2017:1254, RHSA-2017:1256, RHSA-2017:1260, UBUNTU-CVE-2016-9606

## What is CVE-2016-9606?

CVE-2016-9606 is a high-severity unsafe deserialization vulnerability in Red Hat, Inc. RESTEasy, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-9606?

2 open source packages ship an affected version, including org.jboss.resteasy:resteasy-bom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.resteasy:resteasy-bom` | Maven | All versions | 3.1.2.Final |
| `org.jboss.resteasy:resteasy-bom` | Maven | All versions | 3.1.2.Final |
| `hibernate4-core-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.26-1.Final_redhat_1.1.ep6.el5 |
| `hibernate4-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.26-1.Final_redhat_1.1.ep6.el5 |
| `hibernate4-entitymanager-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.26-1.Final_redhat_1.1.ep6.el5 |
| `hibernate4-envers-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.26-1.Final_redhat_1.1.ep6.el5 |
| `hibernate4-infinispan-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:4.2.26-1.Final_redhat_1.1.ep6.el5 |
| `hornetq` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:2.3.25-20.SP18_redhat_1.1.ep6.el5 |
| `httpserver` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.8-1.Final_redhat_1.1.ep6.el5 |
| `ironjacamar-common-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-common-impl-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-common-spi-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-core-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-core-impl-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-deployers-common-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-jdbc-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-spec-api-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `ironjacamar-validator-eap6` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:1.0.38-3.Final_redhat_3.1.ep6.el5 |
| `jboss-as-appclient` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-cli` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-client-all` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-clustering` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-cmp` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-configadmin` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-connector` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-controller-client` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-core-security` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-deployment-repository` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-deployment-scanner` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-domain-http` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-domain-management` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-ee` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-ee-deployment` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-ejb3` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-embedded` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-host-controller` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-jacorb` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |
| `jboss-as-jaxr` | Red Hat:jboss_enterprise_application_platform:6::el5 | All versions | 0:7.5.15-1.Final_redhat_3.1.ep6.el5 |

Products: Redhat Resteasy.

## How do I fix CVE-2016-9606?

Upgrade org.jboss.resteasy:resteasy-bom to 3.1.2.Final or later.

## Is CVE-2016-9606 being exploited?

There is no known exploitation of CVE-2016-9606 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat, Inc. RESTEasy

- [CVE-2018-1051](https://insights.sbomify.com/CVE-2018-1051/): Deserialization of Untrusted Data in org.jboss.resteasy:resteasy-yaml-provider (high 8.1)
- [CVE-2016-6346](https://insights.sbomify.com/CVE-2016-6346/): Denial of service in JBoss resteasy (high 7.5)
- [CVE-2016-6345](https://insights.sbomify.com/CVE-2016-6345/): Exposure of Sensitive Information to an Unauthorized Actor in RESTEasy (medium 6.5)
- [CVE-2014-7839](https://insights.sbomify.com/CVE-2014-7839/): XML External Entity Reference in RESTEasy (medium 6.4)
- [CVE-2016-6347](https://insights.sbomify.com/CVE-2016-6347/): Improper Neutralization of Input During Web Page Generation in RESTEasy (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9606 and fix it if it is affected.

What it is: CVE-2016-9606 is a high-severity unsafe deserialization vulnerability in Red Hat, Inc. RESTEasy, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-9606 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.resteasy:resteasy-bom (Maven): affected all versions; fixed in 3.1.2.Final
- org.jboss.resteasy:resteasy-bom (Maven): affected all versions; fixed in 3.1.2.Final

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-9606/ (Markdown: https://insights.sbomify.com/CVE-2016-9606/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-9606
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-9606
- OSV: https://osv.dev/vulnerability/CVE-2016-9606

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-9606/
Summaries are generated and may contain mistakes; the official description above is the record.
