# CVE-2019-14599: Privilege escalation in Control Center-I

> An authenticated local attacker can escalate privileges due to an unquoted service path in Control Center-I.

- **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:** 16 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vqg7-j269-7v36

## What is CVE-2019-14599?

CVE-2019-14599 is a high-severity vulnerability in Control Center-I, published on 16 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unquoted service path in Control Center-I version 2.1.0.0 and earlier may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2019-14599?

It affects 1 product.


Products: Intel Control Center-I.

## How do I fix CVE-2019-14599?

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

## Is CVE-2019-14599 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14599 and fix it if it is affected.

What it is: CVE-2019-14599 is a high-severity vulnerability in Control Center-I, published on 16 Dec 2019. 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-2019-14599 in the wild and no public exploit code.

Affected product: Control Center-I. 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-2019-14599/ (Markdown: https://insights.sbomify.com/CVE-2019-14599/index.md)
```

## Sources

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

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