Skip to content

Puma HTTP Request/Response Smuggling vulnerability

Critical severity GitHub Reviewed Published Aug 18, 2023 in puma/puma • Updated Nov 9, 2023

Package

bundler puma (RubyGems)

Affected versions

< 5.6.7
>= 6.0.0, < 6.3.1

Patched versions

5.6.7
6.3.1

Description

Impact

Prior to version 6.3.1, puma exhibited incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers in a way that allowed HTTP request smuggling.

The following vulnerabilities are addressed by this advisory:

  • Incorrect parsing of trailing fields in chunked transfer encoding bodies
  • Parsing of blank/zero-length Content-Length headers

Patches

The vulnerability has been fixed in 6.3.1 and 5.6.7.

Workarounds

No known workarounds.

References

HTTP Request Smuggling

For more information

If you have any questions or comments about this advisory:

Open an issue in Puma
See our security policy

References

@nateberkopec nateberkopec published to puma/puma Aug 18, 2023
Published to the GitHub Advisory Database Aug 18, 2023
Reviewed Aug 18, 2023
Published by the National Vulnerability Database Aug 18, 2023
Last updated Nov 9, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.363%
(73rd percentile)

Weaknesses

CVE ID

CVE-2023-40175

GHSA ID

GHSA-68xg-gqqm-vgj8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.