https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 23:36:02 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-01263 bdu:2025-01263 https://cve.radiocsirt.org/vuln/bdu:2025-01263 https://cve.radiocsirt.org/vuln/euvd-2026-202903 EUVD-2026-202903 https://cve.radiocsirt.org/vuln/euvd-2026-202903 https://cve.radiocsirt.org/vuln/fkie_cve-2024-52796 <p>Password Pusher, an open source application to communicate sensitive information over the web, 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. In v1.49.0, a fix was implemented to only authorize proxies on local IPs which resolves this issue. As a workaround, one may add rules to one&#39;s proxy and/or firewall to not accept external proxy headers such as `X-Forwarded-*` from clients.</p> <p>Password Pusher, an open source application to communicate sensitive information over the web, 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. In v1.49.0, a fix was implemented to only authorize proxies on local IPs which resolves this issue. As a workaround, one may add rules to one&#39;s proxy and/or firewall to not accept external proxy headers such as `X-Forwarded-*` from clients.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-52796 https://cve.radiocsirt.org/vuln/ghsa-ffp2-8p2h-4m5j <p><strong>Affected:</strong> RubyGems: pwpush</p> <p>### Impact</p> <p>Password Pusher comes with a configurable rate limiter. In versions prior to [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/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.</p> <p>Additionally, with the ability to bypass rate limiting, it also allows attackers to more easily execute brute force attacks.</p> <p>### Patches</p> <p>In [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), a fix was implemented to only authorize proxies on local IPs which resolves this issue.</p> <p>If you are running a remote proxy, please see [this documentation](https://docs.pwpush.com/docs/proxies/#trusted-proxies) on how to authorize the IP address of your remote proxy.</p> <p>### Workarounds</p> <p>It is highly suggested to upgrade to at least [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0) to mitigate this risk.</p> <p>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.</p> <p>### References</p> <p>The new settings are [configurable to authorize remote proxies](https://docs.pwpush.com/docs/proxies/#trusted-proxies).</p> <p>### Credits</p> <p>Thank you to [Positive Technologies](https://www.ptsecurity.com/ww-en/) for reporting and working with me to bring this CVE to the community with the associated fix.</p> <p><strong>Affected:</strong> RubyGems: pwpush</p> <p>### Impact</p> <p>Password Pusher comes with a configurable rate limiter. In versions prior to [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/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.</p> <p>Additionally, with the ability to bypass rate limiting, it also allows attackers to more easily execute brute force attacks.</p> <p>### Patches</p> <p>In [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0), a fix was implemented to only authorize proxies on local IPs which resolves this issue.</p> <p>If you are running a remote proxy, please see [this documentation](https://docs.pwpush.com/docs/proxies/#trusted-proxies) on how to authorize the IP address of your remote proxy.</p> <p>### Workarounds</p> <p>It is highly suggested to upgrade to at least [v1.49.0](https://github.com/pglombardo/PasswordPusher/releases/tag/v1.49.0) to mitigate this risk.</p> <p>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.</p> <p>### References</p> <p>The new settings are [configurable to authorize remote proxies](https://docs.pwpush.com/docs/proxies/#trusted-proxies).</p> <p>### Credits</p> <p>Thank you to [Positive Technologies](https://www.ptsecurity.com/ww-en/) for reporting and working with me to bring this CVE to the community with the associated fix.</p> https://cve.radiocsirt.org/vuln/ghsa-ffp2-8p2h-4m5j