CVE-2017-5836 Memory corruption in n/a

High 7.5 Published Updated

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

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

Which versions are affected by CVE-2017-5836?

It affects 1 product.

Products include Libimobiledevice Libplist.

How do I fix CVE-2017-5836?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-5836 being exploited?

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

Sources

Also known as AZL-36956, AZL-7269, DEBIAN-CVE-2017-5836, GHSA-978x-427c-qcqh, UBUNTU-CVE-2017-5836.

Is CVE-2017-5836 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free