Approved changes feed: RSS · Atom

cpe:2.3:a:socketry:protocol-http1:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorSocketry (c7b05686-c453-5227-9020-7f5e0185a2ae)
ProductProtocol Http1 (9b88438f-6cfb-51a8-90ff-065e8fe67e07)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:gem/protocol-http1 purl2cpe 2026-06-01 10:17:18.268527
pkg:github/socketry/protocol-http1 purl2cpe 2026-06-01 10:17:18.268529

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-38697 vulnerable 2026-06-08 06:08:18.652921 protocol-http1 HTTP Request/Response Smuggling vulnerability
MEDIUM (5.8)
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.
Published: 2023-08-04T17:32:51.164Z
Updated: 2024-10-04T19:39:00.470Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.