CVE-2025-22838
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) RealSense(TM) Dynamic Calibrator software before version 2.14.2.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 RealSense Dynamic Calibrator software before version 2.14.2.0 contains an uncontrolled search path vulnerability where the application loads DLLs from locations that an authenticated local user can control. By placing a malicious DLL in a searched directory, an attacker can achieve privilege escalation.
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.
-
Check if Intel RealSense Dynamic Calibrator is installedOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKLM\SOFTWARE\Intel\RealSense\DynamicCalibrator, or check Program Files for folders containing 'RealSense' and 'DynamicCalibrator'Affected if The software is present on the system
-
Determine the installed version numberRight-click the Dynamic Calibrator executable, select Properties, then view the Details tab for Product Version, or check the Uninstall registry entry for DisplayVersionAffected if A version number is found that is below 2.14.2.0
-
Compare version to the affected rangeIf version is found, compare it numerically to 2.14.2.0. For example, 2.14.1.0 or 2.12.5.0 would be older versionsAffected if Installed version is lower than 2.14.2.0 (e.g., 2.14.1.0, 2.13.0.0, etc.)
-
Verify the application runs with elevated privilegesCheck if the Dynamic Calibrator is configured to run as a scheduled task with SYSTEM privileges, or runs with 'Run as administrator' enabled, by reviewing Task Scheduler or the application shortcut propertiesAffected if The application runs with elevated privileges and the version is below 2.14.2.0
User is affected if Intel RealSense Dynamic Calibrator is installed with a version lower than 2.14.2.0 and runs with elevated privileges, allowing a local authenticated attacker to perform DLL hijacking for 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 · scopedUpgrade Intel RealSense Dynamic Calibrator to version 2.14.2.0 or later to resolve the uncontrolled search path vulnerability.
2.14.2.0
- Check the currently installed version of Intel(R) RealSense(TM) Dynamic Calibrator software
- Download Intel RealSense Dynamic Calibrator version 2.14.2.0 or later from the official Intel website or support channel
- Install or upgrade to the downloaded version following Intel's standard installation procedures
- Verify that the installed version is 2.14.2.0 or later to confirm the update was applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22838 — 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-2025-22838 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