Advisory

GHSA-ffp2-8p2h-4m5j

Also known as: CVE-2024-52796

Summary

Password Pusher rate limiter can be bypassed by forging proxy headers

Details

Impact

Password Pusher comes with a configurable rate limiter. In versions prior to v1.49.0, the rate limiter could be bypassed by forging proxy headers allowing bad actors to send unlimited traffic to the site potentially causing a denial of service.

Additionally, with the ability to bypass rate limiting, it also allows attackers to more easily execute brute force attacks.

Patches

In v1.49.0, a fix was implemented to only authorize proxies on local IPs which resolves this issue.

If you are running a remote proxy, please see this documentation on how to authorize the IP address of your remote proxy.

Workarounds

It is highly suggested to upgrade to at least v1.49.0 to mitigate this risk.

If for some reason you cannot immediately upgrade, the alternative is that you can add rules to your proxy and/or firewall to not accept external proxy headers such as X-Forwarded-* from clients.

References

The new settings are configurable to authorize remote proxies.

Credits

Thank you to Positive Technologies for reporting and working with me to bring this CVE to the community with the associated fix.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-11-20 18:24 UTC
Modified
2024-11-26 19:08 UTC

Affected packages and fixes

pwpush

RubyGems · All systems

Affected

  • introduced 0, fixed 1.49.0 (ecosystem)

Fixed versions

1.49.0

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences