CVE-2025-28169
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 · uneditedBYD QIN PLUS DM-i Dilink OS v3.0_13.1.7.2204050.1 to v3.0_13.1.7.2312290.1_0 was discovered to cend broadcasts to the manufacturer's cloud server unencrypted, allowing attackers to execute a man-in-the-middle attack.
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 confidenceThe BYD QIN PLUS DM-i Dilink OS versions 3.0_13.1.7.2204050.1 through 3.0_13.1.7.2312290.1_0 transmit broadcast data to the manufacturer's cloud server without encryption, enabling a man-in-the-middle attacker to intercept, modify, or inject malicious 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Locate the Dilink OS version in the infotainment systemAccess the vehicle's infotainment settings, typically found under Settings > About > Version Information, or Settings > System > Version on the center console screenAffected if The displayed version falls within 3.0_13.1.7.2204050.1 through 3.0_13.1.7.2312290.1_0 inclusive
-
Compare your version string against the affected rangeExtract the full version number displayed (format: 3.0_13.1.7.XXXXXXX.X) and verify if the numeric portion after 3.0_13.1.7. is >= 2204050.1 and <= 2312290.1Affected if Your version number is greater than or equal to 2204050.1 and less than or equal to 2312290.1_0
-
Confirm the vehicle's network connectivity statusCheck if the vehicle infotainment system has an active data connection (cellular or Wi-Fi) enabled for cloud services such as remote vehicle status, over-the-air updates, or companion app connectivityAffected if The vehicle is connected to a network and uses cloud services while running an affected version
-
Inspect network traffic for unencrypted protocolsUsing a network monitoring tool on a connected device or vehicle diagnostics port, observe outgoing connections from the infotainment system to the manufacturer's cloud endpoints; look for plain HTTP (port 80) or other non-TLS communications destined for BYD cloud serversAffected if Cleartext HTTP traffic to cloud servers is observed from the vehicle's infotainment system
Your vehicle is affected if the Dilink OS version is 3.0_13.1.7.2204050.1 through 3.0_13.1.7.2312290.1_0 and the infotainment system has an active network connection for cloud services.
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 dataThe vehicle firmware requires an update to implement TLS/SSL encryption for all cloud communications; users should avoid connecting to untrusted networks until the manufacturer releases a patch.
- Consultation12.0 h
- Implementation60.0 h
- Testing30.0 h
- Review / QA15.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $32,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28169 — 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-2025-28169 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