Quartus PrimeApplication · Intel

CVE-2023-24016

HIGH · 7.3 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 22.1std / 22.4 or later.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Uncontrolled search path element in some Intel(R) Quartus(R) Prime Pro and Standard edition software for linux may allow an authenticated user to potentially enable escalation of privilege via local access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Intel Quartus Prime software for Linux contains an uncontrolled search path element vulnerability that allows an authenticated local user to potentially perform privilege escalation. This is a DLL/library hijacking issue where the application loads libraries from an insecure path, allowing a malicious library to be substituted for a legitimate one.

MitigationApply the vendor-supplied patch or update to Intel Quartus Prime Pro/Standard edition software. Review and harden file system permissions to prevent unauthorized users from writing to application directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Quartus PrimeApplication
Affected:< 22.1std< 22.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine if Intel Quartus Prime is installed
    Search for Quartus installation directories in common locations such as /opt/intel, /opt/altera, or the user's home directory. Look for directories containing 'quartus' in the name. Use commands like: find /opt -type d -name '*quartus*' 2>/dev/null; ls -la ~ | grep -i quartus
    Affected if Quartus Prime is not installed - not affected
  2. Identify the installed version
    Locate the quartus_sh or quartus binary within the installation directory. Run the binary with version flag such as --version, or check version information files in the installation directory. Common command: ./quartus_sh --version
    Affected if Version is 22.1std or 22.4 or later - not affected; versions below these thresholds are affected
  3. Check write permissions on the installation directory and subdirectories
    List permissions on the Quartus installation directory and its subdirectories (particularly lib, bin, or any directory that may contain shared libraries). Use: ls -la <quartus_install_dir> and ls -la <quartus_install_dir>/*/
    Affected if Non-privileged users have write access to any directory containing application libraries - the DLL hijacking condition is present

If Intel Quartus Prime is installed with a version below 22.1std or 22.4, and the application directories are writable by unprivileged users, the environment is vulnerable to CVE-2023-24016.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.1std / 22.4 or later
Fixed in 22.1std22.4
Interim mitigation

Apply the vendor-supplied patch or update to Intel Quartus Prime Pro/Standard edition software. Review and harden file system permissions to prevent unauthorized users from writing to application directories.

Recommended fix High confidence

Quartus Prime Pro >= 22.1std; Quartus Prime Standard >= 22.4

  1. Upgrade Intel(R) Quartus(R) Prime Pro Edition to version 22.1std or later
  2. Upgrade Intel(R) Quartus(R) Prime Standard Edition to version 22.4 or later
  3. After upgrading, verify the application runs correctly and test any critical design workflows
Caveat Major Quartus Prime version upgrades may require recompilation of existing designs and may have toolchain or IP compatibility considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Quartus Prime Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data