Skip to content

Vapor's incorrect request error handling triggers server crash

Moderate severity GitHub Reviewed Published Oct 5, 2023 in vapor/vapor • Updated Feb 9, 2024

Package

swift github.com/vapor/vapor (Swift)

Affected versions

>= 4.83.2, < 4.84.2

Patched versions

4.84.2

Description

Vapor incorrectly handles errors encountered during parsing of HTTP 1.x requests, triggering a precondition failure in swift-nio due to API misuse and causing immediate termination of the server process.

Impact

This is a denial of service vulnerability, impacting all users of affected versions of Vapor. Because the crash is an explicit assertion failure, there is no corruption of process state and no risk of data leakage or unauthorized code execution. Total impact is limited to an immediately recoverable service interruption.

Patches

The issue is fixed as of Vapor release 4.84.2.

Workarounds

None known at this time.

For more information

If you have any questions or comments about this advisory:

Acknowledgements

Full credit for reporting this issue goes to @t0rchwo0d, with additional thanks for responsibly disclosing.

References

@gwynne gwynne published to vapor/vapor Oct 5, 2023
Published by the National Vulnerability Database Oct 5, 2023
Published to the GitHub Advisory Database Oct 5, 2023
Reviewed Oct 5, 2023
Last updated Feb 9, 2024

Severity

Moderate

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
Low

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:L

EPSS score

0.091%
(40th percentile)

Weaknesses

CVE ID

CVE-2023-44386

GHSA ID

GHSA-3mwq-h3g6-ffhm

Source code

Credits

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