# CVE-2023-27386: Privilege escalation in Intel(R) Pathfinder for RISC-V software

> An authenticated local attacker can escalate privileges via an uncontrolled search path in Intel Pathfinder for RISC-V software.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/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:** 10 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-2pwr-m875-cvc9

## What is CVE-2023-27386?

CVE-2023-27386 is a medium-severity vulnerability in Intel(R) Pathfinder for RISC-V software, published on 10 May 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

Uncontrolled search path in some Intel(R) Pathfinder for RISC-V software may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-428 (Unquoted Search Path or Element), CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Intel Pathfinder for Risc-V.

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

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

## Is CVE-2023-27386 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27386 is a medium-severity vulnerability in Intel(R) Pathfinder for RISC-V software, published on 10 May 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-27386 in the wild and no public exploit code.

Affected product: Intel(R) Pathfinder for RISC-V software. 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-27386/ (Markdown: https://insights.sbomify.com/CVE-2023-27386/index.md)
```

## Sources

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

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