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

CVE-2017-6435 has a CVSS 3.0 base score of 5.0 (Medium). CVSS vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2017-6435?

Yes, a public proof-of-concept exploit is available for CVE-2017-6435. Prioritise patching immediately. EPSS: 0.1%.

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

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

Libplist CVE-2017-6435

MEDIUM

Buffer Overflow (CWE-119)

2017-03-15 cve@mitre.org

Buffer Overflow Denial Of Service Libplist

5.0

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

5.0 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Mar 15, 2017 - 14:59 cve.org

MEDIUM 5.0

DescriptionCVE.org

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.

AnalysisAI

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. Rated medium severity (CVSS 5.0), this vulnerability is low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. 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. Affected products include: Libplist Project Libplist.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.