# CVE-2023-4706: Privilege escalation in 1Lenovo Preload Directory

> Attackers can escalate privileges on Lenovo devices deployed via Microsoft AutoPilot due to incorrect default permissions in the preload directory.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fmxw-c4w5-cjwc

## What is CVE-2023-4706?

CVE-2023-4706 is a high-severity vulnerability in 1Lenovo Preload Directory, published on 8 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A privilege escalation vulnerability was reported in Lenovo preloaded devices deployed using Microsoft AutoPilot under a standard user account due to incorrect default privileges.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-4706?

It affects 1 product.


Products: Lenovo Preload Directory.

## How do I fix CVE-2023-4706?

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

## Is CVE-2023-4706 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4706 and fix it if it is affected.

What it is: CVE-2023-4706 is a high-severity vulnerability in 1Lenovo Preload Directory, published on 8 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-4706 in the wild and no public exploit code.

Affected product: 1Lenovo Preload Directory. 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-2023-4706/ (Markdown: https://insights.sbomify.com/CVE-2023-4706/index.md)
```

## Sources

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

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