CVE-2017-5835: High severity libimobiledevice libplist vulnerability
Published Mar 3, 2017
·Updated
libplist allows attackers to cause a denial of service (large memory allocation and crash) via vectors involving an offset size of zero.
Affected Software
2 affected componentsFixes available
libimobiledevice libplist
Microsoft cbl2 libplist 2.1.0-4
Remediation
Patch Available
Patch Available
Patch Available
Event History
Mar 3, 2017
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:59 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 1, 2025
Data Sourced
via Microsoft·11:10 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·11:10 PM
Affected Software
Updated
via Microsoft·11:10 PM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2017-5835?
CVE-2017-5835 is classified as a medium severity vulnerability due to its potential to disrupt service.
2
How do I fix CVE-2017-5835?
To fix CVE-2017-5835, update to the latest version of libplist where the vulnerability has been addressed.
3
What type of attack does CVE-2017-5835 enable?
CVE-2017-5835 enables attackers to perform a denial of service attack through large memory allocation resulting in crashes.
4
Which software is affected by CVE-2017-5835?
CVE-2017-5835 affects libplist as included in the libimobiledevice suite.
5
Can CVE-2017-5835 be exploited remotely?
Yes, CVE-2017-5835 can potentially be exploited remotely if the vulnerable software is exposed to untrusted input.