PasswordPusher versions v1.45.11 through v2.9.5 contain an improper authorization vulnerability in the push deletion logic. The ownership check compares @push.user against current_user; for an anonymously created push both values are nil, and Ruby evaluates nil == nil as true, so the check passes and the deletable_by_viewer restriction is never enforced. An attacker who knows only the secret URL can permanently delete an anonymous push even when the creator disabled viewer deletion and even without the passphrase.
Only deployments that allow anonymous pushes (the default) are affected. The issue is fixed in v2.9.6.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
Low
Partial data modification
Availability
Low
Partial disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
pglombardo:passwordpusher
References 3
https://github.com/pglombardo/PasswordPusher/security/advisories/GHSA-jf2m-hpj9…
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/passwordpusher-before-authentication-bypas…
disclosure@vulncheck.com
https://tpaidakis.com/writeups/passwordpusher-nil-authorization/
disclosure@vulncheck.com