CVE-2023-28907
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 · uneditedThere is no memory isolation between CPU cores of the MIB3 infotainment. This fact allows an attacker with access to the main operating system to compromise the CPU core responsible for CAN message processing. The vulnerability was originally discovered in Skoda Superb III car with MIB3 infotainment unit OEM part number 3V0035820. The list of affected MIB3 OEM part numbers is provided in the referenced resources.
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 confidenceThe MIB3 infotainment system lacks memory isolation between CPU cores, allowing an attacker with main OS access to compromise the separate CPU core responsible for CAN message processing. This enables interference with safety-critical vehicle communications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MIB3 infotainment system in useCheck vehicle infotainment system version through diagnostic tools, firmware identification, or system information interfaces (e.g., infotainment head unit part number, firmware version string)Affected if System is identified as MIB3 (third-generation Modular Infotainment Platform)
-
Verify memory isolation configurationInspect system firmware or hypervisor configuration for memory isolation between application processor cores. Check for separate memory domains or protected memory regions for CAN processing.Affected if No hypervisor or memory isolation layer is configured between main OS and CAN processing core
-
Check CAN processing core isolationAnalyze system architecture documentation or firmware configuration to determine if CAN message processing runs on a separate, isolated CPU core with dedicated memoryAffected if CAN processing shares the same memory space or CPU core as the main infotainment OS without hardware-level isolation
User is affected if MIB3 infotainment system is present and there is no memory isolation configured between the main OS and the CAN processing core
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 dataOEM firmware update implementing proper memory isolation (e.g., hypervisor, separate memory domains) between the infotainment and CAN bus processing cores; hardware isolation or separate MCU may be required for complete remediation.
- Consultation40.0 h
- Implementation120.0 h
- Testing80.0 h
- Review / QA40.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $78,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28907 — 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-2023-28907 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