jvndb-2024-000122
Vulnerability from jvndb
Published
2024-11-27 14:36
Modified
2024-11-27 14:36
Severity ?
Summary
HAProxy vulnerable to HTTP request/response smuggling
Details
HAProxy HTTP/3 implementation contains an issue on accepting malformed HTTP headers. When a request including malformed HTTP headers is forwarded to a HTTP/1.1 non-compliant back-end server, it is exploited to conduct an HTTP request/response smuggling attack (CWE-444). Yuki Mogi of FFRI Security, Inc. reported this vulnerability to the developer and coordinated. After the coordination was completed, JPCERT/CC coordinated with the developer to publish this advisory in order to notify users of the solution through JVN.
Impacted products
HAProxy TechnologiesHAProxy
Show details on JVN DB website


{
   "@rdf:about": "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-000122.html",
   "dc:date": "2024-11-27T14:36+09:00",
   "dcterms:issued": "2024-11-27T14:36+09:00",
   "dcterms:modified": "2024-11-27T14:36+09:00",
   description: "HAProxy HTTP/3 implementation contains an issue on accepting malformed HTTP headers. When a request including malformed HTTP headers is forwarded to a HTTP/1.1 non-compliant back-end server, it is exploited to conduct an HTTP request/response smuggling attack (CWE-444).\r\n\r\nYuki Mogi of FFRI Security, Inc. reported this vulnerability to the developer and coordinated. After the coordination was completed, JPCERT/CC coordinated with the developer to publish this advisory in order to notify users of the solution through JVN.",
   link: "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-000122.html",
   "sec:cpe": {
      "#text": "cpe:/a:haproxy:haproxy",
      "@product": "HAProxy",
      "@vendor": "HAProxy Technologies",
      "@version": "2.2",
   },
   "sec:cvss": {
      "@score": "5.3",
      "@severity": "Medium",
      "@type": "Base",
      "@vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "@version": "3.0",
   },
   "sec:identifier": "JVNDB-2024-000122",
   "sec:references": [
      {
         "#text": "https://jvn.jp/en/jp/JVN88385716/index.html",
         "@id": "JVN#88385716",
         "@source": "JVN",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2024-53008",
         "@id": "CVE-2024-53008",
         "@source": "CVE",
      },
      {
         "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
         "@id": "CWE-Other",
         "@title": "No Mapping(CWE-Other)",
      },
   ],
   title: "HAProxy vulnerable to HTTP request/response smuggling",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.