pysec-2024-178
Vulnerability from pysec
Published
2024-11-20 21:15
Modified
2025-01-19 01:52
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Details

Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to version 2.13.0, the multipart form parser shipped with litestar expects the entire request body as a single byte string and there is no default limit for the total size of the request body. This allows an attacker to upload arbitrary large files wrapped in a multipart/form-data request and cause excessive memory consumption on the server. The multipart form parser in affected versions is vulnerable to this type of attack by design. The public method signature as well as its implementation both expect the entire request body to be available as a single byte string. It is not possible to accept large file uploads in a safe way using this parser. This may be a regression, as a variation of this issue was already reported in CVE-2023-25578. Limiting the part number is not sufficient to prevent out-of-memory errors on the server. A patch is available in version 2.13.0.

Impacted products
Name purl
litestar pkg:pypi/litestar
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "litestar",
            purl: "pkg:pypi/litestar",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "53c1473b5ff7502816a9a339ffc90731bb0c2138",
                  },
               ],
               repo: "https://github.com/litestar-org/litestar",
               type: "GIT",
            },
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.13.0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "1.0.0a0",
            "2.0.0",
            "2.0.0a3",
            "2.0.0a4",
            "2.0.0a5",
            "2.0.0a6",
            "2.0.0a7",
            "2.0.0b1",
            "2.0.0b2",
            "2.0.0b3",
            "2.0.0b4",
            "2.0.0rc1",
            "2.0.1",
            "2.1.0",
            "2.1.1",
            "2.10.0",
            "2.11.0",
            "2.12.0",
            "2.12.1",
            "2.2.0",
            "2.2.1",
            "2.3.0",
            "2.3.1",
            "2.3.2",
            "2.4.0",
            "2.4.1",
            "2.4.2",
            "2.4.3",
            "2.4.4",
            "2.4.5",
            "2.5.0",
            "2.5.1",
            "2.5.2",
            "2.5.3",
            "2.5.4",
            "2.5.5",
            "2.6.0",
            "2.6.1",
            "2.6.2",
            "2.6.3",
            "2.6.4",
            "2.7.0",
            "2.7.1",
            "2.7.2",
            "2.8.0",
            "2.8.1",
            "2.8.2",
            "2.8.3",
            "2.9.0",
            "2.9.1",
         ],
      },
   ],
   aliases: [
      "CVE-2024-52581",
   ],
   details: "Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to version 2.13.0, the multipart form parser shipped with litestar expects the entire request body as a single byte string and there is no default limit for the total size of the request body. This allows an attacker to upload arbitrary large files wrapped in a `multipart/form-data` request and cause excessive memory consumption on the server. The multipart form parser in affected versions is vulnerable to this type of attack by design. The public method signature as well as its implementation both expect the entire request body to be available as a single byte string. It is not possible to accept large file uploads in a safe way using this parser. This may be a regression, as a variation of this issue was already reported in CVE-2023-25578. Limiting the part number is not sufficient to prevent out-of-memory errors on the server. A patch is available in version 2.13.0.",
   id: "PYSEC-2024-178",
   modified: "2025-01-19T01:52:23.772726+00:00",
   published: "2024-11-20T21:15:08+00:00",
   references: [
      {
         type: "ADVISORY",
         url: "https://github.com/litestar-org/litestar/security/advisories/GHSA-gjcc-jvgw-wvwj",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/litestar-org/litestar/security/advisories/GHSA-p24m-863f-fm6q",
      },
      {
         type: "EVIDENCE",
         url: "https://github.com/litestar-org/litestar/security/advisories/GHSA-gjcc-jvgw-wvwj",
      },
      {
         type: "FIX",
         url: "https://github.com/litestar-org/litestar/commit/53c1473b5ff7502816a9a339ffc90731bb0c2138",
      },
      {
         type: "WEB",
         url: "https://github.com/litestar-org/litestar/blob/main/litestar/_multipart.py#L97",
      },
   ],
   related: [
      "GHSA-gjcc-jvgw-wvwj",
      "GHSA-p24m-863f-fm6q",
   ],
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


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.




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.