Menu

Star on GitHub · 3.2k

CVE-2015-7082

10.0 · HIGH

Multiple unspecified vulnerabilities in Git before 2.5.4, as used in Apple Xcode before 7.2, have unknown impact and attack vectors.

Published Dec 11, 2015git_projectEPSS 1.68%

Overview

CVE-2015-7082 is a high-severity vulnerability affecting git_project git. It was published on December 11, 2015 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Multiple unspecified vulnerabilities in Git before 2.5.4, as used in Apple Xcode before 7.2, have unknown impact and attack vectors. NOTE: this CVE is associated only with Xcode use cases.

Remediation

Check the references section for vendor advisories and patches from git_project. Update git to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
git_projectgit0Affected

Frequently asked questions

What is CVE-2015-7082?

CVE-2015-7082 is a high-severity vulnerability affecting git_project git. It was published on December 11, 2015 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2015-7082?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2015-7082?

Check the references section for vendor advisories and patches from git_project. Update git to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2015-7082?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2015-7082 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2015

View all