dbcve.org
Realsense Software Development KitApplication · Intel

CVE-2023-32663

HIGH · 7.8 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to after 0.25.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 in some Intel(R) RealSense(TM) SDKs in version 2.53.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 confidence

Intel RealSense SDK version 2.53.1 ships with incorrect default permissions on certain files, directories, or services that allow an authenticated local user to modify protected resources and escalate privileges to higher permission levels.

MitigationApply the vendor patch for RealSense SDK 2.53.1 to remediate the permission misconfiguration, or manually restrict permissions on affected SDK components to follow least-privilege principles.

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
Realsense Software Development KitApplication
Affected:<= 0.25.0

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
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 checks

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

  1. Check if Intel RealSense SDK is installed
    Search for RealSense SDK installation directories or installed programs. Common locations include C:\Program Files\Intel\RealSense or C:\Program Files (x86)\Intel\RealSense on Windows, or /opt/intel/realsense, /usr/local/lib/realsense, or ~/IntelRealSense on Linux. Also check for the realsense-sdk or librealsense package via package manager (dpkg -l | grep -i realsense, rpm -qa | grep -i realsense).
    Affected if Intel RealSense SDK is present on the system
  2. Determine the installed version
    Check the SDK version from installed files. Look for version information in the SDK directory (version.txt, about, or similar), or query the installed package if installed via package manager. On Windows, check the file properties of the main SDK DLLs or check in Add/Remove Programs.
    Affected if Installed version is 0.25.0 or lower (any version <= 0.25.0)
  3. Inspect SDK directory permissions for world-writable or group-writable access
    Examine permissions on the main RealSense SDK installation directory and subdirectories. On Linux: use 'ls -la /path/to/realsense' and look for permissions with 'w' for others or group (o+w, g+w). On Windows: right-click the folder, go to Properties > Security, and check if Authenticated Users or Users group has Modify or Write permissions beyond Read/Execute.
    Affected if Authenticated local users have Modify, Write, or Full Control permissions on SDK directories or files
  4. Check for service or executable permissions that allow modification
    Identify any RealSense services or executables in the SDK folder. Check if these files are writable by non-privileged users. Look for .exe, .dll, or configuration files within the SDK directory and verify write permissions for standard user accounts.
    Affected if Non-privileged authenticated users can modify or replace SDK executables, DLLs, or configuration files

The environment is affected if Intel RealSense SDK version 0.25.0 or lower is installed and SDK directories or files are writable by authenticated local users (not just administrators).

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
Upgrade available Upgrade to a release after 0.25.0
Interim mitigation

Apply the vendor patch for RealSense SDK 2.53.1 to remediate the permission misconfiguration, or manually restrict permissions on affected SDK components to follow least-privilege principles.

Recommended fix Moderate confidence

Latest stable release of Intel RealSense SDK (check Intel website for version containing fix)

  1. 1. Check the currently installed Intel RealSense SDK version using package manager or project dependencies
  2. 2. Navigate to the official Intel RealSense download page or Intel Developer Zone for the latest SDK version
  3. 3. Download and install the latest stable release of the Intel RealSense SDK that addresses CVE-2023-32663
  4. 4. Verify the installation completed successfully
  5. 5. Rebuild any projects that depend on the RealSense SDK to link against the updated libraries
  6. 6. Test applications to ensure functionality is maintained after the upgrade
Caveat Minor API changes may exist between versions; review release notes before upgrading

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

Fix this in Realsense Software Development Kit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32663 — 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-2023-32663 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