What is the severity of CVE-2017-5209?

CVE-2017-5209 has a medium severity rating due to its potential for information disclosure and denial of service.

How do I fix CVE-2017-5209?

To fix CVE-2017-5209, upgrade to libplist version 1.12 or later, where the vulnerability has been addressed.

What are the potential impacts of CVE-2017-5209?

CVE-2017-5209 can lead to sensitive information disclosure or a denial of service through buffer over-read.

Is CVE-2017-5209 remotely exploitable?

CVE-2017-5209 is typically considered not remotely exploitable as it requires specific conditions to be met.

Which versions of libplist are affected by CVE-2017-5209?

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

Vulnerability/
CVE-2017-5209

critical

9.1

CWE

125

11/1/2017

5/8/2024

CVE-2017-5209

First published: Wed Jan 11 2017(Updated: )

The base64decode function in base64.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 split encoded Apple Property List data.

Credit: cve@mitre.org

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

Remedy

https://github.com/libimobiledevice/libplist/commit/3a55ddd3c4c11ce75a86afbefd085d8d397ff957

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5209?
CVE-2017-5209 has a medium severity rating due to its potential for information disclosure and denial of service.
How do I fix CVE-2017-5209?
To fix CVE-2017-5209, upgrade to libplist version 1.12 or later, where the vulnerability has been addressed.
What are the potential impacts of CVE-2017-5209?
CVE-2017-5209 can lead to sensitive information disclosure or a denial of service through buffer over-read.
Is CVE-2017-5209 remotely exploitable?
CVE-2017-5209 is typically considered not remotely exploitable as it requires specific conditions to be met.
Which versions of libplist are affected by CVE-2017-5209?
CVE-2017-5209 affects all versions of libplist up to and including version 1.12.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/author
agent/weakness
agent/remedy
agent/last-modified-date
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
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-5209?
CVE-2017-5209 has a medium severity rating due to its potential for information disclosure and denial of service.
How do I fix CVE-2017-5209?
To fix CVE-2017-5209, upgrade to libplist version 1.12 or later, where the vulnerability has been addressed.
What are the potential impacts of CVE-2017-5209?
CVE-2017-5209 can lead to sensitive information disclosure or a denial of service through buffer over-read.
Is CVE-2017-5209 remotely exploitable?
CVE-2017-5209 is typically considered not remotely exploitable as it requires specific conditions to be met.
Which versions of libplist are affected by CVE-2017-5209?
CVE-2017-5209 affects all versions of libplist up to and including version 1.12.