||IBM WebSphere Application Server 8.0.x before 22.214.171.124 and 8.5.x before 126.96.36.199 allows remote attackers to spoof OpenID and OpenID Connect cookies, and consequently obtain sensitive information, via a crafted URL.
IBM WebSphere Application Server 188.8.131.52
IBM WebSphere Application Server 184.108.40.206
IBM WebSphere Application Server 220.127.116.11 (Fix Pack 2)
IBM WebSphere Application Server 18.104.22.168 (Fix Pack 3)
IBM WebSphere Application Server 22.214.171.124 (Fix Pack 4)
IBM WebSphere Application Server 126.96.36.199 (FixPack 5)
IBM WebSphere Application Server 188.8.131.52 (Fix Pack 6)
IBM WebSphere Application Server 184.108.40.206 (Fix Pack 7)
IBM WebSphere Application Server 220.127.116.11 (Fix Pack 8)
IBM WebSphere Application Server 18.104.22.168
IBM WebSphere Application Server 22.214.171.124
IBM WebSphere Application Server 126.96.36.199 (Fix Pack 1)
IBM WebSphere Application Server 188.8.131.52 (Fix Pack 2)
IBM WebSphere Application Server 184.108.40.206
IBM WebSphere Application Server 220.127.116.11
IBM WebSphere Application Server 18.104.22.168
IBM WebSphere Application Server 22.214.171.124 (Fix Pack 3)
|Base: ||5.0 (as of 18-12-2014 - 14:35)|
Subverting Environment Variable Values
The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
Exploiting Trust in Client (aka Make the Client Invisible)
An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client.
An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client.
There are numerous variations of this type of attack.
An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
Session Credential Falsification through Prediction
This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
Reusing Session IDs (aka Session Replay)
This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
Using Slashes in Alternate Encoding
This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
|NASL family||Web Servers |
|NASL id||WEBSPHERE_8_5_5_4.NASL |
|description||The IBM WebSphere Application Server running on the remote host is
version 8.5 prior to Fix Pack 126.96.36.199. It is, therefore, affected by
the following vulnerabilities :
- Multiple errors exist related to the included IBM HTTP
server that can allow remote code execution or denial
of service. (CVE-2013-5704, CVE-2014-0118,
CVE-2014-0226, CVE-2014-0231 / PI22070)
- An unspecified error exists related to HTTP headers
that can allow information disclosure. (CVE-2014-3021
- An error exists related to the way SSL 3.0 handles
padding bytes when decrypting messages encrypted using
block ciphers in cipher block chaining (CBC) mode. A
man-in-the-middle attacker can decrypt a selected byte
of a cipher text in as few as 256 tries if they are able
to force a victim application to repeatedly send the
same data over newly created SSL 3.0 connections. This
is also known as the 'POODLE' issue. (CVE-2014-3566 /
PI28435, PI28436, PI28437)
- An unspecified input validation errors exist related to
the administrative console that can allow cross-site
scripting and cross-site request forgery attacks.
(CVE-2014-4770, CVE-2014-4816 / PI23055)
- An unspecified error exists that can allow OpenID and
OpenID Connect cookies to be spoofed, allowing
information disclosure. (CVE-2014-6164 / PI23430)
- An error exists related to the Communications Enabled
Applications (CEA) service that can allow XML External
Entity Injection (XXE) attacks leading to information
disclosure. This only occurs if CEA is enabled. By
default this is disabled. (CVE-2014-6166 / PI25310)
- An input validation error exists related to session
input using URL rewriting that can allow cross-site
scripting attacks. (CVE-2014-6167 / PI23819)
- An error exists related to the administrative console
that can allow 'click-jacking' attacks. (CVE-2014-6174 /
- An error exists related to deployment descriptor
security constraints and ServletSecurity annotations on
a servlet that can allow privilege escalation. Note that
this issue only affects the 'Liberty Profile'.
(CVE-2014-8890 / PI29911) |
|last seen||2019-01-16 |
|plugin id||80398 |
|title||IBM WebSphere Application Server 8.5 < Fix Pack 188.8.131.52 Multiple Vulnerabilities (POODLE) |
|Last major update
||18-12-2014 - 14:40
||18-12-2014 - 11:59
||07-09-2017 - 21:29