CVE-2024-54728
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 · uneditedIncorrect access control in BYD QIN PLUS DM-i Dilink OS 3.0_13.1.7.2204050.1 allows unauthorized attackers to access system logcat logs.
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 confidenceThis vulnerability in BYD QIN PLUS DM-i Dilink OS 3.0_13.1.7.2204050.1 allows unauthorized attackers to access system logcat logs due to incorrect access control. Logcat logs often contain sensitive system information, debug messages, and potentially credentials or tokens, making this an information disclosure issue.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm the vehicle model and infotainment systemIdentify if the system is a BYD QIN PLUS DM-i vehicle using the Dilink OS infotainment system. Check the vehicle settings or system information for the model and OS identification.Affected if The vehicle is not a BYD QIN PLUS DM-i or does not use Dilink OS - not affected.
-
Check the Dilink OS versionNavigate to the system settings on the infotainment unit and locate the OS version information. Compare the installed version against 3.0_13.1.7.2204050.1.Affected if The installed version matches or is earlier than 3.0_13.1.7.2204050.1 - potentially affected.
-
Verify logcat access is exposedAttempt to access the logcat utility or log files through the infotainment system interfaces (such as developer menus, USB debugging, or service menus). Determine if logcat output can be retrieved without authentication.Affected if Logcat logs are accessible without requiring authentication or elevated privileges - vulnerable configuration present.
-
Inspect logcat for sensitive data exposureIf logcat is accessible, examine the log output for sensitive information such as credentials, tokens, system details, or debug messages that should not be visible to unauthorized users.Affected if Logcat output contains sensitive system information, credentials, or tokens that should be restricted - confirms the information disclosure vulnerability.
A user is affected if they own a BYD QIN PLUS DM-i running Dilink OS version 3.0_13.1.7.2204050.1 or earlier, and logcat logs are accessible without authentication on their infotainment system.
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 dataImplement proper authentication and authorization checks before allowing access to logcat logs. Restrict log access to privileged/system processes only, and ensure any sensitive data is filtered or redacted from logs.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54728 — 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-2024-54728 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