dbcve.org
Distribution For GdbApplication · Intel

CVE-2024-23491

HIGH · 7.3 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 2024.0.1 / 2024.1 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 in some Intel(R) Distribution for GDB software before version 2024.0.1 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

Uncontrolled search path vulnerability in Intel Distribution for GDB before version 2024.0.1 allows an authenticated local user to hijack library or executable loading by placing malicious files in locations the application searches, potentially enabling privilege escalation.

MitigationUpdate Intel Distribution for GDB to version 2024.0.1 or later to obtain the patched binaries with corrected library search paths.

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
Distribution For GdbApplication
Affected:< 2024.0.1
Oneapi Base ToolkitApplication
Affected:< 2024.1

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. Identify Intel Distribution for GDB installation
    Search for 'gdb.exe' or 'gdb' binary in common Intel installation paths: C:\Program Files\Intel\, C:\Program Files (x86)\Intel\, /opt/intel/oneapi/, or check Start Menu for Intel OneAPI shortcuts. Use 'where gdb' on Windows or 'which gdb' on Linux to locate the binary.
    Affected if GDB binary is found in an Intel oneAPI installation directory and its version is below 2024.0.1
  2. Determine installed GDB version
    Run 'gdb --version' or right-click the gdb binary and view Properties > Details to see the version number. For Intel oneAPI, the version is typically embedded in the installation folder name under /oneapi/ or /oneAPI/.
    Affected if Version displayed is earlier than 2024.0.1 (for example, 2023.x, 2022.x, or any 2024.0.0.x)
  3. Check Intel OneAPI Base Toolkit version
    Open Intel OneAPI Base Toolkit via Start Menu, or check Add/Remove Programs (Windows) or installed packages (Linux). The toolkit includes Intel Distribution for GDB as a component.
    Affected if OneAPI Base Toolkit version is below 2024.1
  4. Inspect GDB library search path configuration
    Run GDB and execute 'show environment' and 'show solib-search-path' to view library paths. On Linux, also check 'ldd <gdb_binary>' output for library locations. Identify directories where GDB loads shared libraries from.
    Affected if Any directory in the search path is writable by unprivileged users, or the GDB installation directory itself allows non-admin write access

User is affected if Intel Distribution for GDB or Intel OneAPI Base Toolkit is installed with a version below 2024.0.1 or 2024.1 respectively, AND the GDB binary or its library search paths are in directories writable by local 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 2024.0.1 / 2024.1 or later
Fixed in 2024.0.12024.1
Interim mitigation

Update Intel Distribution for GDB to version 2024.0.1 or later to obtain the patched binaries with corrected library search paths.

Recommended fix High confidence

Intel Distribution for GDB >= 2024.0.1; Intel OneAPI Base Toolkit >= 2024.1

  1. Identify the installed Intel(R) Distribution for GDB version by running 'gdb --version' or checking the installation directory
  2. Identify the installed Intel(R) OneAPI Base Toolkit version through the Intel OneAPI installation manager or 'oneapi-cli'
  3. Download Intel(R) Distribution for GDB version 2024.0.1 or later from the official Intel download site
  4. Download Intel(R) OneAPI Base Toolkit version 2024.1 or later from the official Intel download site
  5. Uninstall the current versions through the Intel OneAPI installation manager or Windows Add/Remove Programs
  6. Install the updated versions (2024.0.1+ for GDB, 2024.1+ for OneAPI Base Toolkit)
  7. Verify the installation by checking the installed version matches or exceeds the fixed releases
  8. Restart any running GDB instances to ensure the updated binaries are loaded
Caveat Review Intel OneAPI 2024.1 release notes for any compatibility changes with existing projects or toolchains before upgrading production systems

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

Fix this in Distribution For Gdb 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-2024-23491 — 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-23491 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