# CVE-2024-52005 status?

3 messages from 2025-11-02 to 2025-11-02. Participants: Thomas Klausner, brian m. carlson, rsbecker@nexbridge.com.
Thread: https://gitlist.dev/t/64420

## Thomas Klausner, 2025-11-02 00:48

Subject: CVE-2024-52005 status?
Message-ID: <7mfgh4ufx6wr3ict2ee6utg3vvfpiy6xi3rfyfu4yionmcwu6a@yry3kefdxbwf>
URL: https://gitlist.dev/e/7mfgh4ufx6wr3ict2ee6utg3vvfpiy6xi3rfyfu4yionmcwu6a%40yry3kefdxbwf

```
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?

Thanks,
 Thomas

(Please cc me, I'm not subscribed.)

```

## brian m. carlson, 2025-11-02 15:58

Subject: Re: CVE-2024-52005 status?
Message-ID: <aQd_iisOrwX909Fr@fruit.crustytoothpaste.net>
URL: https://gitlist.dev/e/aQd_iisOrwX909Fr%40fruit.crustytoothpaste.net
In-Reply-To: <7mfgh4ufx6wr3ict2ee6utg3vvfpiy6xi3rfyfu4yionmcwu6a@yry3kefdxbwf>

```
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

```

## rsbecker@nexbridge.com, 2025-11-02 16:19

Subject: RE: CVE-2024-52005 status?
Message-ID: <01a101dc4c14$7f8f8000$7eae8000$@nexbridge.com>
URL: https://gitlist.dev/e/01a101dc4c14%247f8f8000%247eae8000%24%40nexbridge.com
In-Reply-To: <aQd_iisOrwX909Fr@fruit.crustytoothpaste.net>

```
On November 2, 2025 10:58 AM, brian m. carlson wrote:
>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.

If the code that dumps messages like this is localized, perhaps we can run a filter that
removes any non-printable characters (like \ESC) that could trigger this. It might be
switchable in some variable like core.filterUnprintableCharacters=true to opt-in to
prevent this. However, some emulators might just see a URL and treat it like a link,
so I don't know.


```