# CVE-2023-4003: One Identity Password Manager version 5.9.7.1 - Unauthenticated physical access privilege escalation

> An attacker with physical access can escalate privileges to SYSTEM on workstations running One Identity Password Manager.

- **Severity:** High 7.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-j27c-p2q4-c74c

## What is CVE-2023-4003?

CVE-2023-4003 is a high-severity vulnerability in  One, published on 27 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

One Identity Password Manager version 5.9.7.1 - An unauthenticated attacker with physical access to a workstation may upgrade privileges to SYSTEM through an unspecified method. CWE-250: Execution with Unnecessary Privileges.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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

It affects 1 product.


Products: Oneidentity Password Manager.

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

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

## Is CVE-2023-4003 being exploited?

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

## Other vulnerabilities in  One

- [CVE-2023-48654](https://insights.sbomify.com/CVE-2023-48654/): Privilege escalation in n/a (critical 9.8)
- [CVE-2023-51772](https://insights.sbomify.com/CVE-2023-51772/): Security feature bypass in n/a (high 8.8)
- [CVE-2020-7962](https://insights.sbomify.com/CVE-2020-7962/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4003 is a high-severity vulnerability in  One, published on 27 Sep 2023. 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-2023-4003 in the wild and no public exploit code.

Affected product:  One. 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-4003/ (Markdown: https://insights.sbomify.com/CVE-2023-4003/index.md)
```

## Sources

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

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