Home Cyber Crime Git vulnerability could enable remote code execution attacks during clone process

Git vulnerability could enable remote code execution attacks during clone process


Jessica Haworth

10 March 2021 at 15:30 UTC

Up to date: 10 March 2021 at 15:56 UTC

Replace to the newest model now, say builders

The Git Project has patched a bug that could lead to remote code execution for some users

The Git Mission has patched a vulnerability that might lead to remote code execution.

The bug – tracked as CVE-2021-21300 – is current in a number of variations of the open source code administration system, and will enable a hostile distant repository to execute code regionally throughout a clone operation.

Crucially, the vulnerability solely impacts customers with case-insensitive filesystems that allow assist for symbolic hyperlinks. Recordsdata utilizing a clear/smudge filter akin to Git LFS should even be enabled for the assault to work.

Read more of the latest remote code execution news

An announcement launched yesterday (March 9) reads: “On case-insensitive file techniques with assist for symbolic hyperlinks, if Git is configured globally to use delay-capable clear/smudge filters (akin to Git LFS), Git might be fooled into working distant code throughout a clone.”

A security advisory reads: “In affected variations of Git, a specifically crafted repository that incorporates symbolic hyperlinks in addition to recordsdata utilizing a clear/smudge filter akin to Git LFS, could trigger just-checked out script to be executed whereas cloning onto a case-insensitive file system akin to NTFS, HFS+ or APFS (i.e., the default file techniques on Home windows and macOS).

“Observe that clear/smudge filters must be configured for that.”

Git customers are urged to replace as quickly as potential. The discharge fixes the bug in variations 2.17.6 by way of to 2.30.2.

Copycat issues

Git customers usually clone an current repository for numerous causes, akin to constructing on a totally fledged copy from elsewhere or conserving a replica of their venture in case the server disk is corrupted.

For the reason that RCE vulnerability solely impacts case-insensitive filesystems, not all Git customers are weak to exploitation.

MacOS – which enabled case-insensitive filesystems by default – is especially open to assault, multiple sources have warned, as is Home windows, which configures Git LFS by default.

READ Git developers release test code to transition away from aging SHA-1 hashing

“As a workaround, if symbolic hyperlink assist is disabled in Git (e.g by way of ), the described assault gained’t work.

“Likewise, if no clear/smudge filters akin to Git LFS are configured globally (i.e ), the assault is foiled. As at all times, it’s best to keep away from cloning repositories from untrusted sources,” the advisory reads.

Different working techniques akin to Linux – which is case-sensitive by default – are presumed to be protected, nevertheless customers ought to nonetheless heed warning.

“This vulnerability impacts case-insensitive file techniques, due to this fact typical Linux situations ought to be protected,” wrote Purple Hat software program engineer Huzaifa Sidhpurwala.

“Nonetheless as per upstream exploitation is even potential on Linux underneath sure circumstances.”

Bettering consumer security

Git was created again in 2005 by Linus Torvalds as a system to trace modifications in supply code for the Linux kernel.

Lately, it has undergone main modifications together with moving away from the aging SHA-1 hashing algorithm to a safer various.

Nonetheless, transferring to a stronger hash has proved to be a difficult migration since within the early days of Git, Torvalds was “unconcerned about the potential of SHA‑1 being damaged”, and due to this fact he by no means designed within the capability to change to a distinct hash.

YOU MAY ALSO LIKE Git security: Newline injection bug tricked version control system into leaking usernames and password

Source link