Live data from Hacker News

Git client vulnerability announced

github.com

41–50 of 191 posts

Re: Git client vulnerability announced

#41
post #8

Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git

brew update will use `git clone`, so yeah...

If you read the blog post, GitHub has checked all their repos for for this exploit and is blocking it on pushes; cloning from GitHub should be safe.

Re: Git client vulnerability announced

#42
post #8

Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git

brew update will use `git clone`, so yeah...

You better walk over to the Homebrew office and get the update on a USB stick then, Mr. Safety!

Re: Git client vulnerability announced

#43

> We have also completed an automated scan of all existing content on github.com to look for malicious content that might have been pushed to our site before this vulnerability was discovered did they find any problems? The post doesn't say...

Vicent Marti (from GitHub) states: "In case it's not obvious from the post: There are no malicious repos in @github and they can't be pushed anymore. Update your Git anyway." https://twitter.com/vmg/status/545693913491984385

Which still doesn't say! That says there aren't any, but is silent on whether there were any. It's probably safe to assume that this is just clumsy wording and he meant to say that the scan found nothing, but it could also be a careful attempt at trying to sound like it says more than it really does.

Re: Git client vulnerability announced

#44

Earlier quoted context omitted.

The announcement includes several links to binaries. Is there one you need that's missing?

The blog post on Github.com only includes links to Github for Mac binaries, not git proper. The link in the blog post to kernel.org has tarballs of source, not binaries. Did I miss something?

It also includes a link to msysgit for Windows. If you need some type of binary not listed, it would help if you mention what type of binaries you need.

Re: Git client vulnerability announced

#45
post #8

Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git

Ironically, Homebrew uses git to update its package metadata, but presumably you already trust Homebrew to not deliver malicious software (I also don't know if "pull" is vulnerable, or just "clone" and "checkout". Also Homebrew is hosted on Github, which now scans/blocks malicious repos)

Re: Git client vulnerability announced

#46
post #6

Earlier quoted context omitted.

It's a very high priority, because there are things that transparently use Git and don't host all their repositories on Github. Update ASAP.

Yeah, but typically you have a certain level of trust in your project dependencies. Adding a library to your project often means granting access to your system anyway (if the dependency contains executable code).

You can at least in theory inspect the library code after cloning it but before compiling it. Insta-owning your machine just because you cloned it is considerably worse. This is especially true if you always run the library in a sandbox of some sort (e.g. you're building an Android app and your code always runs on an Android device or emulator).

Re: Git client vulnerability announced

#48
post #29

Earlier quoted context omitted.

Wow downvoting because I ask for binaries instead of source? Majority of people reading this want a fast, immediate solution from a trustworthy source. edit: obvious places still haven't updated. git-scm still provides 6-month-old binaries

[deleted]

[deleted]

Re: Git client vulnerability announced

#49

Should programs periodically check for critical security fixes, and then refuse to run if the current version is affected? It seems like there are a lot of people who don't really pay attention to social media or other security alert channels, who won't have a clue about the extent of this vulnerability. I'm sure they'd update if they knew "if I clone a malicious repo, I'm toast," but there's no way to inform them ex…

Coming from NPM land, sounds like a nice module to build.

Re: Git client vulnerability announced

#50
post #30
post #8

Homebrew just updated ( https://github.com/Homebrew/homebrew/pull/35105 ), so Homebrew users should be covered by brew update && brew upgrade git

I keep getting fatal: unable to access 'https://github.com/Homebrew/homebrew/': The requested URL returned error: 503 Error: Failure while executing: git pull -q origin refs/heads/master:refs/remotes/origin/master Weird, it's the first time it's ever happened. edit: wait, it worked after a couple of tries; maybe it's due to panicked people updating brew\git?

This might be an issue with github due to load or their security fixes or code scans. I've been able to run `brew update && brew upgrade git`.
Post reply on HN