libplist project vulnerabilities
Recent CVEs affecting libplist project products. 6 tracked.
libplist project has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-03-15. Highest priority: CVE-2017-6438 (score 44/100).
- CVE-2017-6440 MEDIUM 5.0 DOWNGRADE The parse_data_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a denia
- CVE-2017-6439 MEDIUM 5.0 DOWNGRADE Heap-based buffer overflow in the parse_string_node function in bplist.c in libimobiledevice libplist 1.12 all
- CVE-2017-6438 HIGH 7.3 DOWNGRADE Heap-based buffer overflow in the parse_unicode_node function in bplist.c in libimobiledevice libplist 1.12 al
- CVE-2017-6437 MEDIUM 5.0 DOWNGRADE The base64encode function in base64.c in libimobiledevice libplist 1.12 allows local users to cause a denial o
- CVE-2017-6436 MEDIUM 5.0 DOWNGRADE The parse_string_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a den
- CVE-2017-6435 MEDIUM 5.0 DOWNGRADE The parse_string_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a den
FAQ
How do I fix libplist project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libplist project being exploited right now?
None of the tracked libplist project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libplist project CVE should I patch first?
CVE-2017-6438 currently ranks highest (44/100): Heap-based buffer overflow in the parse_unicode_node function in bplist.c in libimobiledevice libplist 1.12 al.