September 30, 2019
Redhat Undertow is prone to an information-disclosure vulnerability. Successfully exploiting this issue may allow an attacker to obtain sensitive information that may aid in further attacks. Undertow versions 2.0.20 and prior are vulnerable.
- Redhat JBoss Data Grid 7
- Redhat JBoss Enterprise Application Platform (for RHEL 6) 7.2
- Redhat JBoss Enterprise Application Platform (for RHEL 7) 7.2
- Redhat JBoss Enterprise Application Platform (for RHEL 8) 7.2
- Redhat JBoss Fuse 7.0
- Redhat Jboss EAP 7.2
- Redhat Single Sign-On 7.0
- Redhat Undertow 1.0.16
- Redhat Undertow 1.3.25
- Redhat Undertow 1.4.0
- Redhat Undertow 1.4.26
- Redhat Undertow 1.4.27
- Redhat Undertow 2.0.10
- Redhat Undertow 2.0.12
- Redhat Undertow 2.0.16
- Redhat Undertow 2.0.17
- Redhat Undertow 2.0.18
- Redhat Undertow 2.0.19
- Redhat Undertow 2.0.20
- Redhat Undertow 2.0.5
Block external access at the network boundary, unless external parties require service.
Filter access to the affected computer at the network boundary if global access isn't needed. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.
Run all software as a nonprivileged user with minimal access rights.
Attackers may successfully exploit client flaws in the browser through cross-site scripting vulnerabilities. When possible, run all software as a user with minimal privileges and limited access to system resources. Use additional precautions such as restrictive environments to insulate software that may potentially handle malicious content.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.
Updates are available. Please see the references or vendor advisory for more information.
The vendor reported this issue.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.