CVE-2024-45614: Header normalization allows for client to clobber proxy set headers in Puma

Published Sep 19, 2024
·
Updated

Impact

Clients could clobber values set by intermediate proxies (such as X-Forwarded-For) by providing a underscore version of the same header (X-ForwardedFor). Any users trusting headers set by their proxy may be affected. Attackers may be able to downgrade connections to HTTP (non-SSL) or redirect responses, which could cause confidentiality leaks if combined with a separate MITM attack.

Patches v6.4.3/v5.6.9 now discards any headers using underscores if the non-underscore version also exists. Effectively, allowing the proxy defined headers to always win.

Workarounds Nginx has a underscoresinheaders configuration variable to discard these headers at the proxy level.

Any users that are implicitly trusting the proxy defined headers for security or availability should immediately cease doing so until upgraded to the fixed versions.

Other sources

Puma is a Ruby/Rack web server built for parallelism. In affected versions clients could clobber values set by intermediate proxies (such as X-Forwarded-For) by providing a underscore version of the same header (X-ForwardedFor). Any users relying on proxy set variables is affected. v6.4.3/v5.6.9 now discards any headers using underscores if the non-underscore version also exists. Effectively, allowing the proxy defined headers to always win. Users are advised to upgrade. Nginx has a underscoresinheaders configuration variable to discard these headers at the proxy level as a mitigation. Any users that are implicitly trusting the proxy defined headers for security should immediately cease doing so until upgraded to the fixed versions.

MITRE

Affected Software

5 affected componentsFixes available
rubygems/puma>=6.0.0<6.4.3
6.4.3
rubygems/puma<5.6.9
5.6.9
debian/puma<=4.3.8-1+deb11u2, <=5.6.5-3, <=6.4.2-6
Puma Puma Ruby<5.6.9
Puma Puma Ruby>=6.0.0<6.4.3

Event History

Sep 19, 2024
CVE Published
via MITRE·10:42 PM
Data Sourced
via MITRE·10:42 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Sep 20, 2024
Advisory Published
via GitHub·02:40 PM
Oct 2, 2024
Data Sourced
via Ubuntu·03:04 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-45614?

CVE-2024-45614 has been assessed as a medium-severity vulnerability affecting header values trusted by clients.

2

How do I fix CVE-2024-45614?

To fix CVE-2024-45614, upgrade to Puma version 6.4.3 or 5.6.9 or patch older versions as recommended.

3

What software is affected by CVE-2024-45614?

CVE-2024-45614 affects Puma versions between 6.0.0 and 6.4.3, as well as versions up to 5.6.9.

4

What type of attack does CVE-2024-45614 enable?

CVE-2024-45614 allows attackers to potentially downgrade network connections and manipulate header values.

5

Who is impacted by CVE-2024-45614?

Users who trust intermediary proxies that set HTTP headers may be affected by CVE-2024-45614.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203