# CVE-2020-1710: Other in JBoss Enterprise Application Platform

> JBoss EAP fails to reject malformed HTTP headers per RFC7230, returning 200 instead of 400, potentially causing request smuggling or cache poisoning.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 16 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xqwp-g97m-cxpr

## What is CVE-2020-1710?

CVE-2020-1710 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The issue appears to be that JBoss EAP 6.4.21 does not parse the field-name in accordance to RFC7230[1] as it returns a 200 instead of a 400.

## Which versions are affected by CVE-2020-1710?

It affects 4 products.


Products: Redhat Jboss Data Grid, Redhat Jboss Enterprise Application Platform, Redhat Openshift Application Runtimes, Redhat Single Sign-On.

## How do I fix CVE-2020-1710?

Apply the vendor's patch.

## Is CVE-2020-1710 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2020-1757](https://insights.sbomify.com/CVE-2020-1757/): Improper Input Validation in Undertow (high 8.1)
- [CVE-2019-14887](https://insights.sbomify.com/CVE-2019-14887/): Inadequate Encryption Strength and Algorithm Downgrade in Wildfly (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1710 and fix it if it is affected.

What it is: CVE-2020-1710 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 16 Sep 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-1710 in the wild and no public exploit code.

Affected product: Redhat Jboss Enterprise Application Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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