Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
5.3

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.

CVE-2020-1710 · published 6 years ago
Summary

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.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
redhat jboss_data_grid 7.0.0
cpe:2.3:a:redhat:jboss_data_grid:-:*:*:*:text-only:*:*:*
redhat jboss_enterprise_application_platform 6.4.21
7.0.0
7.2.0
7.3.0
cpe:2.3:a:redhat:jboss_enterprise_application_platform:-:*:*:*:text-only:*:*:*
redhat openshift_application_runtimes All versions
cpe:2.3:a:redhat:openshift_application_runtimes:-:*:*:*:*:*:*:*
redhat single_sign-on All versions
cpe:2.3:a:redhat:single_sign-on:-:*:*:*:text-only:*:*:*
Original advisory text
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.
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.
References
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
5.3 Medium
Exploitation
1% chance of attack within 30 days
Timeline
Published16 Sep 2020
Updated4 Nov 2026
First seen29 Sep 2026
Sources
CVE-2020-1710 · NVD
Track software like this
Free during beta