Skip to content

pocketmine/raklib reliable-ordered queue size is unlimited, allowing a session to hog server memory

Moderate severity GitHub Reviewed Published Nov 15, 2023 in pmmp/RakLib • Updated Nov 15, 2023

Package

composer pocketmine/raklib (Composer)

Affected versions

>= 0.14.0, < 0.14.6
>= 0.15.0, < 0.15.1

Patched versions

0.14.6
0.15.1

Description

Impact

A client can send reliable-ordered packets 0, 2, 3, 4, 5 ... etc, and all the packets 2 and up will stay in the reliable-ordered queue until 1 arrives. A malicious client can exploit this to waste all available server memory by simply never sending the missing packet. Since the server doesn't make any effort to limit the size of the queue or detect this kind of abuse, this problem is easy to abuse.

Patches

This bug was fixed on the 0.14.x and 0.15.x release lines by 371190f5854372154d1b263cd2a10e658e92bebe.

Workarounds

No workaround is known.

References

@dktapps dktapps published to pmmp/RakLib Nov 15, 2023
Published to the GitHub Advisory Database Nov 15, 2023
Reviewed Nov 15, 2023
Last updated Nov 15, 2023

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

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-w98g-5fmx-wm4x

Source code

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