CVE-2017-5834

The parse_dict_node function in bplist.c in libplist allows attackers to cause a denial of service (out-of-bounds heap read and crash) via a crafted file.

Published: 2017-03-03 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-5834 is rated Moderate Risk (41.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.32%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-5834

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-15 0.50% 0.32% -0.18%
2 2025-11-21 0.22% 0.50% +0.29%
3 2025-11-18 — 0.22% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5834

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2017-5834

OS Trackers for CVE-2017-5834

vendor priority summary link
debian not yet assigned CVE-2017-5834 not yet assigned priority: Debian including 1 source packages (libplist), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-5834
redhat low — https://access.redhat.com/security/cve/CVE-2017-5834
suse medium CVE-2017-5834 severity moderate: SUSE including 30 source package names (libplist++-2_0-3-2.2.0-1.6, libplist++-2_0-3-32bit-2.2.0-1.6, …), 92 product×package rows across 38 product lines (SUSE Linux Enterprise Desktop 12 SP1, SUSE Linux Enterprise Desktop 12 SP2, … (38 product lines)): Fixed 92. https://www.suse.com/security/cve/CVE-2017-5834/
ubuntu negligible CVE-2017-5834 negligible priority: Ubuntu including 1 source packages (libplist), 23 status rows across 23 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 17, ignored 3, DNE 1, needed 1, released 1. https://ubuntu.com/security/CVE-2017-5834

Affected software / configurations for CVE-2017-5834

Vendor Product Version Raw CPE
libimobiledevice libplist — cpe:2.3:a:libimobiledevice:libplist:*:*:*:*:*:*:*:*

References for CVE-2017-5834

cvelogic Threat Intelligence