# CVE-2019-14596: Missing authorization in Intel(R) Chipset Device Software INF Utility

> An authenticated local user can cause a denial of service in the Intel Chipset Device Software INF Utility installer due to improper access control.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 17 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-364x-r3f5-mp8c

## What is CVE-2019-14596?

CVE-2019-14596 is a medium-severity missing authorization vulnerability in Intel(R) Chipset Device Software INF Utility, published on 17 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in the installer for Intel(R) Chipset Device Software INF Utility before version 10.1.18 may allow an authenticated user to potentially enable denial of service via local access.

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

It affects 1 product.


Products: Intel Chipset Inf Utility.

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

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

## Is CVE-2019-14596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14596 is a medium-severity missing authorization vulnerability in Intel(R) Chipset Device Software INF Utility, published on 17 Jan 2020. 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-14596 in the wild and no public exploit code.

Affected product: Intel(R) Chipset Device Software INF Utility. 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-14596/ (Markdown: https://insights.sbomify.com/CVE-2019-14596/index.md)
```

## Sources

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

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