What is the severity of CVE-2017-5545?

CVE-2017-5545 is considered to have a medium severity level due to its potential to cause denial of service and expose sensitive information.

How do I fix CVE-2017-5545?

To fix CVE-2017-5545, upgrade libplist to version 1.13 or later.

What versions of libplist are affected by CVE-2017-5545?

CVE-2017-5545 affects all versions of libplist up to and including 1.12.

What kind of attacks can CVE-2017-5545 facilitate?

CVE-2017-5545 can facilitate attacks that lead to denial of service through buffer over-reads or exposure of sensitive information from process memory.

What is the source of the vulnerability in CVE-2017-5545?

The vulnerability in CVE-2017-5545 originates from improper handling of Apple Property List data in the libplist library.

Vulnerability/
CVE-2017-5545

critical

9.1

CWE

125

21/1/2017

2/4/2020

CVE-2017-5545

First published: Sat Jan 21 2017(Updated: )

The main function in plistutil.c in libimobiledevice libplist through 1.12 allows attackers to obtain sensitive information from process memory or cause a denial of service (buffer over-read) via Apple Property List data that is too short.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
libimobiledevice and libplist	<=1.12

Remedy

https://github.com/libimobiledevice/libplist/commit/7391a506352c009fe044dead7baad9e22dd279ee

Remedy

https://github.com/libimobiledevice/libplist/issues/87

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5545?
CVE-2017-5545 is considered to have a medium severity level due to its potential to cause denial of service and expose sensitive information.
How do I fix CVE-2017-5545?
To fix CVE-2017-5545, upgrade libplist to version 1.13 or later.
What versions of libplist are affected by CVE-2017-5545?
CVE-2017-5545 affects all versions of libplist up to and including 1.12.
What kind of attacks can CVE-2017-5545 facilitate?
CVE-2017-5545 can facilitate attacks that lead to denial of service through buffer over-reads or exposure of sensitive information from process memory.
What is the source of the vulnerability in CVE-2017-5545?
The vulnerability in CVE-2017-5545 originates from improper handling of Apple Property List data in the libplist library.

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

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-5545?
CVE-2017-5545 is considered to have a medium severity level due to its potential to cause denial of service and expose sensitive information.
How do I fix CVE-2017-5545?
To fix CVE-2017-5545, upgrade libplist to version 1.13 or later.
What versions of libplist are affected by CVE-2017-5545?
CVE-2017-5545 affects all versions of libplist up to and including 1.12.
What kind of attacks can CVE-2017-5545 facilitate?
CVE-2017-5545 can facilitate attacks that lead to denial of service through buffer over-reads or exposure of sensitive information from process memory.
What is the source of the vulnerability in CVE-2017-5545?
The vulnerability in CVE-2017-5545 originates from improper handling of Apple Property List data in the libplist library.