Skoda ConnectApplication · Skoda Auto

CVE-2023-28900

MEDIUM · 5.3 CVSS v3.1 Published 2024-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The Skoda Automotive cloud contains a Broken Access Control vulnerability, allowing to obtain nicknames and other user identifiers of Skoda Connect service users by specifying an arbitrary vehicle VIN number.

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

The Skoda Automotive cloud API lacks proper authorization validation when retrieving user data associated with vehicle identification numbers (VINs). An attacker can query the API with any valid VIN to obtain associated user nicknames and other identifiers, indicating an Insecure Direct Object Reference (IDOR) or broken access control vulnerability where the service fails to verify the requesting user owns or has permission to access the specified vehicle.

MitigationImplement and enforce proper authentication and authorization checks to validate that the requesting user owns or has legitimate access rights to the vehicle before returning any associated user data. Additionally, consider removing or obfuscating unnecessary user identifiers exposed through API endpoints.

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
Skoda ConnectApplication
Affected:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Skoda Connect usage
    Identify whether your organization or users utilize the Skoda Auto Skoda Connect cloud service for vehicle management or telematics
    Affected if Skoda Connect is actively used as the cloud platform for vehicle data access
  2. Verify API authentication requirement
    Inspect API documentation or capture network traffic to confirm that the affected endpoints require valid authentication credentials (such as OAuth tokens, API keys, or session tokens)
    Affected if API endpoints accept requests without requiring authentication tokens
  3. Check authorization validation for VIN-based queries
    Test or inspect API responses when requesting user data associated with a vehicle identification number (VIN) - verify whether the API validates that the requesting user owns or has permission to access that specific vehicle before returning data
    Affected if API returns user nicknames, identifiers, or personal data for any valid VIN without confirming the requester's ownership of that vehicle
  4. Identify exposed user identifiers
    Review API response payloads to determine what user-identifying information is returned - look for fields such as user nicknames, account identifiers, email addresses, or other personal data linked to VINs
    Affected if API responses expose user nicknames or other personal identifiers in association with vehicle data without ownership verification

You are affected if your environment uses Skoda Connect and the API returns user data for vehicle VINs without verifying that the requesting user owns or has permission to access that vehicle.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement and enforce proper authentication and authorization checks to validate that the requesting user owns or has legitimate access rights to the vehicle before returning any associated user data. Additionally, consider removing or obfuscating unnecessary user identifiers exposed through API endpoints.

Fix this in Skoda Connect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28900 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