# CVE-2020-8763: Privilege escalation in Intel(R) RealSense(TM) D400 Series Advisory

> An authenticated local attacker can escalate privileges due to improper installer permissions in the Intel RealSense D400 driver.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j29q-wcgf-g9qq

## What is CVE-2020-8763?

CVE-2020-8763 is a high-severity vulnerability in Intel(R) RealSense(TM) D400 Series Advisory, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper permissions in the installer for the Intel(R) RealSense(TM) D400 Series UWP driver for Windows* 10 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-8763?

It affects 3 products.


Products: Intel Realsense D415 Firmware, Intel Realsense D435 Firmware, Intel Realsense D435i Firmware.

## How do I fix CVE-2020-8763?

No fix has been published for CVE-2020-8763 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-8763 being exploited?

There is no known exploitation of CVE-2020-8763 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8763 and fix it if it is affected.

What it is: CVE-2020-8763 is a high-severity vulnerability in Intel(R) RealSense(TM) D400 Series Advisory, published on 13 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8763 in the wild and no public exploit code.

Affected product: Intel(R) RealSense(TM) D400 Series Advisory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-8763/ (Markdown: https://insights.sbomify.com/CVE-2020-8763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8763
- OSV: https://osv.dev/vulnerability/CVE-2020-8763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8763/
Summaries are generated and may contain mistakes; the official description above is the record.