# CVE-2020-1695: Improper Input Validation in RESTEasy > Improper input validation in RESTEasy allows illegal header injection into HTTP responses, potentially causing unexpected behavior. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 May 2020 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2020-1695, GHSA-63cq-ppq8-cw6g, MGASA-2021-0039, OESA-2022-1483, RHSA-2021:1775, RLSA-2021:1775, UBUNTU-CVE-2020-1695 ## What is CVE-2020-1695? CVE-2020-1695 is a high-severity vulnerability in Fedoraproject Fedora, published on 19 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in all resteasy 3.x.x versions prior to 3.12.0.Final and all resteasy 4.x.x versions prior to 4.6.0.Final, where an improper input validation results in returning an illegal header that integrates into the server's response. This flaw may result in an injection, which leads to unexpected behavior when the HTTP response is constructed. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2020-1695? 4 open source packages ship an affected version, including org.jboss.resteasy:resteasy-client. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jboss.resteasy:resteasy-client` | Maven | From 3.0.0 | 3.12.0 | | `org.jboss.resteasy:resteasy-client` | Maven | From 3.0.0 | 3.12.0 | | `org.jboss.resteasy:resteasy-client` | Maven | From 4.0.0 | 4.6.0 | | `org.jboss.resteasy:resteasy-client` | Maven | From 4.0.0 | 4.6.0 | | `apache-commons-collections` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.2.2-10.module+el8.1.0+3366+6dfb954c | | `apache-commons-lang` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.6-21.module+el8.1.0+3366+6dfb954c | | `apache-commons-net` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.6-3.module+el8.3.0+6805+72837426 | | `bea-stax` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.0-16.module+el8.1.0+3366+6dfb954c | | `bea-stax-api` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.0-16.module+el8.1.0+3366+6dfb954c | | `glassfish-fastinfoset` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.2.13-9.module+el8.1.0+3366+6dfb954c | | `glassfish-jaxb` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | | `glassfish-jaxb-api` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.12-8.module+el8.1.0+3366+6dfb954c | | `glassfish-jaxb-core` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | | `glassfish-jaxb-runtime` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | | `glassfish-jaxb-txw2` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.11-11.module+el8.1.0+3366+6dfb954c | | `jackson-annotations` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 | | `jackson-core` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 | | `jackson-databind` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.10.0-1.module+el8.2.0+5059+3eb3af25 | | `jackson-jaxrs-json-provider` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.9-1.module+el8.1.0+3832+9784644d | | `jackson-jaxrs-providers` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.9-1.module+el8.1.0+3832+9784644d | | `jackson-module-jaxb-annotations` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.7.6-4.module+el8.1.0+3366+6dfb954c | | `jakarta-commons-httpclient` | Red Hat:enterprise_linux:8::appstream | All versions | 1:3.1-28.module+el8.1.0+3366+6dfb954c | | `javassist` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.18.1-8.module+el8.1.0+3366+6dfb954c | | `javassist-javadoc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.18.1-8.module+el8.1.0+3366+6dfb954c | | `jss` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.8.1-2.module+el8.4.0+10451+3e5b5448 | | `jss-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.8.1-2.module+el8.4.0+10451+3e5b5448 | | `jss-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.8.1-2.module+el8.4.0+10451+3e5b5448 | | `jss-javadoc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.8.1-2.module+el8.4.0+10451+3e5b5448 | | `ldapjdk` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.22.0-1.module+el8.3.0+6784+6e1e4c62 | | `ldapjdk-javadoc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:4.22.0-1.module+el8.3.0+6784+6e1e4c62 | | `pki-acme` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-base` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-base-java` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-ca` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-core` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-core-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-core-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-kra` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-server` | Red Hat:enterprise_linux:8::appstream | All versions | 0:10.10.5-2.module+el8.4.0+10466+9830f79e | | `pki-servlet-4.0-api` | Red Hat:enterprise_linux:8::appstream | All versions | 1:9.0.30-1.module+el8.3.0+6730+8f9c6254 | Products: Fedoraproject Fedora, Redhat Resteasy. ## How do I fix CVE-2020-1695? Upgrade org.jboss.resteasy:resteasy-client to a fixed version for your release line: 3.12.0 or 4.6.0. ## Is CVE-2020-1695 being exploited? There is no known exploitation of CVE-2020-1695 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-1695 and fix it if it is affected. What it is: CVE-2020-1695 is a high-severity vulnerability in Fedoraproject Fedora, published on 19 May 2020. 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-2020-1695 in the wild and no public exploit code. Affected packages and fixed versions: - org.jboss.resteasy:resteasy-client (Maven): affected from 3.0.0; fixed in 3.12.0 - org.jboss.resteasy:resteasy-client (Maven): affected from 3.0.0; fixed in 3.12.0 - org.jboss.resteasy:resteasy-client (Maven): affected from 4.0.0; fixed in 4.6.0 - org.jboss.resteasy:resteasy-client (Maven): affected from 4.0.0; fixed in 4.6.0 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-2020-1695/ (Markdown: https://insights.sbomify.com/CVE-2020-1695/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1695 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1695 - OSV: https://osv.dev/vulnerability/CVE-2020-1695 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-1695/ Summaries are generated and may contain mistakes; the official description above is the record.