dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-20095

MEDIUM · 6.7 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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
Incorrect Default Permissions for some Intel(R) RealSense™ SDK software before version 2.56.2 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 confidence

The Intel RealSense SDK versions prior to 2.56.2 ship with overly permissive default file or directory permissions, allowing an authenticated local user to modify or replace executables or configuration files that are subsequently run with elevated privileges, leading to privilege escalation.

MitigationUpgrade Intel RealSense SDK to version 2.56.2 or later to obtain the corrected permission model.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Detect Intel RealSense SDK installation
    Search for the SDK in common installation directories: On Windows check C:\Program Files\Intel RealSense SDK or C:\Program Files (x86)\Intel RealSense SDK; On Linux check /usr/lib/realsense, /opt/intel/realsense, or ~/.local/lib/realsense. Also search for executables such as realsense-viewer.exe, rs-capture, rs-depth, or other rs-* binaries in PATH or standard program directories.
    Affected if Intel RealSense SDK is found installed on the system
  2. Identify installed SDK version
    Once the SDK installation directory is located, look for a version file, release notes, or examine the properties of any realsense-viewer.exe or librealsense DLL/so files. Alternatively, run any installed rs-* command with a version flag such as --version or -v if available.
    Affected if The installed version is determined to be earlier than 2.56.2 (for example, 2.55.1, 2.54.0, or any version shown as less than 2.56.2)
  3. Verify file permissions on SDK directories
    Examine the access control list on the SDK installation folder: On Windows use icacls "<SDK_install_path>" or right-click the folder > Properties > Security to verify which users have Write or Modify permissions. On Linux use ls -la on the directory to check owner, group, and world permissions.
    Affected if Non-privileged users or the Users group have Write or Modify permissions to the SDK installation directory or its executable files
  4. Check for privileged execution of SDK components
    Look for Windows services, scheduled tasks, or startup items that execute RealSense SDK binaries: Run services.msc and search for Intel RealSense entries, or run schtasks /query /fo LIST to list scheduled tasks. On Linux check /etc/init.d/, systemd services in /lib/systemd/system/, or cron entries for realsense-related binaries.
    Affected if Any Intel RealSense SDK component is configured to run with elevated privileges (such as SYSTEM, Administrator, or root)

The environment is affected if Intel RealSense SDK version 2.56.2 or earlier is installed AND the SDK directories or files are writable by non-privileged users, especially when any SDK component runs with elevated privileges.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Intel RealSense SDK to version 2.56.2 or later to obtain the corrected permission model.

Recommended fix Moderate confidence

Intel RealSense SDK version 2.56.2

  1. 1. Identify the installed Intel RealSense SDK version on the system
  2. 2. If the installed version is earlier than 2.56.2, download Intel RealSense SDK version 2.56.2 or later from the official Intel website
  3. 3. Back up any existing projects or configurations that depend on the current SDK version
  4. 4. Uninstall the current version of Intel RealSense SDK
  5. 5. Install the new version 2.56.2 or later
  6. 6. Verify the installation completed successfully and confirm the new version number
  7. 7. Test that dependent applications function correctly with the updated SDK
Caveat Review release notes for any API changes between your current version and 2.56.2 that may affect compatibility with existing code

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

Have this fixed 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 help mitigating

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-2025-20095 — 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-2025-20095 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