Vulnerability from bitnami_vulndb
Published
2024-03-06 10:53
Modified
2025-04-03 14:40
Summary
Details

HAProxy through 2.0.32, 2.1.x and 2.2.x through 2.2.30, 2.3.x and 2.4.x through 2.4.23, 2.5.x and 2.6.x before 2.6.15, 2.7.x before 2.7.10, and 2.8.x before 2.8.2 forwards empty Content-Length headers, violating RFC 9110 section 8.6. In uncommon cases, an HTTP/1 server behind HAProxy may interpret the payload as an extra request.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "haproxy",
        "purl": "pkg:bitnami/haproxy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.33"
            },
            {
              "introduced": "2.2.0"
            },
            {
              "fixed": "2.2.31"
            },
            {
              "introduced": "2.4.0"
            },
            {
              "fixed": "2.4.24"
            },
            {
              "introduced": "2.5.0"
            },
            {
              "fixed": "2.6.15"
            },
            {
              "introduced": "2.7.0"
            },
            {
              "fixed": "2.7.10"
            },
            {
              "introduced": "2.8.0"
            },
            {
              "fixed": "2.8.2"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-40225"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "HAProxy through 2.0.32, 2.1.x and 2.2.x through 2.2.30, 2.3.x and 2.4.x through 2.4.23, 2.5.x and 2.6.x before 2.6.15, 2.7.x before 2.7.10, and 2.8.x before 2.8.2 forwards empty Content-Length headers, violating RFC 9110 section 8.6. In uncommon cases, an HTTP/1 server behind HAProxy may interpret the payload as an extra request.",
  "id": "BIT-haproxy-2023-40225",
  "modified": "2025-04-03T14:40:37.652Z",
  "published": "2024-03-06T10:53:12.013Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://cwe.mitre.org/data/definitions/436.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/haproxy/haproxy/commit/6492f1f29d738457ea9f382aca54537f35f9d856"
    },
    {
      "type": "WEB",
      "url": "https://github.com/haproxy/haproxy/issues/2237"
    },
    {
      "type": "WEB",
      "url": "https://www.haproxy.org/download/2.6/src/CHANGELOG"
    },
    {
      "type": "WEB",
      "url": "https://www.haproxy.org/download/2.7/src/CHANGELOG"
    },
    {
      "type": "WEB",
      "url": "https://www.haproxy.org/download/2.8/src/CHANGELOG"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-40225"
    }
  ],
  "schema_version": "1.5.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.