CVE-2024-21841
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 · uneditedUncontrolled search path for some Intel(R) Distribution for GDB software before version 2024.0 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 confidenceIntel Distribution for GDB before version 2024.0 contains an uncontrolled search path vulnerability that allows an authenticated local user to potentially escalate privileges. The application searches for files or libraries in an insecure manner, enabling an attacker to inject malicious code via the search path.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Intel Distribution for GDB installationSearch common installation directories such as /opt/intel/oneapi/, C:\Program Files\Intel\oneapi\, or check PATH environment variable for 'gdb' or 'intel-gdb' executables. Run 'where gdb' on Windows or 'which gdb' on Linux to find the binary.Affected if The software is found on the system, indicating Intel Distribution for GDB is installed.
-
Identify the installed versionRun the gdb binary with version flags such as 'gdb --version', 'intel-gdb --version', or check the installation directory for a version file. Common paths include <install_dir>/gdb/version.txt or check the oneapi installer metadata.Affected if The version cannot be determined or the binary is not found.
-
Compare version against the affected rangeExtract the full version string (for example, 2023.1, 2023.2, 2023.3, etc.) and compare numerically to version 2024.0. Any version lower than 2024.0 is considered affected.Affected if The installed version is lower than 2024.0 (for example, 2023.x, 2022.x, or any 202X version prior to the 2024.0 release).
If Intel Distribution for GDB is installed and the version is below 2024.0, the system is affected by this uncontrolled search path vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Intel Distribution for GDB version 2024.0 or later. Verify that the software uses secure, controlled paths for file and library resolution.
Intel Distribution for GDB 2024.0
- Download Intel Distribution for GDB version 2024.0 or later from the official Intel website
- Uninstall or remove any existing version of Intel Distribution for GDB prior to 2024.0
- Install the updated version 2024.0 or later
- Verify the installed version matches the patched release
- Restart any GDB instances to ensure the new version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21841 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21841 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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