# CVE-2018-4397: Information disclosure in Apple Support app

> Analytics data was transmitted over unencrypted HTTP, allowing attackers to intercept sensitive usage information from the Apple Support app.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g665-9726-cg3r

## What is CVE-2018-4397?

CVE-2018-4397 is a medium-severity vulnerability in Apple Support app, published on 3 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Analytics data was sent using HTTP rather than HTTPS. This was addressed by sending analytics data using HTTPS. This issue affected versions prior to Apple Support 2.4 for iOS.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Apple Apple Support.

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

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

## Is CVE-2018-4397 being exploited?

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

## Other vulnerabilities in Apple Support app

- [CVE-2017-7147](https://insights.sbomify.com/CVE-2017-7147/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-4397 is a medium-severity vulnerability in Apple Support app, published on 3 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-4397 in the wild and no public exploit code.

Affected product: Apple Support app. 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-4397/ (Markdown: https://insights.sbomify.com/CVE-2018-4397/index.md)
```

## Sources

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

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