CVE-2019-8739
First published: Fri Sep 20 2019(Updated: )
A memory corruption issue was addressed with improved state management. This issue is fixed in Xcode 11.0. Processing a maliciously crafted file may lead to arbitrary code execution.
Credit: product-security@apple.com Pan ZhenPeng @Peterpan0927 Qihoo 360 Nirvan TeamPan ZhenPeng @Peterpan0927 Qihoo 360 Nirvan Team
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apple Xcode | <11.0 | |
| Apple Xcode | <11.0 | 11.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Peer vulnerabilities
(Found alongside the following vulnerabilities)
Frequently Asked Questions
What is CVE-2019-8739?
CVE-2019-8739 is a vulnerability related to otool, a memory corruption issue that allows for arbitrary code execution.
How does CVE-2019-8739 affect Apple Xcode?
CVE-2019-8739 affects Apple Xcode versions prior to 11.0, allowing arbitrary code execution when processing a malicious file.
What is the severity of CVE-2019-8739?
The severity of CVE-2019-8739 is high, with a CVSS score of 7.8.
Is there a fix for CVE-2019-8739?
Yes, the issue is fixed in Xcode 11.0, so updating to this version will resolve the vulnerability.
Where can I find more information about CVE-2019-8739?
More information about CVE-2019-8739 can be found at the following references: [link1], [link2].
- collector/nvd-index
- collector/apple-support
- alias/CVE-2019-8739
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/type
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/tags
- agent/description
- collector/mitre-cve
- source/MITRE
- vendor/apple
- canonical/apple xcode