CVE-2019-8738
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 |
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 the severity of CVE-2019-8738?
The severity of CVE-2019-8738 is high.
How does CVE-2019-8738 affect Apple Xcode?
CVE-2019-8738 affects Apple Xcode version up to exclusive 11.0.
How can CVE-2019-8738 be exploited?
CVE-2019-8738 can be exploited by processing a maliciously crafted file, which may lead to arbitrary code execution.
Has CVE-2019-8738 been fixed?
CVE-2019-8738 has been fixed in Xcode 11.0.
Where can I find more information about CVE-2019-8738?
You can find more information about CVE-2019-8738 on the Apple support website.
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/author
- agent/last-modified-date
- agent/severity
- agent/event
- agent/description
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/apple-support
- alias/CVE-2019-8739
- vendor/apple
- canonical/apple xcode