# CVE-2024-6348: Predictable seed generation after ECU reset

> Attackers can bypass security access controls in Nissan Altima Blind Spot Protection Sensors by predicting seeds after ECU resets.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/V:D/RE:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2024
- **Updated:** 19 Aug 2024
- **Also known as:** GHSA-qp2p-3fr2-8j54

## What is CVE-2024-6348?

CVE-2024-6348 is a medium-severity vulnerability in Nissan Altima, published on 19 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Predictable seed generation in the security access mechanism of UDS in the Blind Spot Protection Sensor ECU in Nissan Altima (2022) allows attackers to predict the requested seeds and bypass security controls via repeated ECU resets and seed requests.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2024-6348?

It affects 1 product.


Products: Nissan-Global Blind Spot Protection Sensor Ecu Firmware.

## How do I fix CVE-2024-6348?

No fix has been published for CVE-2024-6348 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6348 being exploited?

There is no known exploitation of CVE-2024-6348 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6348 and fix it if it is affected.

What it is: CVE-2024-6348 is a medium-severity vulnerability in Nissan Altima, published on 19 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6348 in the wild and no public exploit code.

Affected product: Nissan Altima. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6348/ (Markdown: https://insights.sbomify.com/CVE-2024-6348/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6348
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6348
- OSV: https://osv.dev/vulnerability/CVE-2024-6348

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6348/
Summaries are generated and may contain mistakes; the official description above is the record.