From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Thomas Klausner <wiz@gatalith.at>
Cc: git@vger.kernel.org
Subject: Re: CVE-2024-52005 status?
Date: Sun, 2 Nov 2025 15:58:02 +0000 [thread overview]
Message-ID: <aQd_iisOrwX909Fr@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <7mfgh4ufx6wr3ict2ee6utg3vvfpiy6xi3rfyfu4yionmcwu6a@yry3kefdxbwf>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On 2025-11-02 at 00:48:53, Thomas Klausner wrote:
> Hi!
>
> I'm trying to find out more details about CVE-2024-52005 so I can
> handle it correctly in pkgsrc.
>
> https://nvd.nist.gov/vuln/detail/CVE-2024-52005
>
> points to
>
> https://github.com/git/git/security/advisories/GHSA-7jjc-gg6m-3329
>
> which lists many affected versions, but no fixed versions. I only
> found one reference to the CVE in the release announcement for 'Git
> for Windows' 2.47.1(2):
>
> https://groups.google.com/g/git-packagers/c/ZWDc6K6tYcc/m/VxikezMeCgAJ
>
> The CVE description sounds like this also might affect non-Windows Git
> versions. Can someone please tell me if this was fixed, and in which
> version?
We determined this was not a vulnerability. The Git for Windows
maintainer disagreed and listed it as one nevertheless.
The problem is that on some terminal emulators, including at least some
of the ones available on Windows, you can execute arbitrary binaries by
creating a hyperlink via terminal codes and having someone click on it.
That is, however, a bug in the terminal emulator and not in Git, since
clicking a URL should not lead to code execution.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2025-11-02 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 0:48 CVE-2024-52005 status? Thomas Klausner
2025-11-02 15:58 ` brian m. carlson [this message]
2025-11-02 16:19 ` rsbecker
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=aQd_iisOrwX909Fr@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=wiz@gatalith.at \
/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 NNTP newsgroup(s).