pysec-2022-195
Vulnerability from pysec
Published
2022-04-04 18:15
Modified
2022-05-17 23:28
Details

Twisted is an event-based framework for internet applications, supporting Python 3.6+. Prior to version 22.4.0rc1, the Twisted Web HTTP 1.1 server, located in the twisted.web.http module, parsed several HTTP request constructs more leniently than permitted by RFC 7230. This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling. Users who may be affected use Twisted Web's HTTP 1.1 server and/or proxy and also pass requests through a different HTTP server and/or proxy. The Twisted Web client is not affected. The HTTP 2.0 server uses a different parser, so it is not affected. The issue has been addressed in Twisted 22.4.0rc1. Two workarounds are available: Ensure any vulnerabilities in upstream proxies have been addressed, such as by upgrading them; or filter malformed requests by other means, such as configuration of an upstream proxy.

Impacted products
Name purl
twisted pkg:pypi/twisted
Aliases


To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "twisted",
        "purl": "pkg:pypi/twisted"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "592217e951363d60e9cd99c5bbfd23d4615043ac"
            }
          ],
          "repo": "https://github.com/twisted/twisted",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "22.4.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.0.1",
        "1.0.3",
        "1.0.4",
        "1.0.5",
        "1.0.6",
        "1.0.7",
        "1.1.0",
        "1.1.1",
        "1.2.0",
        "10.0.0",
        "10.1.0",
        "10.2.0",
        "11.0.0",
        "11.1.0",
        "12.0.0",
        "12.1.0",
        "12.2.0",
        "12.3.0",
        "13.0.0",
        "13.1.0",
        "13.2.0",
        "14.0.0",
        "14.0.1",
        "14.0.2",
        "15.0.0",
        "15.1.0",
        "15.2.0",
        "15.2.1",
        "15.3.0",
        "15.4.0",
        "15.5.0",
        "16.0.0",
        "16.1.0",
        "16.1.1",
        "16.2.0",
        "16.3.0",
        "16.3.1",
        "16.3.2",
        "16.4.0",
        "16.4.1",
        "16.5.0",
        "16.5.0rc1",
        "16.5.0rc2",
        "16.6.0",
        "16.6.0rc1",
        "16.7.0rc1",
        "16.7.0rc2",
        "17.1.0",
        "17.1.0rc1",
        "17.5.0",
        "17.9.0",
        "17.9.0rc1",
        "18.4.0",
        "18.4.0rc1",
        "18.7.0",
        "18.7.0rc1",
        "18.7.0rc2",
        "18.9.0",
        "18.9.0rc1",
        "19.10.0",
        "19.10.0rc1",
        "19.2.0",
        "19.2.0rc1",
        "19.2.0rc2",
        "19.2.1",
        "19.7.0",
        "19.7.0rc1",
        "2.1.0",
        "2.4.0",
        "2.5.0",
        "20.3.0",
        "20.3.0rc1",
        "21.2.0",
        "21.2.0rc1",
        "21.7.0",
        "21.7.0rc1",
        "21.7.0rc2",
        "21.7.0rc3",
        "22.1.0",
        "22.1.0rc1",
        "22.2.0",
        "22.2.0rc1",
        "22.4.0rc1",
        "8.0.0",
        "8.0.1",
        "8.1.0",
        "8.2.0",
        "9.0.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-24801",
    "GHSA-c2jg-hw38-jrqq"
  ],
  "details": "Twisted is an event-based framework for internet applications, supporting Python 3.6+. Prior to version 22.4.0rc1, the Twisted Web HTTP 1.1 server, located in the `twisted.web.http` module, parsed several HTTP request constructs more leniently than permitted by RFC 7230. This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling. Users who may be affected use Twisted Web\u0027s HTTP 1.1 server and/or proxy and also pass requests through a different HTTP server and/or proxy. The Twisted Web client is not affected. The HTTP 2.0 server uses a different parser, so it is not affected. The issue has been addressed in Twisted 22.4.0rc1. Two workarounds are available: Ensure any vulnerabilities in upstream proxies have been addressed, such as by upgrading them; or filter malformed requests by other means, such as configuration of an upstream proxy.",
  "id": "PYSEC-2022-195",
  "modified": "2022-05-17T23:28:35.399117Z",
  "published": "2022-04-04T18:15:00Z",
  "references": [
    {
      "type": "FIX",
      "url": "https://github.com/twisted/twisted/commit/592217e951363d60e9cd99c5bbfd23d4615043ac"
    },
    {
      "type": "WEB",
      "url": "https://github.com/twisted/twisted/releases/tag/twisted-22.4.0rc1"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/twisted/twisted/security/advisories/GHSA-c2jg-hw38-jrqq"
    },
    {
      "type": "WEB",
      "url": "https://lists.debian.org/debian-lts-announce/2022/05/msg00003.html"
    }
  ]
}


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 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.