# CVE-2018-11477: Information disclosure in n/a

> Attackers can intercept unencrypted vehicle data transmitted between the mobile app and the OBD2 dongle due to lack of encryption and weak wireless protection.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 30 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8683-jchg-7mg5

## What is CVE-2018-11477?

CVE-2018-11477 is a medium-severity vulnerability in n/a, published on 30 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Vgate iCar 2 Wi-Fi OBD2 Dongle devices. The data packets that are sent between the iOS or Android application and the OBD dongle are not encrypted. The combination of this vulnerability with the lack of wireless network protection exposes all transferred car data to the public.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2018-11477?

It affects 1 product.


Products: Vgate Icar 2 Wi-Fi Obd2 Firmware.

## How do I fix CVE-2018-11477?

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

## Is CVE-2018-11477 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11476](https://insights.sbomify.com/CVE-2018-11476/): Auth bypass in n/a (high 8.8)
- [CVE-2018-11478](https://insights.sbomify.com/CVE-2018-11478/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11477 and fix it if it is affected.

What it is: CVE-2018-11477 is a medium-severity vulnerability in n/a, published on 30 May 2018. 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-2018-11477 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-2018-11477/ (Markdown: https://insights.sbomify.com/CVE-2018-11477/index.md)
```

## Sources

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

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