Xcode 7.3.1

About the security content of Xcode 7.3.1

 

This document describes the security content of Xcode 7.3.1. For the protection of our customers, Apple does not disclose, discuss, or confirm security issues until a full investigation has occurred and any necessary patches or releases are available. To learn more about Apple Product Security, see the Apple Product Security website. For information about the Apple Product Security PGP Key, see How to use the Apple Product Security PGP Key. Where possible, CVE IDs are used to reference the vulnerabilities for further information. To learn about other security updates, see Apple security updates.

 

Xcode 7.3.1

 

Git

Available for: OS X El Capitan v10.11 and later

Impact: A remote attacker may be able to execute arbitrary code

Description: A heap-based buffer overflow issue existed in the handling of filenames. This issue was addressed by updating git to version 2.7.4.

 

CVE-ID

 

CVE‑2016‑2324

Integer overflow in Git before 2.7.4 allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, which triggers a heap-based buffer overflow.

Bugfix patches were backported from the ‘master’ front to plug heap corruption holes, to catch integer overflow in the computation of pathname lengths, and to get rid of the name_path API. Both of these would have resulted in writing over an under-allocated buffer when formulating pathnames while tree traversal.

 

CVE‑2016‑2315

revision.c in git before 2.7.4 uses an incorrect integer data type, which allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, leading to a heap-based buffer overflow.

A remote authenticated user can push a specially crafted repository to trigger a heap overflow and execute arbitrary code on the target system [CVE-2016-2315].

Lael Cellier (@ytrezq) reported this vulnerability.

 

Share on FacebookTweet about this on TwitterPin on PinterestShare on Google+
Rbcafe © 2004- | Rb Cafe 1.3 | Contacto Rbcafe | Rbcafe en Twitter | Rbcafe en Facebook | Política de privacidad