CVE-2025-13665
DLL Planting Vulnerability in Windows System Console Utility
Publication date: 2025-12-12
Last updated on: 2025-12-12
Assigner: Altera
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| system_console_utility | system_console_utility | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-427 | The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves checking if the System Console Utility for Windows is installed standalone outside the full Quartus Prime Standard Edition installation directory, as this configuration is vulnerable. You can verify the installation paths and presence of the utility. Additionally, look for suspicious DLL files in directories where the utility is installed that could be used for DLL planting. Specific commands are not provided in the resources. [1]
Can you explain this vulnerability to me?
This vulnerability is a DLL planting issue in the System Console Utility for Windows. DLL planting occurs when an attacker places a malicious DLL file in a location where the application loads DLLs, causing the application to load the malicious DLL instead of the legitimate one.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized code execution with limited privileges, potentially allowing an attacker to execute malicious code within the context of the System Console Utility, which may compromise system integrity and security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, install Quartus Prime Standard Edition version 24.1 or newer, or ensure that the full Quartus Prime Standard Edition is installed rather than the standalone System Console Utility. This prevents the DLL planting vulnerability by correcting the search path handling. [1]