Skip to content
Fencer Intel
medium 5.0

CVE-2017-6435 json

The parse_string_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a denial of service (memory corrup…

published 2017-03-15 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15492

cvss
5.0
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

The parse_string_node function in bplist.c in libimobiledevice libplist 1.12 allows local users to cause a denial of service (memory corruption) via a crafted plist file.

Patch / fix

  • libplist Debian 14, Debian 13, Debian 12 1.12+git+1+e37ca00-0.1

debian advisories DEBIAN-CVE-2017-6435

  • libplist SLES for SAP 12 SP3, SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2 +8 more 1.12-20.3.2

suse advisories SUSE-SU-2017:2201-1

  • libplist Arch Linux 2.0.0-1

arch linux advisories AVG-215

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-6435 updated cvss 3.3

libplist: Missing return value check from malloc()

  • Red Hat Enterprise Linux 6 libplist, libplist-python Red Hat Enterprise Linux 7 libplist, libplist-python
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/libimobiledevice/libplist/issues/93 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.0 CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.