CVE-2020-1710Published Sep 16, 2020 · Sep 16Updated Jun 17
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…
JBoss Enterprise Application Platform
Medium5.3
JBoss Enterprise Application Platform
JBoss EAP 6.4.21 does not parse HTTP field names in accordance with RFC 7230 and returns a 200 response where a 400 response is expected. The input does not specify an attacker outcome beyond this response behavior, or whether authentication or user interaction is required.
Engineers running JBoss Enterprise Application Platform 6.4.21 should check their deployments.