Skip to content

Denial of service vulnerability when parsing multipart request body

High severity GitHub Reviewed Published Feb 15, 2023 in litestar-org/litestar • Updated Feb 24, 2023

Package

pip starlite (pip)

Affected versions

< 1.51.2

Patched versions

1.51.2

Description

Summary

The request body parsing in starlite allows a potentially unauthenticated
attacker to consume a large amount of CPU time and RAM.

Details

The multipart body parser processes an unlimited number of file parts.
The multipart body parser processes an unlimited number of field parts.

Impact

This is a remote, potentially unauthenticated Denial of Service vulnerability.

This vulnerability affects applications with a request handler that accepts
a Body(media_type=RequestEncodingType.MULTI_PART).

The large amount of CPU time required for processing requests can block all
available worker processes and significantly delay or slow down the processing
of legitimate user requests.
The large amount of RAM accumulated while processing requests can lead to
Out-Of-Memory kills.
Complete DoS is achievable by sending many concurrent multipart requests in a
loop.

References

@peterschutt peterschutt published to litestar-org/litestar Feb 15, 2023
Published by the National Vulnerability Database Feb 15, 2023
Published to the GitHub Advisory Database Feb 15, 2023
Reviewed Feb 15, 2023
Last updated Feb 24, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.127%
(48th percentile)

Weaknesses

CVE ID

CVE-2023-25578

GHSA ID

GHSA-p24m-863f-fm6q

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.