# CVE-2023-32283: Information disclosure in Intel(R) On Demand software

> An authenticated local user can access sensitive information logged by Intel On Demand software, leading to potential data exposure.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 Nov 2023
- **Updated:** 30 Aug 2024
- **Also known as:** GHSA-w369-f878-vgmj

## What is CVE-2023-32283?

CVE-2023-32283 is a medium-severity vulnerability in Intel(R) On Demand software, published on 14 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insertion of sensitive information into log file in some Intel(R) On Demand software before versions 1.16.2, 2.1.1, 3.1.0 may allow an authenticated user to potentially enable information disclosure via local access.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Intel on Demand.

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

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

## Is CVE-2023-32283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32283 is a medium-severity vulnerability in Intel(R) On Demand software, published on 14 Nov 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-32283 in the wild and no public exploit code.

Affected product: Intel(R) On Demand 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-32283/ (Markdown: https://insights.sbomify.com/CVE-2023-32283/index.md)
```

## Sources

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

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