||IBM WebSphere Application Server (WAS) Liberty Profile 8.5 before 188.8.131.52, when SSL is not enabled, does not properly validate authentication cookies, which allows remote authenticated users to bypass intended access restrictions via an HTTP session.
|Base: ||3.5 (as of 24-04-2013 - 08:08)|
An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
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.
Utilizing REST's Trust in the System Resource to Register Man in the Middle
This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated.
Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
Man in the Middle Attack
This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
|NASL family||Web Servers |
|NASL id||WEBSPHERE_8_5_0_2.NASL |
|description||IBM WebSphere Application Server 8.5 before Fix Pack 2 appears to be
running on the remote host and is, therefore, potentially affected by
the following vulnerabilities :
- The included Java SDK contains several errors that
affect the application directly. (CVE-2013-0169,
- Input validation errors exist related to the
administration console that could allow cross-site
scripting attacks. (CVE-2013-0458 / PM71139,
CVE-2013-0461 / PM71389, CVE-2013-0542 / PM81846,
CVE-2013-0565 / PM83402)
- An input validation error exists related to the
administration console that could allow cross-site
scripting attacks. Note that this issue affects only
the application when running on z/OS operating systems.
(CVE-2013-0459 / PM72536)
- An unspecified error could allow security bypass for
authenticated users. (CVE-2013-0462 / PM76886 or
- An error exists related to 'WS-Security' and SOAP
message handling that could allow an attacker to spoof
message signatures. (CVE-2013-0482 / PM76582)
- An error exists related to authentication cookies that
could allow remote attackers to gain access to
restricted resources. Note this only affects the
application when running the 'Liberty Profile'.
(CVE-2013-0540 / PM81056)
- A buffer overflow error exists related to 'WebSphere
Identity Manger (WIM)' that could allow denial of
service attacks. (CVE-2013-0541 / PM74909)
- An unspecified error could allow security bypass, thus
allowing remote attackers access to restricted resources
on HP, Linux and Solaris hosts.
(CVE-2013-0543 / PM75582)
- An unspecified error related to the administration
console could allow directory traversal attacks on
Unix and Linux hosts. (CVE-2013-0544 / PM82468) |
|last seen||2019-01-16 |
|plugin id||66375 |
|title||IBM WebSphere Application Server 8.5 < Fix Pack 2 Multiple Vulnerabilities |
|Last major update
||24-04-2013 - 00:00
||24-04-2013 - 06:28
||28-08-2017 - 21:33