# CVE-2016-7666: Information disclosure in n/a

> Attackers can obtain sensitive information by crafting a malicious EPUB file processed by Apple Transporter.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r3x2-hcpw-54h4

## What is CVE-2016-7666?

CVE-2016-7666 is a medium-severity vulnerability in n/a, published on 20 Feb 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in certain Apple products. Transporter before 1.9.2 is affected. The issue involves the "iTMSTransporter" component, which allows attackers to obtain sensitive information via a crafted EPUB.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-7666?

It affects 1 product.


Products: Apple Transporter.

## How do I fix CVE-2016-7666?

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

## Is CVE-2016-7666 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7666 and fix it if it is affected.

What it is: CVE-2016-7666 is a medium-severity vulnerability in n/a, published on 20 Feb 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-7666 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-2016-7666/ (Markdown: https://insights.sbomify.com/CVE-2016-7666/index.md)
```

## Sources

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

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