Skip to content
Fencer Vulns
critical 9.1

CVE-2017-5209 json

The base64decode function in base64.c in libimobiledevice libplist through 1.12 allows attackers to obtain sensitive information from proce…

published 2017-01-11 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-14315

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

Summary

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.

Patch / fix

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

debian advisories DEBIAN-CVE-2017-5209

  • libplist SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +3 more 1.12-19.1
  • libplist SLES for SAP 12 SP1, SLES 12 SP1, SLED 12 SP1 +3 more 1.8-10.9.1

suse advisories SUSE-SU-2017:1379-1SUSE-SU-2017:1368-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-5209 updated cvss 4.4

libplist: base64decode buffer over-read via split encoded Apple Property List data

  • Red Hat Enterprise Linux 6 libplist, libplist-python Red Hat Enterprise Linux 7 libplist, libplist-python
    not affected: vulnerable code not present

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

2.85% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Vulns 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.