GHSA-4fwj-m62q-pp47
Suggest an improvement- Source
- https://github.com/advisories/GHSA-4fwj-m62q-pp47
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/12/GHSA-4fwj-m62q-pp47/GHSA-4fwj-m62q-pp47.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-4fwj-m62q-pp47
- Aliases
-
- CVE-2024-56733
- Published
- 2024-12-30T16:46:43Z
- Modified
- 2024-12-31T19:05:02.358745Z
- Severity
-
- 5.7 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
- Summary
- Password Pusher Allows Session Token Interception Leading to Potential Hijacking
- Details
-
Impact
A vulnerability has been reported in Password Pusher where an attacker can copy the session cookie before a user logs out, potentially allowing session hijacking.
Although the session token is replaced and invalidated upon logout, if an attacker manages to capture the session cookie before this process, they can use the token to gain unauthorized access to the user's session until the token expires or is manually cleared.
This vulnerability hinges on the attacker's ability to access the session cookie during an active session, either through a man-in-the-middle attack, by exploiting another vulnerability like XSS, or via direct access to the victim's device.
Patches
Although there is no direct resolution to this vulnerability, it is recommended to always use the latest version of Password Pusher to best mitigate risk.
Workarounds
If self-hosting, ensure Password Pusher is hosted exclusively over SSL connections to encrypt traffic and prevent session cookies from being intercepted in transit. Additionally, implement best practices in local security to safeguard user systems, browsers, and data against unauthorized access.
To further mitigate session hijacking risks, Password Pusher implements the following security measures:
- Automatic Session Expiration: Sessions are automatically expired after 2 hours of inactivity, reducing the window for potential exploitation.
- Session Reset on Login and Logout: Sessions are fully reset both when a user logs in and logs out, ensuring that session tokens are not reusable post-logout. This practice invalidates old session tokens and issues new ones, minimizing the risk of session hijacking.
- Encrypted Cookies: Cookies are encrypted using the value of SECRETKEYBASE from the application's configuration. This encryption adds a layer of protection against tampering or reading the session cookie's contents if intercepted, although it doesn't prevent the cookie from being used if stolen.
Note: While these measures significantly enhance security, they are part of a broader security strategy.
References
- https://edgeguides.rubyonrails.org/security.html#session-hijacking
Credits
Thank you to Positive Technologies for reporting and working with me to bring this CVE to the community.
- Database specific
{ "nvd_published_at": "2024-12-30T17:15:09Z", "github_reviewed_at": "2024-12-30T16:46:43Z", "github_reviewed": true, "severity": "MODERATE", "cwe_ids": [ "CWE-384" ] }- References
Affected packages
RubyGems / pwpush
Package
- Name
- pwpush
- Purl
- pkg:gem/pwpush