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

> Remote attackers can obtain sensitive information or cause a denial of service via a crafted XML file in Apple products using libxml2.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cjcf-pw36-x638

## What is CVE-2017-7013?

CVE-2017-7013 is a high-severity vulnerability in Apple Icloud, published on 20 Jul 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. iOS before 10.3.3 is affected. macOS before 10.12.6 is affected. iCloud before 6.2.2 on Windows is affected. iTunes before 12.6.2 on Windows is affected. tvOS before 10.2.2 is affected. watchOS before 3.2.3 is affected. The issue involves the "libxml2" component. It allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and application crash) via a crafted XML file.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 6 products.


Products: Apple Icloud, Apple Iphone Os, Apple Itunes, Apple Mac Os X, Apple Tvos, Apple Watchos.

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

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

## Is CVE-2017-7013 being exploited?

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

## Other vulnerabilities in Apple Icloud

- [CVE-2019-8506](https://insights.sbomify.com/CVE-2019-8506/): Apple Multiple Products Type Confusion (high 8.8, exploited in the wild)
- [CVE-2020-27932](https://insights.sbomify.com/CVE-2020-27932/): Apple Multiple Products Type Confusion (high 7.8, exploited in the wild)
- [CVE-2019-8746](https://insights.sbomify.com/CVE-2019-8746/): Memory corruption in iOS (critical 9.8)
- [CVE-2019-8749](https://insights.sbomify.com/CVE-2019-8749/): Memory corruption in iOS (critical 9.8)
- [CVE-2019-8756](https://insights.sbomify.com/CVE-2019-8756/): Memory corruption in iOS (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7013 is a high-severity vulnerability in Apple Icloud, published on 20 Jul 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-2017-7013 in the wild and no public exploit code.

Affected product: Apple Icloud. 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-7013/ (Markdown: https://insights.sbomify.com/CVE-2017-7013/index.md)
```

## Sources

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

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