What is the severity of CVE-2017-5836?

CVE-2017-5836 has been classified as a denial of service vulnerability that can lead to application crashes.

How do I fix CVE-2017-5836?

To mitigate CVE-2017-5836, users should apply the patches released by the libimobiledevice project for libplist.

What software is affected by CVE-2017-5836?

CVE-2017-5836 affects the libplist component used in libimobiledevice.

Can CVE-2017-5836 be exploited remotely?

CVE-2017-5836 is a local vulnerability that requires the attacker to have access to manipulate plist files.

What are the consequences of exploiting CVE-2017-5836?

Exploiting CVE-2017-5836 can lead to a denial of service, causing the application to crash.

Vulnerability/
CVE-2017-5836

high

7.5

CWE

415

3/3/2017

7/3/2017

CVE-2017-5836: Double Free

First published: Fri Mar 03 2017(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
libimobiledevice and libplist

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5836?
CVE-2017-5836 has been classified as a denial of service vulnerability that can lead to application crashes.
How do I fix CVE-2017-5836?
To mitigate CVE-2017-5836, users should apply the patches released by the libimobiledevice project for libplist.
What software is affected by CVE-2017-5836?
CVE-2017-5836 affects the libplist component used in libimobiledevice.
Can CVE-2017-5836 be exploited remotely?
CVE-2017-5836 is a local vulnerability that requires the attacker to have access to manipulate plist files.
What are the consequences of exploiting CVE-2017-5836?
Exploiting CVE-2017-5836 can lead to a denial of service, causing the application to crash.

agent/weakness
agent/references
agent/type
agent/event
agent/description
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
agent/severity
agent/remedy
agent/author
vendor/libimobiledevice
canonical/libimobiledevice and libplist

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-5836?
CVE-2017-5836 has been classified as a denial of service vulnerability that can lead to application crashes.
How do I fix CVE-2017-5836?
To mitigate CVE-2017-5836, users should apply the patches released by the libimobiledevice project for libplist.
What software is affected by CVE-2017-5836?
CVE-2017-5836 affects the libplist component used in libimobiledevice.
Can CVE-2017-5836 be exploited remotely?
CVE-2017-5836 is a local vulnerability that requires the attacker to have access to manipulate plist files.
What are the consequences of exploiting CVE-2017-5836?
Exploiting CVE-2017-5836 can lead to a denial of service, causing the application to crash.

CVE-2017-5836: Double Free

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5836?

How do I fix CVE-2017-5836?

What software is affected by CVE-2017-5836?

Can CVE-2017-5836 be exploited remotely?

What are the consequences of exploiting CVE-2017-5836?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2017-5836?

How do I fix CVE-2017-5836?

What software is affected by CVE-2017-5836?

Can CVE-2017-5836 be exploited remotely?

What are the consequences of exploiting CVE-2017-5836?