dbcve.org
On DemandApplication · Intel

CVE-2023-32283

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Intel(R) On Demand software versions prior to 1.16.2, 2.1.1, and 3.1.0 contain a vulnerability where sensitive information is being written to log files. An authenticated user with local access can potentially read these logs to obtain the exposed sensitive data.

MitigationUpgrade Intel(R) On Demand software to version 1.16.2, 2.1.1, 3.1.0 or later. Review existing log files for any sensitive data exposure and rotate logs if necessary.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
On DemandApplication
Affected:= 1.16.1.1= 2.1.0.1= 3.0.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel On Demand is installed
    Check for the presence of Intel On Demand software on the system. Look for installation directories or use system inventory tools to identify if the product is present.
    Affected if Intel On Demand software is not installed on the system.
  2. Identify the installed version
    Locate the Intel On Demand version information. This is typically found in the software installation directory, system registry, or via the product's built-in version command if available.
    Affected if The installed version cannot be determined or the software is not found.
  3. Compare against affected versions
    Compare your installed version to the following affected versions: 1.16.1.1, 2.1.0.1, and 3.0.1.3. Check if your version is equal to or earlier than these.
    Affected if Your installed version matches or precedes 1.16.1.1, 2.1.0.1, or 3.0.1.3.
  4. Locate log files
    Find log files generated by Intel On Demand. Check the default log directory within the installation path, commonly named 'logs' or similar.
    Affected if Log files exist and were created during operation of the affected software version.
  5. Inspect log contents for sensitive data
    Open and review the log files for any exposed sensitive information such as credentials, tokens, personal data, or other confidential content that should not be written to log files.
    Affected if Log files contain sensitive information that should not have been recorded.

You are affected if Intel On Demand is installed with version 1.16.1.1, 2.1.0.1, or 3.0.1.3 and log files contain sensitive data that should not have been written.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Intel(R) On Demand software to version 1.16.2, 2.1.1, 3.1.0 or later. Review existing log files for any sensitive data exposure and rotate logs if necessary.

Recommended fix Moderate confidence

Upgrade to Intel On Demand version 1.16.2 (or later), 2.1.1 (or later), or 3.1.0 (or later) depending on current installed version

  1. 1. Identify the current installed version of Intel(R) On Demand software
  2. 2. Based on the installed version (1.16.1.1, 2.1.0.1, or 3.0.1.3), obtain the corresponding fixed version from Intel's support website or through your Intel representative
  3. 3. Download the appropriate updated Intel On Demand software package (version 1.16.2 or later for 1.16.x users; version 2.1.1 or later for 2.1.x users; version 3.1.0 or later for 3.0.x users)
  4. 4. Follow Intel's standard upgrade procedure for On Demand software, ensuring proper backups are made before proceeding
  5. 5. After upgrade, verify the new version is correctly installed
  6. 6. Review system logs to confirm the sensitive information is no longer being written to log files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in On Demand Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32283 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data