Skip to content

GHSA-6f62-3596-g6w7 CVE-2024-47220

HTTP Request Smuggling in ruby webrick

High RubyGems
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Fix
1.8.2
Upgrade webrick to this version or later

Description

An issue was discovered in the WEBrick toolkit through 1.8.1 for Ruby. It allows HTTP request smuggling by providing both a Content-Length header and a Transfer-Encoding header, e.g., "GET /admin HTTP/1.1\r\n" inside of a "POST /user HTTP/1.1\r\n" request. NOTE: the supplier's position is "Webrick should not be used in production."

Affected versions

RubyGems

PackageVulnerableFixed in
webrick
< 1.8.2
1.8.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

webrick RubyGems → 1.8.2

bundler
bundle update webrick # Gemfile: gem "webrick", ">= 1.8.2"

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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

Weakness

CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

How to prevent it
  • Implementation: Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
  • Implementation: Use only SSL communication.
  • Implementation: Terminate the client session after each request.
  • System Configuration: Turn all pages to non-cacheable.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-r995-q44h-hr64
Ruby WEBrick read_headers method can lead to HTTP Request/Response Smuggling
Medium Also affects webrick
GHSA-gwfg-cqmg-cf8f
WEBRick vulnerable to HTTP Request/Response Smuggling
High Also affects webrick
GHSA-369m-2gv6-mw28
WEBrick RCE Vulnerability
High Also affects webrick
GHSA-wfrc-r6c6-7j9r
WEBrick Denial of Service Vulnerability
High Also affects webrick
GHSA-6mq2-37j5-w6r6
WEBrick Improper Input Validation vulnerability
Medium Also affects webrick
EEF-CVE-2026-114216
Chunk extensions accept bare LF and CR, enabling request smuggling in Bandit
Not rated yet Same weakness, CWE-444
RUSTSEC-2026-0388
Pingora HTTP/2 :authority and Host header mismatch enables cache poisoning and host-based access control bypass
Not rated yet Same weakness, CWE-444
GHSA-pqxq-w44r-73xw
AIOHTTP: Pure-Python parser request smuggling
Medium Same weakness, CWE-444
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor