CVE-2021-33073
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 · uneditedUncontrolled resource consumption in the Intel(R) Distribution of OpenVINOâ„¢ Toolkit before version 2021.4 may allow an unauthenticated user to potentially enable denial of service 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 confidenceIntel Distribution of OpenVINO Toolkit before version 2021.4 contains an uncontrolled resource consumption vulnerability that allows an unauthenticated attacker with local access to potentially cause denial of service by exhausting system resources.
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< 2021.4CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify OpenVINO installationCheck for the presence of Intel Distribution of OpenVINO Toolkit on the system. Common installation directories include /opt/intel/openvino/ or C:\Program Files\Intel\openvino\. Look for the openvino environment setup scripts (setupvars.sh on Linux, setupvars.bat on Windows) or the installation directory structure.Affected if OpenVINO toolkit is not found on the system - the user is NOT affected.
-
Determine installed versionLocate and read the version file or check the installation directory name. The version may be encoded in a version.txt file, visible in the installation path, or obtainable by running the OpenVINO environment setup script and checking the returned version information.Affected if Unable to determine the version - manual review required.
-
Compare version to affected rangeCompare the installed version number to 2021.4. The vulnerability affects all versions before 2021.4 (e.g., 2021.3, 2021.2, 2021.1, 2021.0, older releases).Affected if The installed version is lower than 2021.4 - the user IS affected.
-
Assess local access exposureDetermine if untrusted local users have access to the system where OpenVINO is installed. This vulnerability requires local attacker access to exhaust system resources.Affected if Untrusted local users can access the system and OpenVINO version is below 2021.4 - the user IS affected.
The user is affected if Intel Distribution of OpenVINO Toolkit is installed with a version lower than 2021.4 and untrusted local users can access the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2021.4
Upgrade Intel Distribution of OpenVINO Toolkit to version 2021.4 or later to remediate this vulnerability.
2021.4
- Upgrade the Intel Distribution of OpenVINO Toolkit to version 2021.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-33073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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