Executive Summary

This vulnerability occurs because default configurations of Apache Shiro send sensitive cookies, specifically JSESSIONID and rememberMe cookies, in HTTPS sessions without the 'Secure' attribute.

Without the 'Secure' attribute, these cookies can be transmitted over unencrypted HTTP connections, potentially exposing them to interception by attackers.

The issue affects Apache Shiro versions from 1.0 to 2.1.0 and 3.0.0-alpha-1. It is fixed in versions 2.1.1 and 3.0.0-alpha-2 or later.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to sensitive session cookies being exposed over insecure connections, increasing the risk of session hijacking.

An attacker who intercepts these cookies could impersonate a legitimate user, gaining unauthorized access to the user's session and potentially sensitive information.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, users are recommended to upgrade Apache Shiro to version 2.1.1, or 3.0.0-alpha-2 or later, which fixes the issue.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability involves Apache Shiro sending sensitive cookies in HTTPS sessions without the 'Secure' attribute by default. This can lead to the exposure of session cookies over insecure channels, potentially allowing attackers to hijack user sessions.

Such exposure of sensitive session information can negatively impact compliance with common data protection standards and regulations like GDPR and HIPAA, which require appropriate safeguards to protect personal and sensitive data during transmission.

Therefore, the vulnerability may increase the risk of non-compliance with these regulations due to insufficient protection of session cookies.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability involves Apache Shiro sending sensitive cookies (JSESSIONID and rememberMe) over HTTPS without the 'Secure' attribute set by default in affected versions.

To detect this vulnerability on your network or system, you can inspect the cookies sent by your Apache Shiro application over HTTPS and check if the 'Secure' attribute is missing.

One way to do this is by using command-line tools like curl or browser developer tools to observe the Set-Cookie headers.

• Use curl to make an HTTPS request and view the Set-Cookie headers: curl -I https://your-shiro-app.example.com
• Look for Set-Cookie headers for JSESSIONID and rememberMe cookies and verify if the 'Secure' attribute is present.
• Alternatively, use browser developer tools (Network tab) to inspect cookies set by the application during HTTPS sessions.

Useful 0 Not Useful 0