IBM Security Identity Governance Virtual Appliance 5.2 through 5.2.3.2 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 126861.
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Security_identity_governance_and_intelligence | Ibm | 5.2 (including) | 5.2 (including) |
| Security_identity_governance_and_intelligence | Ibm | 5.2.1 (including) | 5.2.1 (including) |
| Security_identity_governance_and_intelligence | Ibm | 5.2.2 (including) | 5.2.2 (including) |
| Security_identity_governance_and_intelligence | Ibm | 5.2.2.1 (including) | 5.2.2.1 (including) |
| Security_identity_governance_and_intelligence | Ibm | 5.2.3 (including) | 5.2.3 (including) |
| Security_identity_governance_and_intelligence | Ibm | 5.2.3.1 (including) | 5.2.3.1 (including) |
| Security_identity_governance_and_intelligence | Ibm | 5.2.3.2 (including) | 5.2.3.2 (including) |
Such a scenario is commonly observed when:
In the generic exploit of session fixation vulnerabilities, an attacker creates a new session on a web application and records the associated session identifier. The attacker then causes the victim to associate, and possibly authenticate, against the server using that session identifier, giving the attacker access to the user’s account through the active session.