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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2023-38697)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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.
    (CVE-2023-38697)

An update of the rubygem package has been released.

The version of rubygem-protocol-http1 installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2023-38697 advisory.

  - 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.
    (CVE-2023-38697)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
251221	Linux Distros Unpatched Vulnerability : CVE-2023-38697	Nessus	Misc.	medium
411509	SCA: security update for protocol-http1 (GHSA-6jwc-qr2q-7xwj)	Tenable Cloud Security	SCA Checks	medium
411509	SCA: security update for protocol-http1 (GHSA-6jwc-qr2q-7xwj)	Tenable Self-Hosted Container Security	SCA Checks	medium
211629	Photon OS 5.0: Rubygem PHSA-2024-5.0-0405	Nessus	PhotonOS Local Security Checks	medium
211628	Photon OS 4.0: Rubygem PHSA-2024-4.0-0713	Nessus	PhotonOS Local Security Checks	medium
180357	CBL Mariner 2.0 Security Update: rubygem-protocol-http1 (CVE-2023-38697)	Nessus	MarinerOS Local Security Checks	medium

Detections

Analytics

CVE-2023-38697

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium