121–130 of 139 posts
What is the recommended upgrade path for macOS' system install of git? I have upgraded my brew install, but am unsure of what to do with the vulnerable system install.
Earlier quoted context omitted.
> Integer overflow isn't a security issue unless your program's memory safety depends on the correctness of the integer operation. That's simply not true and has wide-reaching horrible effects that can occur. The wrong number of tickets can be purchased from a website, charging for less than were purchased. The DNR order can be put in place instead of SAVE LIFE. There are countless security issues that can occur. Say…
Do you have data on the relative frequency and severity of non-memory safety integer overflow security issues?
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=integer+ove...
Earlier quoted context omitted.
As best I can tell from the "The Windows-specific issue involves a $PATH lookup including the current working directory" part, it would be: echo "calc.exe" > aspell.cmd git commit -a -m"lolol windows" and wait for someone to clone that repo
What I don't quite get is why there's spellchecking on incoming commits at all.
Earlier quoted context omitted.
Don't understand what you mean by "incoming commits". git-gui shows you a textbox for the commit message, and error squiggles for misspelled words (presumably; I CBA to install a spell checker). The bug is that it spawns the spellcheck binary using Tcl's API, which on Windows also looks up binaries in the current directory regardless of whether the current directory is in $PATH or not. Edit: Maybe you're referring to…
My reason for asking that is that this is the vuln description from the article: > After cloning a repository, Git GUI automatically applies some post-processing to the resulting checkout, including running a spell-checker, if one is available. > A Windows-specific vulnerability causes Git GUI to look for the spell-check in the worktree that was just checked out, which may result in running untrusted code. I get what…
What happens is that, when you use it clone a repo it immediately shows the window for authoring a new commit message, which as I said will invoke the spell-check. That's why you are vulnerable from the moment you use git-gui to clone.
Earlier quoted context omitted.
Your could use interrupts, no? Basically free when not triggered and when triggered you probably don't care about performance anymore.
Most architectures do not provide an interrupt that is generated by an integer overflow. Since this would be a significant architectural change in the hardware, it can't be simply added in. Additionally, if you are running inside an operating system, handling an interrupt usually incurs a trip through the kernel, which would add extra overhead every time an overflow did happen. Since there's a lot of software which d…
Earlier quoted context omitted.
I too think package managers are amazing... reads new git security threat "brew upgrade" done!
Running brew upgrade uses git, so it has to run the insecure git to upgrade.
Earlier quoted context omitted.
> Integer overflow isn't a security issue unless your program's memory safety depends on the correctness of the integer operation. That's simply not true and has wide-reaching horrible effects that can occur. The wrong number of tickets can be purchased from a website, charging for less than were purchased. The DNR order can be put in place instead of SAVE LIFE. There are countless security issues that can occur. Say…
Do you have data on the relative frequency and severity of non-memory safety integer overflow security issues?