# CVE-2016-6347: Improper Neutralization of Input During Web Page Generation in RESTEasy

> Remote attackers can inject arbitrary web script or HTML via the default exception handler in RESTEasy, potentially leading to code execution.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-6347, GHSA-r346-rmrg-qpgh, UBUNTU-CVE-2016-6347

## What is CVE-2016-6347?

CVE-2016-6347 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the default exception handler in RESTEasy allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.resteasy:resteasy-client` | Maven | All versions | 3.0.20.Final |
| `org.jboss.resteasy:resteasy-client` | Maven | All versions | 3.0.20.Final |
| `org.jboss.resteasy:resteasy-client` | Maven | From 3.1.0.Beta1 | 3.1.0.CR1 |
| `org.jboss.resteasy:resteasy-client` | Maven | From 3.1.0.Beta1 | 3.1.0.CR1 |

Products: Redhat Resteasy.

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

Upgrade org.jboss.resteasy:resteasy-client to a fixed version for your release line: 3.0.20.Final or 3.1.0.CR1.

## Is CVE-2016-6347 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-9606](https://insights.sbomify.com/CVE-2016-9606/): JBoss RESTEasy vulnerable to Improper Input Validation (high 8.1)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6347 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-6347 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.resteasy:resteasy-client (Maven): affected all versions; fixed in 3.0.20.Final
- org.jboss.resteasy:resteasy-client (Maven): affected all versions; fixed in 3.0.20.Final
- org.jboss.resteasy:resteasy-client (Maven): affected from 3.1.0.Beta1; fixed in 3.1.0.CR1
- org.jboss.resteasy:resteasy-client (Maven): affected from 3.1.0.Beta1; fixed in 3.1.0.CR1

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-6347/ (Markdown: https://insights.sbomify.com/CVE-2016-6347/index.md)
```

## Sources

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

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