Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in puma 7.2.1 and puma 8.0.2.
Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection, allowing an attacker to inject a second PROXY header and overwrite REMOTE_ADDR. This issue is fixed in versions 7.2.1 and 8.0.2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| puma | >=5.5.0 <7.2.1, >=8.0.0 <8.0.2 | ||
| rubygems: puma | >=5.5.0 <7.2.1, >=8.0.0 <8.0.2 | 7.2.1, 8.0.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in puma (RubyGems), strongest first
Embed
A live severity badge for an advisory, README or ticket