CVE-2023-29504
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 element in some Intel(R) RealSense(TM) Dynamic Calibration software before version 2.13.1.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 confidenceThis is an uncontrolled search path element vulnerability (commonly known as DLL hijacking) in Intel RealSense Dynamic Calibration software. An authenticated local user can place a malicious DLL in a directory within the application's search path, causing the software to load and execute it with elevated privileges, achieving local privilege escalation.
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< 2.13.1.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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.
-
Find installed version of Intel RealSense Dynamic CalibrationOpen Programs and Features (Windows) or check the application's Help > About dialog for the version number. Look for 'Intel RealSense D400 Series Dynamic Calibration Tool' in the installed programs list.Affected if The version listed is lower than 2.13.1.0 (for example, 2.10.x, 2.11.x, or 2.12.x)
-
Locate the application installation directoryRight-click the application in Programs and Features and select 'Open file location' or 'Properties', then look at the 'Location' path.Affected if The application is installed and you can access its directory path.
-
Check application directory permissionsRight-click the application folder, select Properties > Security tab, and review the permissions. Check if any unprivileged users or groups have 'Write' or 'Modify' permissions to the folder.Affected if Unprivileged users can write files to the application directory where the executable runs.
-
Identify directories in application search pathUse a tool like Process Monitor or examine the application's executable and its dependencies to determine which directories are searched when loading DLLs. Check PATH environment variable and application working directory.Affected if Any directory in the search path (including the application directory itself) is writable by unprivileged users.
You are affected if the installed Intel RealSense Dynamic Calibration version is below 2.13.1.0 AND any directory in its search path is writable by unprivileged users, enabling DLL hijacking for local privilege escalation.
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 · scoped2.13.1.0
Update Intel RealSense Dynamic Calibration software to version 2.13.1.0 or later. As a compensating control, ensure the application directory and directories in its search path are not writable by unprivileged users.
2.13.1.0
- Check the currently installed version of Intel RealSense D400 Series Dynamic Calibration Tool
- Back up any existing calibration data or profiles before upgrading
- Uninstall the current version of the Intel RealSense Dynamic Calibration Tool
- Download the updated version 2.13.1.0 or later from Intel's official support website
- Install the new version following the installation wizard prompts
- Verify the installed version matches 2.13.1.0 or later
- Test the calibration functionality to ensure proper operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29504 — 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-2023-29504 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