# CVE-2017-5836: Memory corruption in n/a

> Attackers can cause a denial of service via a crash in libplist due to an invalid free triggered by improper handling of integer nodes.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** AZL-36956, AZL-7269, DEBIAN-CVE-2017-5836, GHSA-978x-427c-qcqh, UBUNTU-CVE-2017-5836

## What is CVE-2017-5836?

CVE-2017-5836 is a high-severity memory corruption vulnerability in n/a, published on 3 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The plist_free_data function in plist.c in libplist allows attackers to cause a denial of service (crash) via vectors involving an integer node that is treated as a PLIST_KEY and then triggers an invalid free.

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Libimobiledevice Libplist.

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

Apply the vendor's patch.

## Is CVE-2017-5836 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5545](https://insights.sbomify.com/CVE-2017-5545/): Information disclosure in n/a (critical 9.1)
- [CVE-2017-5209](https://insights.sbomify.com/CVE-2017-5209/): Information disclosure in n/a (critical 9.1)
- [CVE-2017-5835](https://insights.sbomify.com/CVE-2017-5835/): Denial of service in n/a (high 7.5)
- [CVE-2015-10082](https://insights.sbomify.com/CVE-2015-10082/): UIKit0 libplist XML xplist.c plist_from_xml xml external entity reference (medium 5.5)
- [CVE-2017-7982](https://insights.sbomify.com/CVE-2017-7982/): Integer overflow in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5836 is a high-severity memory corruption vulnerability in n/a, published on 3 Mar 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-5836 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-5836/ (Markdown: https://insights.sbomify.com/CVE-2017-5836/index.md)
```

## Sources

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

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