From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-announce@cygwin.com
Subject: Security update: Git v2.35.2-1
Date: Wed, 13 Apr 2022 08:49:34 +0100 [thread overview]
Message-ID: <CA+kUOamuCv-3GPc0wDeHrwoqbkL+o=NuW_+z5s_B=r0SJ1hMCw@mail.gmail.com> (raw)
Version 2.35.2-1 of Git has been uploaded and should be coming soon to a
mirror near you.
This is an update to the latest upstream release, and fixes security
vulnerability CVE-2022-24765:
> On multi-user machines, Git users might find themselves unexpectedly
> in a Git worktree, e.g. when another user created a repository in
> `C:\.git`, in a mounted network drive or in a scratch space. Merely
> having a Git-aware prompt that runs `git status` (or `git diff`) and
> navigating to a directory which is supposedly not a Git worktree, or
> opening such a directory in an editor or IDE such as VS Code or Atom,
> will potentially run commands defined by that other user.
This update includes the following packages:
- git
- git-cvs
- git-debuginfo
- git-email
- git-gui
- gitk
- git-p4
- git-svn
For a full list of the upstream changes in this release, please refer to the
upstream changelogs, available at:
https://git.kernel.org/cgit/git/git.git/tree/Documentation/RelNotes
https://github.com/git/git/tree/master/Documentation/RelNotes
Enjoy!
reply other threads:[~2022-04-13 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+kUOamuCv-3GPc0wDeHrwoqbkL+o=NuW_+z5s_B=r0SJ1hMCw@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=cygwin-announce@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).