CVE-2025-65947: Thread amount Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-jf9p-2fv9-2jp2
CVSS 7.5
CWE-400 CWE-772
Published
Advisory Summary

CVE-2025-65947 is a HIGH (CVSS 7.5) remote code execution vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Thread amount libraries in the crates.io ecosystem. The issue involves thread-amount vulnerable to resource exhaustion (memory and handle leaks) on windows and macos. Remediation is available by upgrading affected packages to version 0.2.2.

CVE-2025-65947 at a Glance

CVE Identifier CVE-2025-65947
GHSA Identifier GHSA-jf9p-2fv9-2jp2
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Thread amount
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2025-65947

To remediate this vulnerability, upgrade all affected Thread amount dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

thread-amount fixed: 0.2.2
Upgrade thread-amount to 0.2.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for thread-amount

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-65947, inspect your project dependencies for Thread amount:

inspect dependencies for thread-amount

Analyze the terminal output to locate any version of Thread amount in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.2.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Thread amount, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2025-65947 Affected Thread amount Versions

1 component(s)
Fixed Versions:
0.2.2
Product / Package Ecosystem Affected Versions Fixed Version
thread-amount
crates.io
< 0.2.2
0.2.2

References

Frequently Asked Questions

What is CVE-2025-65947?
CVE-2025-65947 is a security vulnerability in Thread amount involving thread-amount Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS under CWE-400: Uncontrolled Resource Consumption.
Which Thread amount versions are affected?
Affected versions include releases prior to 0.2.2 across affected packages: thread-amount.
What version fixes CVE-2025-65947?
Upgrading to 0.2.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is thread-amount affected?
Yes, thread-amount is affected in releases prior to 0.2.2. Upgrade your dependency to 0.2.2 or later.
What is the CVSS score of CVE-2025-65947?
CVE-2025-65947 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2025-65947?
CVE-2025-65947 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check crates.io dependencies for CVE-2025-65947?
Run the dependency tree command: 'inspect dependencies for thread-amount'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jf9p-2fv9-2jp2",
  "modified" : "2025-11-27T07:53:32Z",
  "published" : "2025-11-21T18:19:40Z",
  "aliases" : [ "CVE-2025-65947" ],
  "summary" : "thread-amount Vulnerable to Resource Exhaustion (Memory and Handle Leaks) on Windows and macOS",
  "details" : "Affected versions of this crate contain resource leaks when querying thread counts on Windows and Apple platforms.\n\n### Windows\nThe `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.\n\n### macOS / iOS\nThe `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.\n\n### Impact\nLong-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.\n\n### Resources\n\n- https://github.com/jzeuzs/thread-amount/pull/29",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "thread-amount"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.2.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jzeuzs/thread-amount/security/advisories/GHSA-jf9p-2fv9-2jp2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-65947"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jzeuzs/thread-amount/pull/29"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jzeuzs/thread-amount/commit/28860d4a38286609cb884c13b5b7941edc2390e5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jzeuzs/thread-amount"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2025-0125.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400", "CWE-772" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-21T18:19:40Z",
    "nvd_published_at" : "2025-11-21T23:15:45Z"
  }
}