# CVE-2019-0127: Information disclosure in n/a

> A logic error in the Intel OpenVINO installer allows privileged local users to disclose sensitive information.

- **Severity:** Low 3.9 (`CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-94x5-5h76-gq8m

## What is CVE-2019-0127?

CVE-2019-0127 is a low-severity vulnerability in n/a, published on 18 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Logic error in the installer for Intel(R) OpenVINO(TM) 2018 R3 and before for Linux may allow a privileged user to potentially enable information disclosure via local access.

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

It affects 1 product.


Products: Intel Openvino.

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

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

## Is CVE-2019-0127 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-28405](https://insights.sbomify.com/CVE-2023-28405/): Path traversal in Intel(R) Distribution of OpenVINO(TM) Toolkit (medium 6.7)
- [CVE-2023-25080](https://insights.sbomify.com/CVE-2023-25080/): Information disclosure in Intel(R) Distribution of OpenVINO toolkit software (medium 5.3)
- [CVE-2021-26251](https://insights.sbomify.com/CVE-2021-26251/): Denial of service in Intel(R) Distribution of OpenVINO(TM) Toolkit (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0127 is a low-severity vulnerability in n/a, published on 18 Feb 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-0127 in the wild and no public exploit code.

Affected product: n/a. 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-0127/ (Markdown: https://insights.sbomify.com/CVE-2019-0127/index.md)
```

## Sources

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

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