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

> Attackers can intercept encrypted API data to obtain vehicle location and control remote parking or unlocking features.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v39m-fc2p-hp53

## What is CVE-2018-18071?

CVE-2018-18071 is a high-severity vulnerability in n/a, published on 9 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Daimler Mercedes-Benz Me app 2.11.0-846 for iOS. The encrypted Connected Vehicle API data exchange between the app and a server might be intercepted. The app can be used to operate the Remote Parking Pilot, unlock the vehicle, or obtain sensitive information such as latitude, longitude, and direction of travel.

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

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

It affects 1 product.


Products: Mercedes-Benz Mercedes Me.

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

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

## Is CVE-2018-18071 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-47392](https://insights.sbomify.com/CVE-2023-47392/): Missing authorization in n/a (medium 5.3)
- [CVE-2023-47393](https://insights.sbomify.com/CVE-2023-47393/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18071 is a high-severity vulnerability in n/a, published on 9 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18071 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-18071/ (Markdown: https://insights.sbomify.com/CVE-2018-18071/index.md)
```

## Sources

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

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