CVE-2025-65947
BaseFortify
Publication date: 2025-11-21
Last updated on: 2025-11-21
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| thread_amount | thread_amount | 0.2.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-772 | The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. |
| CWE-400 | The product does not properly control the allocation and maintenance of a limited resource. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the thread-amount tool prior to version 0.2.2, where it improperly manages system resources when querying thread counts. On Windows, it calls CreateToolhelp32Snapshot but does not close the handle with CloseHandle, causing handle leaks. On Apple platforms, it calls task_threads which allocates memory but fails to deallocate it with vm_deallocate, causing memory leaks. Repeated calls lead to resource exhaustion, causing system instability or process termination.
How can this vulnerability impact me? :
The vulnerability can cause resource leaks that accumulate over time. On Windows, the handle count grows indefinitely, potentially leading to system instability or process termination when handle limits are reached. On Apple platforms, memory leaks can cause the process to be killed by the Out of Memory (OOM) killer. This can disrupt normal operation and cause crashes or instability in affected applications.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the handle count of the process using the thread_amount function on Windows or by observing memory usage growth on Apple platforms. On Windows, you can use commands like 'handle.exe -p <process_id>' from Sysinternals to check for increasing handle counts. On Apple platforms, monitoring the process memory usage over time with commands like 'top -pid <process_id>' or 'vmmap <process_id>' may help detect memory leaks caused by this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade the thread-amount tool to version 0.2.2 or later, where the resource leaks have been patched. Until the upgrade, limit the frequency of calls to the thread_amount function to reduce resource exhaustion and monitor system stability closely.