Password Pusher Allows Session Token Interception Leading to Potential Hijacking

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-56733: 0.21% estimated exploitation activity in the next 30 days; percentile 11.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

30 Dec 2024, 16:46 UTC

Last modified by the source

31 Dec 2024, 18:42 UTC

Source last checked

26 Oct 2026, 15:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4fwj-m62q-pp47

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-56733

Advisory: Password Pusher Allows Session Token Interception Leading to Potential Hijacking
IDs: CVE-2024-56733, GHSA-4fwj-m62q-pp47
Record: https://patchnext.com/advisories/cve-2024-56733 (revision 1, source checked 26 Oct 2026, 15:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems pwpush: affected <= 1.50.3

## Suggested inspection (read-only)
- RubyGems pwpush: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pwpush.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4fwj-m62q-pp47 (GitHub-reviewed advisory GHSA-4fwj-m62q-pp47 lists affected ranges: RubyGems pwpush >=0 <=1.50.3)

Commands are suggestions: review each one before running it.