CVE-2025-13654
BaseFortify
Publication date: 2025-12-05
Last updated on: 2025-12-17
Assigner: CERT/CC
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zevv | duc | to 1.4.6 (inc) |
| zevv | duc | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stack buffer overflow in the buffer_get function of duc, a disk management tool. It occurs because a condition can evaluate to true due to an underflow, which allows an out-of-bounds read.
How can this vulnerability impact me? :
The vulnerability can lead to a stack buffer overflow, which may cause unexpected behavior such as crashes or potentially allow an attacker to read memory out-of-bounds. This could compromise the stability or security of the system running duc.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for crashes or abnormal behavior in the Duc disk management tool when processing input data. A proof-of-concept exploit triggers a crash by requesting an out-of-bounds read, which can be detected using tools like AddressSanitizer. However, no specific detection commands are provided. It is recommended to check the Duc version installed on your system using commands like `duc --version` or `dpkg -l | grep duc` (on Debian-based systems) to verify if it is older than version 1.4.6, which is vulnerable. [3, 1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade Duc to version 1.4.6 or later, which contains the patch fixing the buffer overflow issue. This update corrects the bounds checking in the buffer_get function to prevent underflow and out-of-bounds reads. Users should obtain the patched version from the official GitHub repository and apply the update promptly to avoid crashes or potential information disclosure. [1, 3, 2]