Safeguard
Vulnerability Analysis•

CVE-2023-28897: Medium Hard-Coded Secret in Skoda MIB3 Infotainment

CVE-2023-28897 is a hard-coded secret for diagnostic services in the Skoda MIB3 infotainment firmware. No fix is stated; ask your dealer about updates.

Safeguard Security Team
3 min read

CVE-2023-28897 is a hard-coded secret in the firmware of the MIB3 infotainment unit, used to guard critical UDS diagnostic services. It was reported on a 2022 Skoda Superb III. NVD scores it 4.0, Medium. The advisory I read does not state a fix, so ask the manufacturer.

What's affected

The ASRG advisory says the issue was found on a Skoda Superb III (3V3) 2.0 TDI manufactured in 2022, and the NVD entry lists the Superb 3 firmware for 2022 and the Superb 3 hardware. The advisory names the MIB3 infotainment unit as the component. It does not list other vehicles, so I cannot say which other models share the same firmware.

Fixed version: not stated in the advisory I read, and it does not describe a vendor response. Treat this as unconfirmed and ask a Skoda dealer or the manufacturer whether an infotainment software update addresses it.

Severity: NVD scores it 4.0, Medium. The ASRG page gives no score of its own and links to NVD.

How to check if you're exposed

For a vehicle owner, there is no command to run. Ask your dealer whether your infotainment software version is the one reported and whether an update is available. For a fleet manager, list the vehicles by model and production year and ask the supplier the same question.

For engineers who build or integrate automotive firmware, check whether any diagnostic service secret, seed key or password is the same across units or sits in the firmware image.

What to do now

  1. Ask the manufacturer or dealer whether a software update for the MIB3 unit addresses this CVE.
  2. Do not leave unknown devices connected to the vehicle's diagnostic port, since that is where diagnostic services are normally reached.
  3. If you run a fleet, record which vehicles carry the affected infotainment units.
  4. For firmware teams, replace fixed secrets with per-device values that are not stored in the image.
  5. Check the Gold page for this CVE for later changes.

Why it matters

The record classes the flaw as CWE-798 (Use of Hard-coded Credentials). A hard-coded secret is the same in every unit that carries that firmware. Once someone extracts it from one device, it works on all of them. The advisory places it under authentication bypass, since anyone who holds the secret can reach services that were meant to be locked.

The score is Medium because reaching the diagnostic services normally requires physical or close access to the vehicle. The page does not describe specific consequences beyond access to those services, and I will not guess at more. The wider lesson for hardware makers is that fixed secrets age badly: they are found by firmware analysis, shared, and cannot be revoked without a firmware update.

Automotive diagnostic protocols such as UDS were designed for workshops, where the person at the port is a trusted technician. As cars gain more connected systems, the gate in front of those services matters more. A per-vehicle secret, or one issued by the manufacturer on request, keeps one extracted key from opening every car.

Quick check

Is there a fix?

The advisory I read does not say. Ask the manufacturer or a dealer.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.