GitHub Advisoryadvisory · crates.io

GHSA-jf9p-2fv9-2jp2 thread-amount Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS

HIGH Published 2025-11-21 Modified 2025-11-27 Official page ↗
Aliases
CVE-2025-65947
Ecosystem
crates.io
Packages
thread-amount
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400, CWE-772
Reviewed
2025-11-21

Affected packages

• crates.io thread-amount: < 0.2.2 → fixed in 0.2.2

Description

Affected versions of this crate contain resource leaks when querying thread counts on Windows and Apple platforms. Windows The `thread_amount` function calls `CreateToolhelp32Snapshot` but fails to close the returned `HANDLE` using `CloseHandle`. Repeated calls to this function will cause the handle count of the process to grow indefinitely, eventually leading to system instability or process termination when the handle limit is reached. macOS / iOS The `thread_amount` function calls `task_threads` (via Mach kernel APIs) which allocates memory for the thread list. The function fails to deallocate this memory using `vm_deallocate`. Repeated calls will result in a steady memory leak, eventually causing the process to be killed by the OOM (Out of Memory) killer. Impact Long-running applications (such as servers, daemons, or monitoring tools) that use this crate to periodically check thread counts will eventually crash due to resource exhaustion. Resources • https://github.com/jzeuzs/thread-amount/pull/29

Related

Alias · CVE (1)

  • CVE-2025-65947 thread-amount is a tool that gets the amount of threads in the current process. vulnerability

Weakness · CWE (2)

  • CWE-400 Uncontrolled Resource Consumption weakness
  • CWE-772 Missing Release of Resource after Effective Lifetime weakness

References