Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.2%
exploitation probability
0.2%top 93% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Affected products
puma · pumaReferences
https://github.com/puma/puma/commit/439c6136d9c2275721b7864db3ee78af7c80889fhttps://github.com/puma/puma/commit/ebe9db3929ab8299d19c8f5b41e8ef4f4b22fa58https://github.com/puma/puma/pull/3944https://github.com/puma/puma/pull/3947https://github.com/puma/puma/releases/tag/v7.2.1https://github.com/puma/puma/releases/tag/v8.0.2https://github.com/puma/puma/security/advisories/GHSA-2vqw-3mp8-cgmx