CVE-2023-38697 protocol-http1 HTTP Request/Response Smuggling vulnerability
- Published
- Updated
- Exploit status
- Proof-of-concept only
Description
protocol-http1 provides a low-level implementation of the HTTP/1 protocol. RFC 9112 Section 7.1 defined the format of chunk size, chunk data and chunk extension. The value of Content-Length header should be a string of 0-9 digits, the chunk size should be a string of hex digits and should split from chunk data using CRLF, and the chunk extension shouldn't contain any invisible character. However, Falcon has following behaviors while disobey the corresponding RFCs: accepting Content-Length header values that have + prefix, accepting Content-Length header values that written in hexadecimal with 0x prefix, accepting 0x and + prefixed chunk size, and accepting LF in chunk extension. This behavior can lead to desync when forwarding through multiple HTTP parsers, potentially results in HTTP request smuggling and firewall bypassing. This issue is fixed in protocol-http1 v0.15.1. There are no known workarounds.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| rubygems protocol-http1(RubyGems) | < 0.15.1 | 0.15.1 |
| rubygems protocol-http1(RubyGems) | = 0.1.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.10.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.10.1 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.10.2 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.10.3 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.11.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.11.1 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.12.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.13.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.13.1 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.13.2 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.14.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.14.1 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.14.2 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.14.3 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.14.4 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.14.6 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.15.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.2.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.3.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.4.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.4.1 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.5.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.6.0 | No fix listed |
Show 29 more
| Product | Affected versions | Fixed in |
|---|---|---|
| rubygems protocol-http1(RubyGems) | = 0.7.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.8.0 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.8.1 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.8.2 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.8.3 | No fix listed |
| rubygems protocol-http1(RubyGems) | = 0.9.0 | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | All versions | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | = 0.14.6-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | = 0.35.2-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | = 0.37.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | = 0.39.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | = 0.40.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:12) | = 0.41.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | < 0.35.2-1 | 0.35.2-1 |
| debian/ruby-protocol-http1(Debian:14) | = 0.12.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.13.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.13.0-2 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.13.0-3 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.13.1-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.14.0-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.14.1-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.14.2-1 | No fix listed |
| debian/ruby-protocol-http1(Debian:14) | = 0.14.6-1 | No fix listed |
| socketry protocol-http1 | = < 0.15.1 | No fix listed |
| socketry protocol-http1 | < 0.15.1 | 0.15.1 |
| ubuntu/ruby-protocol-http1(Ubuntu:22.04) | All versions | No fix listed |
| ubuntu/ruby-protocol-http1(Ubuntu:24.04) | All versions | No fix listed |
| ubuntu/ruby-protocol-http1(Ubuntu:26.04) | All versions | No fix listed |
| ubuntu/ruby-protocol-http1(Ubuntu:26.10) | All versions | No fix listed |
References
- https://github.com/socketry/protocol-http1/security/advisories/GHSA-6jwc-qr2q-7xwj vendor-advisory
- https://github.com/socketry/protocol-http1/pull/20 issue-tracking patch
- https://github.com/socketry/protocol-http1/commit/e11fc164fd2b36f7b7e785e69fa8859eb06bcedd patch
- nvd.nist.gov third-party-advisory vendor-advisory
- https://www.rfc-editor.org/rfc/rfc9112#name-chunked-transfer-coding technical-description
- github.com exploit
- github.com
- github.com product
- Debian Security Tracker CVE-2023-38697 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- www.cve.org
- bugs.debian.org issue-tracking