ID CVE-2009-0891
Summary The Web Services Security component in IBM WebSphere Application Server 7.0 before Fix Pack 1 (7.0.0.1), 6.1 before Fix Pack 23 (6.1.0.23),and 6.0.2 before Fix Pack 33 (6.0.2.33) does not properly enforce (1) nonce and (2) timestamp expiration values in WS-Security bindings as stored in the com.ibm.wsspi.wssecurity.core custom property, which allows remote authenticated users to conduct session hijacking attacks.
References
Vulnerable Configurations
  • IBM WebSphere Application Server 7.0
    cpe:2.3:a:ibm:websphere_application_server:7.0
  • IBM WebSphere Application Server 6.1
    cpe:2.3:a:ibm:websphere_application_server:6.1
  • IBM WebSphere Application Server 6.1.0
    cpe:2.3:a:ibm:websphere_application_server:6.1.0
  • IBM WebSphere Application Server 6.1.0.0
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.0
  • IBM WebSphere Application Server 6.1.0.1 (Fix Pack 1)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.1
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.10
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.10
  • IBM WebSphere Application Server 6.1.0.11 (Fix Pack 11)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.11
  • IBM WebSphere Application Server 6.1.0.12
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.12
  • IBM WebSphere Application Server 6.1.0.13 (Fix Pack 13)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.13
  • IBM WebSphere Application Server 6.1.0.14 (Fix Pack 14)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.14
  • IBM WebSphere Application Server 6.1.0.15 (Fix Pack 15)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.15
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.16
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.16
  • IBM WebSphere Application Server 6.1.0.17 (Fix Pack 17)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.17
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.18
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.18
  • IBM WebSphere Application Server 6.1.0.19 (Fix Pack 19)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.19
  • IBM WebSphere Application Server 6.1.0.2 (Fix Pack 2)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.2
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.20
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.20
  • IBM WebSphere Application Server 6.1.0.21 (Fix Pack 21)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.21
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.22
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.22
  • IBM WebSphere Application Server 6.1.0.3 (Fix Pack 3)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.3
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.4
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.4
  • IBM WebSphere Application Server 6.1.0.5 (Fix Pack 5)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.5
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.6
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.6
  • IBM WebSphere Application Server 6.1.0.7 (Fix Pack 7)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.7
  • cpe:2.3:a:ibm:websphere_application_server:6.1.0.8
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.8
  • IBM WebSphere Application Server 6.1.0.9 (Fix Pack 9)
    cpe:2.3:a:ibm:websphere_application_server:6.1.0.9
  • IBM WebSphere Application Server 6.0.2
    cpe:2.3:a:ibm:websphere_application_server:6.0.2
  • IBM WebSphere Application Server 6.0.2.1
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.1
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.10
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.10
  • IBM WebSphere Application Server 6.0.2.11
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.11
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.12
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.12
  • IBM WebSphere Application Server 6.0.2.13
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.13
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.14
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.14
  • IBM WebSphere Application Server 6.0.2.15
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.15
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.16
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.16
  • IBM WebSphere Application Server 6.0.2.17
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.17
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.18
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.18
  • IBM WebSphere Application Server 6.0.2.19
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.19
  • IBM WebSphere Application Server 6.0.2.2
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.2
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.20
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.20
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.21
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.21
  • IBM WebSphere Application Server 6.0.2.22
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.22
  • IBM WebSphere Application Server 6.0.2.23
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.23
  • IBM WebSphere Application Server 6.0.2.24
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.24
  • IBM WebSphere Application Server 6.0.2.25
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.25
  • IBM WebSphere Application Server 6.0.2.27
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.27
  • IBM WebSphere Application Server 6.0.2.28
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.28
  • IBM WebSphere Application Server 6.0.2.29
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.29
  • IBM WebSphere Application Server 6.0.2.3
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.3
  • IBM WebSphere Application Server 6.0.2.30
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.30
  • IBM WebSphere Application Server 6.0.2.31
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.31
  • IBM WebSphere Application Server 6.0.2.32
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.32
  • IBM WebSphere Application Server 6.0.2.4
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.4
  • IBM WebSphere Application Server 6.0.2.5
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.5
  • IBM WebSphere Application Server 6.0.2.6
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.6
  • IBM WebSphere Application Server 6.0.2.7
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.7
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2.8
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.8
  • IBM WebSphere Application Server 6.0.2.9
    cpe:2.3:a:ibm:websphere_application_server:6.0.2.9
  • cpe:2.3:a:ibm:websphere_application_server:6.0.2:-:fp17
    cpe:2.3:a:ibm:websphere_application_server:6.0.2:-:fp17
CVSS
Base: 5.5 (as of 25-03-2009 - 10:06)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    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.
Access
VectorComplexityAuthentication
NETWORK LOW SINGLE_INSTANCE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL NONE
nessus via4
  • NASL family Web Servers
    NASL id WEBSPHERE_6_0_2_33.NASL
    description IBM WebSphere Application Server 6.0.2 before Fix Pack 33 appears to be running on the remote host. As such, it is reportedly affected by multiple vulnerabilities : - Provided an attacker has valid credentials, it may be possible to hijack an authenticated session. (PK66676) - The PerfServlet code writes sensitive information in the 'systemout.log' and ffdc files, provided Performance Monitoring Infrastructure (PMI) is enabled. (PK63886) - It may be possible to login to the administrative console using a user account that is locked by the operating system. (PK67909) - An unknown vulnerability affects z/OS-based IBM WebSphere application servers. (PK71143) - An unspecified vulnerability in the administrative console could allow arbitrary file retrieval from the remote system. (PK72036) - If APAR PK41002 has been applied, a vulnerability in the JAX-RPC WS-Security component could incorrectly validate 'UsernameToken'. (PK75992) - Certain files associated with interim fixes for Unix- based versions of IBM WebSphere Application Server are built with insecure file permissions. (PK78960)
    last seen 2019-01-16
    modified 2018-08-06
    plugin id 36132
    published 2009-04-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=36132
    title IBM WebSphere Application Server < 6.0.2.33 Multiple Vulnerabilities
  • NASL family Web Servers
    NASL id WEBSPHERE_6_1_0_23.NASL
    description IBM WebSphere Application Server 6.1 before Fix Pack 23 appears to be installed on the remote host. Such versions are reportedly affected by multiple vulnerabilities : - Provided an attacker has valid credentials, it may be possible to hijack an authenticated session. (PK66676) - It may be possible for a remote attacker to redirect users to arbitrary sites using ibm_security_logout servlet. (PK71126) - Under certain conditions it may be possible to access administrative console user sessions. (PK74966) - If APAR PK41002 has been applied, a vulnerability in the JAX-RPC WS-Security component could incorrectly validate 'UsernameToken'. (PK75992) - Sample applications shipped with IBM WebSphere Application Server are affected by cross-site scripting vulnerabilities. (PK76720) - The administrative console is affected by a cross-site scripting vulnerability. (PK77505) - It may be possible for an attacker to read arbitrary application-specific war files. (PK81387)
    last seen 2019-01-16
    modified 2018-08-06
    plugin id 36161
    published 2009-04-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=36161
    title IBM WebSphere Application Server < 6.1.0.23 Multiple Flaws
refmap via4
aixapar PK66676
confirm
secunia 34131
xf websphere-ws-security-session-hijacking(49391)
Last major update 24-10-2014 - 01:36
Published 24-03-2009 - 21:30
Last modified 16-08-2017 - 21:30
Back to Top