Skip to content

http2: improper compressed header handling can lead to resource starvation

High
victorjulien published GHSA-9jxm-qw9v-266r May 7, 2024

Package

suricata

Affected versions

>=7.0.0,<=7.0.4
>=6.0.0,<=6.0.18

Patched versions

7.0.5
6.0.19

Description

Impact

Small amount of HTTP/2 traffic can lead to Suricata using a large amount of memory.

Patches

The issue has been addressed in Suricata 7.0.5 and 6.0.19.

Workarounds

Disable the HTTP/2 parser.

Reduce app-layer.protocols.http2.max-table-size value (default is 65536)

References

https://redmine.openinfosecfoundation.org/issues/6892
https://redmine.openinfosecfoundation.org/issues/6900

Credits

OSS-fuzz using quadfuzz

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

CVE ID

CVE-2024-32663

Weaknesses