CVE-2020-0573
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 · uneditedOut of bounds read in the Intel CSI2 Host Controller driver 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 confidenceAn out-of-bounds read vulnerability exists in the Intel CSI2 (Camera Serial Interface 2) Host Controller driver. The flaw allows an authenticated local user to read memory contents beyond allocated buffer boundaries, potentially exposing sensitive information. This is a driver-level vulnerability affecting how the CSI2 host controller handles data transfers.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel CSI2 hardware is presentOn Linux, run 'lspci | grep -i csi2' or 'lspci | grep -i camera' to list camera/CSI2 related devices. On Windows, open Device Manager and look under 'System devices' or 'Cameras' for Intel CSI2 Host Controller.Affected if The Intel CSI2 Host Controller device appears in the system hardware listing
-
Check if the CSI2 host controller driver is loadedOn Linux, run 'lsmod | grep csi' or check /proc/modules for any csi2-related kernel modules. On Windows, open Device Manager, locate the Intel CSI2 Host Controller, and view driver details.Affected if The CSI2 driver is installed and loaded in the system
-
Determine driver versionOn Linux, use 'modinfo <csi2_module_name>' if a module is identified. On Windows, right-click the Intel CSI2 Host Controller in Device Manager, select Properties, then view the Driver version field.Affected if Any version of the Intel CSI2 Host Controller driver is installed (the vulnerability affects all versions)
-
Verify local authenticated user accessReview system user accounts and local access controls. Check which users have console or local login access to the affected machine.Affected if Untrusted or unauthorized local users have authenticated access to the system where CSI2 hardware and driver are present
A system is affected if it contains Intel CSI2 Host Controller hardware with the driver installed, regardless of version, and untrusted local users can gain authenticated access.
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.
From vendor dataApply the Intel-provided driver update or firmware patch for the CSI2 Host Controller. Verify that only trusted, authenticated users have local access to affected systems to reduce the attack surface.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0573 — 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-2020-0573 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