Intel Quartus Prime CVE-2025-13665

Exploitation requires: (1) local access to the Windows host running Intel/Altera Quartus Prime (Standard edition) with at least low-level privileges to write a file (PR:L); (2) ability to drop a malicious DLL into a directory within the System Console Utility's DLL search order (e.g., the working directory or an otherwise writable path it probes before the system directories); and (3) a legitimate user actively launching the utility afterward (UI:A), with a specific attack precondition present (AT:P). Limiting factors that reduce realistic risk: no remote vector (AV:L), high attack complexity (AC:H), dependence on user interaction, and the need for pre-existing local write access - it cannot be triggered against a default configuration remotely or without a victim running the tool.

This is a medium-severity local privilege/code-execution issue (vendor CVSS 4.0 base 5.4) whose real-world risk is LOW despite high technical impact. The CVSS vector is strongly limiting: AV:L (local only, not network-reachable), AC:H (high complexity), AT:P (a specific attack precondition must be present), PR:L (attacker needs some local privileges) and UI:A (a user must actively launch the vulnerable utility). EPSS reinforces this - 0.11% probability at the 1st percentile indicates near-zero expected mass exploitation. It is NOT in CISA KEV and no public exploit was provided, so there is no evidence of active exploitation. The VC:H/VI:H/VA:H impact (full code execution in the launching user's context, typical of CWE-427 DLL planting) is why the score is not lower, but the chain of local access + DLL placement + victim execution makes this an opportunistic/targeted issue rather than a widespread threat. Note a signal conflict: the input 'Information Disclosure' tag understates the impact, since the CVSS marks all of confidentiality, integrity and availability HIGH, consistent with arbitrary code execution rather than mere disclosure - verify intended impact against the Altera advisory.

A local attacker with low privileges places a malicious DLL in a directory that the Intel/Altera Quartus Prime System Console Utility searches when it starts. When a legitimate user subsequently launches the utility on that Windows host, the planted DLL is loaded and the attacker's code runs in that user's security context. No public proof-of-concept was identified in the provided data.