CVE-2024-23495
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 · uneditedIncorrect default permissions 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 · moderate confidenceThis is a local privilege escalation vulnerability in Intel Distribution for GDB caused by incorrect default file or directory permissions. An authenticated local user can exploit these overly permissive default settings to gain elevated privileges on the system. The vulnerability affects all versions prior to 2024.0.1.
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< 2024.0.1< 2024.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Intel Distribution for GDB is installedSearch for Intel Distribution for GDB installation directories. Common locations include /opt/intel (Linux) or C:\Program Files\Intel (Windows). Look for directories containing 'gdb' or 'intelpython' in the Intel installation path.Affected if The software is found on the system
-
Determine the installed versionLocate version information in the installation directory. Check for a version file, manifest, or use the gdb executable with --version or -v flags if accessible. Common paths include <install_dir>/gdb/version.txt or within the inteloneapi directory.Affected if The installed version is prior to 2024.0.1 (or Intel OneAPI Base Toolkit prior to 2024.1)
-
Inspect installation directory permissionsUse operating system tools to list permissions on the Intel GDB installation directory and its subdirectories. On Linux: 'ls -la <install_dir>'. On Windows: Right-click properties > Security or use 'icacls' command.Affected if Any directory or critical file within the installation shows world-writable (rwx permissions for 'others' on Linux) or overly permissive group/access settings that allow unauthorized local users to modify executables or libraries
-
Check for writable executable or library filesIdentify executable files (bin/gdb, bin/gdbserver, *.dll, *.so) and critical library files within the installation. Verify that these files are not writable by unprivileged users.Affected if Executable or library files are writable by non-admin users, allowing potential injection or replacement
-
Audit permission inheritanceVerify that newly created files within the installation directory do not inherit overly permissive default permissions. Check umask settings if applicable, and test creating a test file in the installation directory.Affected if Newly created files default to world-writable or group-writable permissions
A user is affected if Intel Distribution for GDB (or Intel OneAPI Base Toolkit) version prior to 2024.0.1/2024.1 is installed with overly permissive default file or directory permissions that allow unprivileged local users to modify executables or libraries.
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 · scoped2024.0.12024.1
Update Intel Distribution for GDB to version 2024.0.1 or later to obtain the corrected default permissions. For existing deployments, audit and remediate file system permissions on the installation directory to follow least-privilege principles.
Intel Distribution for GDB 2024.0.1+ and Intel OneAPI Base Toolkit 2024.1+
- Upgrade Intel Distribution for GDB to version 2024.0.1 or later
- Upgrade Intel OneAPI Base Toolkit to version 2024.1 or later
- Verify the installed versions after upgrade to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23495 — 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-23495 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