What is the CVSS score of CVE-2017-5545?

CVE-2017-5545 has a CVSS 3.0 base score of 9.1 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. EPSS exploitation probability: 0.4%.

Is there a patch available for CVE-2017-5545?

Yes, a patch is available for CVE-2017-5545. Update the affected software to the latest version immediately.

Libimobiledevice CVE-2017-5545

CRITICAL

Out-of-bounds Read (CWE-125)

2017-01-21 cve@mitre.org

Buffer Overflow Denial Of Service Information Disclosure Apple Libimobiledevice Libplist

9.1

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

9.1 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Jan 21, 2017 - 01:59 cve.org

CRITICAL 9.1

DescriptionCVE.org

AnalysisAI

The main function in plistutil.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. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Out-of-bounds Read vulnerability could allow attackers to read data from memory outside the intended buffer boundaries.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. The main function in plistutil.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 Apple Property List data that is too short. Affected products include: Libimobiledevice Libplist. Version information: through 1.12.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.