Vulnerabilities for products matching "xcode"
Found 1 matching product.
You can search for specific versions with /product/xcode/1.2.3
apple / xcode
124 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
High | December 18, 2019 12/18/19 |
< 11.0
|
|
|
|
High | December 18, 2019 12/18/19 |
< 11.0
|
|
|
|
Critical | July 29, 2019 7/29/19 |
< 13.3
|
|
|
|
High | April 3, 2019 4/3/19 |
< 10
|
|
|
|
High | March 21, 2019 3/21/19 |
< 11.0
|
|
|
|
High | November 7, 2018 11/7/18 |
< 13.0
|
|
|
|
High | November 7, 2018 11/7/18 |
< 13.0
|
|
|
|
Medium | November 7, 2018 11/7/18 |
< 13.0
|
|
|
|
High | April 3, 2018 4/3/18 |
< 9.3
|
|
|
|
Medium | April 3, 2018 4/3/18 |
< 9.2
|
|
|
|
Medium | October 23, 2017 10/23/17 |
<= 8.3.3
|
|
|
|
Medium | October 23, 2017 10/23/17 |
<= 8.3.3
|
|
|
|
Medium | October 23, 2017 10/23/17 |
<= 8.3.3
|
|
|
|
Medium | October 23, 2017 10/23/17 |
<= 8.3.3
|
|
|
|
High | July 13, 2017 7/13/17 |
< 13.0
|
|
|
|
High | September 18, 2016 9/18/16 |
<= 7.3.1
|
|
|
|
High | September 18, 2016 9/18/16 |
<= 7.3.1
|
|
|
|
Low | March 24, 2016 3/24/16 |
<= 7.2.1
|
|
|
|
Medium | February 15, 2016 2/15/16 |
< 13.0
|
|
|
|
Critical | February 15, 2016 2/15/16 |
< 13.0
|
|
|
|
High | February 15, 2016 2/15/16 |
< 13.0
|
|
|
|
Low | December 11, 2015 12/11/15 |
<= 7.1.1
|
|
|
|
Medium | December 11, 2015 12/11/15 |
<= 7.1.1
|
|
|
|
Low | December 11, 2015 12/11/15 |
<= 7.1.1
|
|
|
|
High | October 23, 2015 10/23/15 |
<= 7.0
|
|
|
|
Low | September 18, 2015 9/18/15 |
<= 6.4
|
|
|
|
Medium | September 18, 2015 9/18/15 |
<= 6.4
|
|
|
|
Low | August 12, 2015 8/12/15 |
<= 7.2.1
|
|
|
|
Medium | August 12, 2015 8/12/15 |
<= 7.2.1
|
|
|
|
Low | July 20, 2015 7/20/15 |
== 7.0
|
|
|
|
Medium | April 10, 2015 4/10/15 |
<= 6.2
|
|
|
|
High | April 10, 2015 4/10/15 |
<= 6.2
|
|
|
|
Low | April 8, 2015 4/8/15 |
== 7.0
|
|
|
|
Medium | April 8, 2015 4/8/15 |
== 7.0
|
|
|
|
Medium | December 18, 2014 12/18/14 |
== 6.1.1
|
|
|
|
Medium | December 18, 2014 12/18/14 |
== 6.1.1
|
|
|
|
High | October 8, 2014 10/8/14 |
== 7.0
|
|
|
|
Low | August 19, 2014 8/19/14 |
== 6.1.1
|
|
|
|
Low | August 19, 2014 8/19/14 |
== 6.1.1
|
|
|
|
Medium | July 26, 2012 7/26/12 |
== 4.0
== 3.2.4
== 2.2.0
== 3.1.4
== 3.1.3
== 4.2.1
== 3.1
== 3.2.3
== 4.3.1
== 3.1.1
== 4.3
== 2.4.1
== 4.3.2
== 4.0.1
== 3.2.1
== 1.5.0
== 2.3.0
== 4.0.2
== 3.1.2
== 2.1.0
<= 4.3.3
== 2.4.0
== 3.2.2
== 3.2.5
== 4.1.1
== 4.2
== 2.0.0
|
|
|
|
Medium | July 14, 2008 7/14/08 |
== 1.5
== 2.2
|
|
|
|
High | October 17, 2006 10/17/06 |
<= 2.2
|
|
|
|
High | October 17, 2006 10/17/06 |
<= 2.2
|
|
|
|
Low | May 24, 2006 5/24/06 |
<= 2.2
|
|
|
|
High | December 31, 2004 12/31/04 |
== 1.5
|
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.