In Undertow before versions 7.1.2.CR1, 7.1.2.GA it was found that the fix for CVE-2016-4993 was incomplete and Undertow web server is vulne…
In Undertow before versions 7.1.2.CR1, 7.1.2.GA it was found that the fix for CVE-2016-4993 was incomplete and Undertow web server is vulnerable to the injection of arbitrary HTTP headers, and also response splitting, due to insufficient sanitization and validation of user input before the input is used as part of an HTTP header value.
The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
https://cwe.mitre.org/data/definitions/113.html →Open in CWE collection →This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
https://capec.mitre.org/data/definitions/31.html →Open in CAPEC collection →https://capec.mitre.org/data/definitions/34.html →Open in CAPEC collection →
This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.
https://capec.mitre.org/data/definitions/85.html →Open in CAPEC collection →https://capec.mitre.org/data/definitions/105.html →Open in CAPEC collection →
| Product | Vendor | Status |
|---|---|---|
| eap7-activemq-artemis | Tracked | |
| eap7-activemq-artemis | Tracked | |
| eap7-hibernate | Tracked | |
| eap7-hibernate | Tracked | |
| eap7-infinispan | Tracked | |
| eap7-infinispan | Tracked | |
| eap7-ironjacamar | Tracked | |
| eap7-ironjacamar | Tracked | |
| eap7-jboss-ec2-eap | Tracked | |
| eap7-jboss-ec2-eap | Tracked | |
| eap7-jboss-ejb-client | Tracked | |
| eap7-jboss-ejb-client | Tracked | |
| eap7-jboss-jsf-api_2.2_spec | Tracked | |
| eap7-jboss-jsf-api_2.2_spec | Tracked | |
| eap7-jboss-marshalling | Tracked | |
| eap7-jboss-marshalling | Tracked | |
| eap7-jboss-server-migration | Tracked | |
| eap7-jboss-server-migration | Tracked | |
| eap7-jboss-weld-2.2-api | Tracked | |
| eap7-jboss-weld-2.2-api | Tracked |