# CVE-2017-7147: Information disclosure in n/a

> Remote attackers can obtain sensitive analytics data from the Apple Support app due to cleartext HTTP transmission to Adobe Marketing Cloud.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 23 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3m24-mjhw-3m4j

## What is CVE-2017-7147?

CVE-2017-7147 is a medium-severity vulnerability in n/a, published on 23 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in certain Apple products. The Apple Support app before 1.2 for iOS is affected. The issue involves the "Analytics" component. It allows remote attackers to obtain sensitive analytics information by leveraging its presence in a cleartext HTTP transmission to an Adobe Marketing Cloud server operated for Apple, as demonstrated by information about the installation date and time.

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

## Which versions are affected by CVE-2017-7147?

It affects 1 product.


Products: Apple Apple Support.

## How do I fix CVE-2017-7147?

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

## Is CVE-2017-7147 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-4397](https://insights.sbomify.com/CVE-2018-4397/): Information disclosure in Apple Support app (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7147 and fix it if it is affected.

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

## Sources

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

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