# CVE-2015-5611: Other in n/a

> Remote attackers on the cellular network can control vehicle movement and modify settings via firmware manipulation and CAN bus access.

- **Severity:** High 8.3 (`AV:A/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 21 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f2p2-8w22-xx6w

## What is CVE-2015-5611?

CVE-2015-5611 is a high-severity vulnerability in n/a, published on 21 Jul 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in Uconnect before 15.26.1, as used in certain Fiat Chrysler Automobiles (FCA) from 2013 to 2015 models, allows remote attackers in the same cellular network to control vehicle movement, cause human harm or physical damage, or modify dashboard settings via vectors related to modification of entertainment-system firmware and access of the CAN bus due to insufficient "Radio security protection," as demonstrated on a 2014 Jeep Cherokee Limited FWD.

## Which versions are affected by CVE-2015-5611?

It affects 1 product.


Products: Fca Uconnect.

## How do I fix CVE-2015-5611?

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

## Is CVE-2015-5611 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5611 and fix it if it is affected.

What it is: CVE-2015-5611 is a high-severity vulnerability in n/a, published on 21 Jul 2015. 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-2015-5611 in the wild and no public exploit code.

Affected product: n/a. 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-2015-5611/ (Markdown: https://insights.sbomify.com/CVE-2015-5611/index.md)
```

## Sources

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

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