CVE-2024-6347
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* Unprotected privileged mode access through UDS session in the Blind Spot Detection Sensor ECU firmware in Nissan Altima (2022) allows attackers to trigger denial-of-service (DoS) by unauthorized access to the ECU's programming session. * No preconditions implemented for ECU management functionality through UDS session in the Blind Spot Detection Sensor ECU in Nissan Altima (2022) allows attackers to disrupt normal ECU operations by triggering a control command without authentication.
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 Blind Spot Detection Sensor ECU in the Nissan Altima (2022) lacks authentication controls on its UDS (Unified Diagnostic Services) session, allowing unauthenticated attackers to access privileged programming modes. This enables denial-of-service conditions and unauthorized execution of ECU control commands without any preconditions.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify Blind Spot Detection Sensor ECU in the vehicleAccess the vehicle's diagnostic system (OBD-II port) and query for ECUs using standard diagnostic protocols. Look for the Blind Spot Detection Sensor ECU (often labeled as BSD or Blind Spot Detection) in the list of available control modules.Affected if The Blind Spot Detection Sensor ECU is present and responding to diagnostic queries
-
Verify UDS session accessibility without authenticationConnect to the Blind Spot Detection Sensor ECU via OBD-II and attempt to initiate a UDS diagnostic session (service $10) without providing any authentication credentials or security access level.Affected if A UDS diagnostic session is established successfully without requiring any authentication token or security access sequence
-
Check for privileged programming mode accessAttempt to access UDS service $27 (Security Access) or service $2E (Write Data By Identifier) on the Blind Spot Detection Sensor ECU. These services typically require elevated privileges for ECU programming or parameter modification.Affected if Privileged programming modes are accessible without prior security authentication or return a positive response indicating access granted
-
Confirm lack of access control on ECU control commandsSend UDS control command services (such as $10 for diagnostic session control, $14 for clear diagnostic information, or $19 for read DTC information) to the Blind Spot Detection Sensor ECU without any pre-authentication.Affected if ECU control commands execute and return successful responses without requiring any authentication or access control verification
The user is affected if their Nissan Altima (2022) has a Blind Spot Detection Sensor ECU and that ECU accepts UDS diagnostic sessions or privileged programming commands without requiring authentication.
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 authentication and session management for UDS diagnostic sessions, particularly for privileged ECU programming operations, and enforce proper access controls on all control commands to prevent unauthorized execution.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6347 — 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-6347 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