dbcve.org
OpenvinoApplication · Intel

CVE-2023-28405

HIGH · 7.8 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 2022.3.0 or later.
See remediation →
80/100
Remediation priority · High
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
Uncontrolled search path in the Intel(R) Distribution of OpenVINO(TM) Toolkit before version 2022.3.0 may allow an authenticated user to potentially enable escalation of privilege 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 · moderate confidence

Intel Distribution of OpenVINO Toolkit before version 2022.3.0 contains an uncontrolled search path vulnerability where the application may load executable code or libraries from user-controlled locations, potentially allowing an authenticated local user to escalate privileges.

MitigationUpgrade to Intel Distribution of OpenVINO Toolkit version 2022.3.0 or later to remediate this vulnerability.

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
OpenvinoApplication
Affected:< 2022.3.0

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
High
Availability
High

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

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. Locate OpenVINO installation
    Search for Intel OpenVINO installation directories, typically under /opt/intel/openvino, C:\Program Files\Intel\openvino, or user's home directory. Check for the presence of the openvino directory structure containing model-optimizer, deployment-tools, or inference_engine libraries.
    Affected if OpenVINO toolkit is found installed on the system
  2. Identify installed version
    Locate the version file or metadata. Common locations include a version.txt file, setup.py version, or the openvino package metadata. The version may also be visible in the installer filename or in registry entries on Windows.
    Affected if A version number cannot be determined or is below 2022.3.0
  3. Compare version against affected range
    Compare the installed version number to 2022.3.0. Note that version comparison must treat 2022.3.0 as the safe version - any version below this (including 2022.2.x, 2022.1.x, 2021.x and earlier) is considered affected.
    Affected if Installed version is a release prior to 2022.3.0 (for example 2022.2.0, 2022.1.0, 2021.4.0, etc.)

The environment is affected if Intel Distribution of OpenVINO Toolkit is installed with any version number lower than 2022.3.0.

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
Upgrade available Upgrade to 2022.3.0 or later
Fixed in 2022.3.0
Interim mitigation

Upgrade to Intel Distribution of OpenVINO Toolkit version 2022.3.0 or later to remediate this vulnerability.

Recommended fix High confidence

2022.3.0

  1. 1. Download the Intel Distribution of OpenVINO Toolkit version 2022.3.0 or later from the official Intel website (download.intel.com) or Intel's developer website.
  2. 2. Uninstall the currently installed version of OpenVINO from the system using the standard uninstallation process for your operating system.
  3. 3. Verify that all environment variables related to OpenVINO (such as OPENVINO_HOME, PATH) are cleaned or updated to point to the new installation path.
  4. 4. Install the downloaded version 2022.3.0 or later by running the installer and following the installation wizard prompts.
  5. 5. After installation, verify the installed version matches or exceeds 2022.3.0 by checking the installation directory or running the version check command.
  6. 6. Ensure that the installation directory is secured and has appropriate access controls to prevent unauthorized modification.
Caveat Review the Intel OpenVINO 2022.3.0 release notes for any API changes or deprecated features that may affect existing workflows

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

Fix this in Openvino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28405 — 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-28405 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