Skip to content

Pleezer resource exhaustion through uncollected hook script processes

Moderate severity GitHub Reviewed Published Apr 13, 2025 in roderickvd/pleezer • Updated Apr 15, 2025

Package

cargo pleezer (Rust)

Affected versions

< 0.16.0

Patched versions

0.16.0

Description

Impact

Hook scripts in pleezer can be triggered by various events like track changes and playback state changes. In affected versions, these scripts were spawned without proper process cleanup, leaving zombie processes in the system's process table.

Even during normal usage, every track change and playback event would leave behind zombie processes. This leads to inevitable resource exhaustion over time as the system's process table fills up, eventually preventing new processes from being created. The issue is exacerbated if events occur rapidly, whether through normal use (e.g., skipping through a playlist) or potential manipulation of the Deezer Connect protocol traffic.

This vulnerability affects all users who have configured hook scripts using the --hook option.

Patches

This issue has been fixed in version 0.16.0. Users should upgrade to this version, which properly manages child processes using asynchronous process handling and cleanup.

Workarounds

Users who cannot upgrade immediately can:

  • Disable hook scripts by removing the --hook option
  • Ensure hook scripts handle their own child process cleanup
  • Regularly restart pleezer to clear accumulated zombie processes

References

References

@roderickvd roderickvd published to roderickvd/pleezer Apr 13, 2025
Published to the GitHub Advisory Database Apr 14, 2025
Reviewed Apr 14, 2025
Published by the National Vulnerability Database Apr 15, 2025
Last updated Apr 15, 2025

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
Low
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:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(29th percentile)

Weaknesses

Improper Cleanup on Thrown Exception

The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow. Learn more on MITRE.

Missing Release of Resource after Effective Lifetime

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. Learn more on MITRE.

CVE ID

CVE-2025-32439

GHSA ID

GHSA-472w-7w45-g3w5

Source code

Credits

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