RHSA-2020:3539: Important: Red Hat build of Thorntail 2.7.1 security and bug fix update
This release of Red Hat build of Thorntail 2.7.1 includes security updates, bug fixes, and enhancements. For more information, see the release notes listed in the References section.Security Fix(es): EAP: field-name is not parsed in accordance to RFC7230 (CVE-2020-1710) Wildfly: Improper authorization issue in WildFlySecurityManager when using alternative protection domain (CVE-2020-1748) keycloak: security headers missing on REST endpoints (CVE-2020-1728) wildfly-elytron: session fixation when using FORM authentication (CVE-2020-10714) hibernate-validator: Improper input validation in the interpolation of constraint error messages (CVE-2020-10693) wildfly: exposed setting of TCCL via the EmbeddedManagedProcess API (CVE-2020-10718) wildfly: unsafe deserialization in Wildfly Enterprise Java Beans (CVE-2020-10740) wildfly: EJB SessionOpenInvocations may not be removed properly after a response is received causing Denial of Service (CVE-2020-14307) keycloak: DoS by sending multiple simultaneous requests with a Content-Length header value greater than actual byte count of request body (CVE-2020-10758) wildfly: Some EJB transaction objects may get accumulated causing Denial of Service (CVE-2020-14297) For more details about the security issues and their impact, the CVSS score, acknowledgements, and other related information, see the CVE pages listed in the References section.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:3539?
The severity of RHSA-2020:3539 is categorized as moderate.
How do I fix RHSA-2020:3539?
To fix RHSA-2020:3539, upgrade your Red Hat build of Thorntail to version 2.7.1 or later.
What vulnerabilities are addressed in RHSA-2020:3539?
RHSA-2020:3539 addresses a vulnerability related to field-name parsing not conforming to RFC7230 (CVE-2020-1710).
Which versions are affected by RHSA-2020:3539?
RHSA-2020:3539 affects earlier versions of Red Hat build of Thorntail prior to 2.7.1.
Is there a workaround for RHSA-2020:3539?
There are no known workarounds for RHSA-2020:3539; the recommended action is to apply the security update.