dbcve.org
High Level Synthesis CompilerApplication · Intel

CVE-2024-23907

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 23.4 / 2024.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 in some Intel(R) High Level Synthesis Compiler software before version 23.4 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 · moderate confidence

This is an uncontrolled search path vulnerability in Intel's High Level Synthesis Compiler prior to version 23.4. The compiler searches for files or resources using a path that can be influenced by an authenticated local user, potentially allowing privilege escalation by placing malicious files in the search path that the privileged compiler process will execute.

MitigationUpgrade to Intel HLS Compiler version 23.4 or later. As a temporary measure, ensure the compiler is run from trusted directories and that the PATH and related environment variables are strictly controlled and not writable by unprivileged users.

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
High Level Synthesis CompilerApplication
Affected:< 23.4
Oneapi Dpc\+\+\/c\+\+ CompilerApplication
Affected:< 2024.1
Quartus PrimeApplication
Affected:< 23.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Identify installed Intel compiler products
    Check for installed Intel HLS Compiler, Intel OneAPI DPC++/C++ Compiler, or Intel Quartus Prime by inspecting common installation directories such as /opt/intel or C:\Program Files\Intel, or using system package managers
    Affected if Any of these Intel products are installed and their version is below the fixed releases (HLS Compiler < 23.4, OneAPI Compiler < 2024.1, Quartus Prime < 23.4)
  2. Determine installed version of Intel HLS Compiler
    Run 'quartus_sh --version' or check the compiler version via the Intel Quartus installation, or inspect the version information in the installation directory
    Affected if The installed version is lower than 23.4
  3. Determine installed version of Intel OneAPI DPC++/C++ Compiler
    Run 'icpx --version' or 'dpcpp --version' to check the compiler version
    Affected if The installed version is lower than 2024.1
  4. Determine installed version of Intel Quartus Prime
    Run 'quartus_sh --version' or check the version from the Quartus Prime installation
    Affected if The installed version is lower than 23.4
  5. Check if PATH environment is writable by unprivileged users
    Inspect file permissions on PATH directories and environment variables to determine if unprivileged users can modify search paths used by the compiler
    Affected if PATH or related environment variables used by the compiler are writable by unprivileged users, allowing them to place malicious files in the search path

A system is affected if any Intel HLS Compiler, OneAPI DPC++/C++ Compiler, or Quartus Prime is installed with a version below 23.4 (or 2024.1 for OneAPI) and the compiler's search path environment is writable by unprivileged users.

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 23.4 / 2024.1 or later
Fixed in 23.42024.1
Interim mitigation

Upgrade to Intel HLS Compiler version 23.4 or later. As a temporary measure, ensure the compiler is run from trusted directories and that the PATH and related environment variables are strictly controlled and not writable by unprivileged users.

Recommended fix High confidence

High Level Synthesis Compiler: 23.4 | OneAPI DPC++/C++ Compiler: 2024.1 | Quartus Prime: 23.4

  1. 1. Identify which Intel products from the affected list are installed: High Level Synthesis Compiler, OneAPI DPC++/C++ Compiler, or Quartus Prime
  2. 2. Check the current version of each installed product using 'quartus_sh --version' for Quartus Prime or the respective version check command for the compiler
  3. 3. For High Level Synthesis Compiler: download version 23.4 or later from the Intel website (intel.com)
  4. 4. For OneAPI DPC++/C++ Compiler: download version 2024.1 or later from the Intel website
  5. 5. For Quartus Prime: download version 23.4 or later from the Intel website
  6. 6. Run the installer for each product with administrator privileges
  7. 7. Follow the installation wizard prompts, selecting upgrade or repair options
  8. 8. After installation, verify the installed version matches the fixed release (23.4 or 2024.1)
Caveat Minor - this appears to be a point release upgrade within the same major version series; existing projects and settings should be preserved, but review release notes for any behavioral changes

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

Fix this in High Level Synthesis Compiler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2024-23907 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