Skip to content

pgsql: memory exhaustion on record parsing

High
victorjulien published GHSA-8583-353f-mvwc Feb 26, 2024

Package

suricata

Affected versions

>= 7.0.0, <= 7.0.2

Patched versions

7.0.3

Description

Impact

Excessive memory use during pgsql parsing could lead to OOM-related crashes.

Patches

Upgrade to 7.0.3.

Workarounds

Disable pgsql app layer parser.

References

https://redmine.openinfosecfoundation.org/issues/6411

Credits

Found by 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-23835

Weaknesses