Loading...
Skip to main content

CVE-2024-56733 — Vulnerability in pwpush — CVE Details

MEDIUM

Password Pusher Allows Session Token Interception Leading to Potential Hijacking

Published December 30, 2024Updated December 31, 2024Source: osv

Summary

### 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: 1. **Automatic Session Expiration**: Sessions are automatically expired after 2 hours of inactivity, reducing the window for potential exploitation. 2. **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. 3. **Encrypted Cookies**: Cookies are encrypted using the value of SECRET_KEY_BASE 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](https://www.ptsecurity.com/ww-en/) for reporting and working with me to bring this CVE to the community.

Advisory Timeline

  • First published December 30, 2024 (651 days ago).
  • Last revised December 31, 2024 — 1 day after initial publication.

Affected Packages (1)

Affects 1 ecosystem: rubygems (1).

PackageEcosystemAffectedFixed In
pwpush
rubygems
0.1.0Range-based data available

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 5.7 score means for each attack dimension.

Attack Vector
Local
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Frequently Asked Questions

What is CVE-2024-56733?
Password Pusher Allows Session Token Interception Leading to Potential Hijacking This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 5.7/10).
How do I check if my project is affected by CVE-2024-56733?
CVE-2024-56733 affects pwpush. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2024-56733 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
5.7

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-4fwj-m62q-pp47

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies