Most recent entries from all

ALSA-2023:3245 — Important: git security update

Affected: AlmaLinux:9: git, AlmaLinux:9: git-all, AlmaLinux:9: git-core, AlmaLinux:9: git-core-doc, AlmaLinux:9: git-credential-libsecret, AlmaLinux:9: git-daemon, AlmaLinux:9: git-email, AlmaLinux:9: git-gui, AlmaLinux:9: git-instaweb, AlmaLinux:9: git-subtree and 5 more

Git is a distributed revision control system with a decentralized architecture. As opposed to centralized version control systems with a client-server model, Git ensures that each working copy of a Git repository is an exact copy with complete revision history. This not only allows the user to work on and contribute to projects without the need to have permission to push the changes to their official repositories, but also makes it possible for the user to work with no network connection.

Security Fix(es):

* git: by feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents (CVE-2023-25652) * git: arbitrary configuration injection when renaming or deleting a section from a configuration file (CVE-2023-29007) * git: data exfiltration with maliciously crafted repository (CVE-2023-22490) * git: git apply: a path outside the working tree can be overwritten with crafted input (CVE-2023-23946) * git: malicious placement of crafted messages when git was compiled with runtime prefix (CVE-2023-25815)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

bdu:2023-06650

Withdrawn: BELL-CVE-2023-25815 — CVE-2023-25815 does not affect BellSoft software

Withdrawn by the publisher.

certfr-2023-avi-0465 — De multiples vulnérabilités ont été corrigées dans les produits Microsoft. Elles permettent…

certfr-2023-avi-0465

CLEANSTART-2026-EP87015 — In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer

Affected: CleanStart: git

Security vulnerability affects the git package. In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer.

EUVD-2026-258817

fkie_cve-2023-25815

This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may remove the permission to create folders in `C:\`.

gsd-2023-25815

OESA-2023-1269 — git security update

Affected: openEuler:20.03-LTS-SP1: git, openEuler:20.03-LTS-SP3: git, openEuler:22.03-LTS: git, openEuler:22.03-LTS-SP1: git

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows. Security Fix(es): Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file exists.(CVE-2023-25652) In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer uses the…

openSUSE-SU-2024:12889-1 — git-2.40.1-1.1 on GA media

git-2.40.1-1.1 on GA media

RHSA-2023:3192 — Red Hat Security Advisory: git security update

git: by feeding specially crafted input to `git apply --reject`, a path outside the working tree can be overwritten with partially controlled contents git: malicious placement of crafted messages when git was compiled with runtime prefix git: arbitrary configuration injection when renaming or deleting a section from a configuration file

SUSE-SU-2023:2038-2 — Security update for git

Security update for git

UBUNTU-CVE-2023-25815

Affected: Ubuntu:Pro:16.04:LTS: git, Ubuntu:18.04:LTS: git, Ubuntu:20.04:LTS: git, Ubuntu:22.04:LTS: git

In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path `C:\mingw64\share\locale` to look for localized messages. And since any authenticated user has the permission to create folders in `C:\` (and since `C:\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in that location where `git.exe` will pick them up in version 2.40.1. This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may remove the permission to create folders in `C:\`.

WID-SEC-W-2023-1072 — git: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in git ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren und seine Privilegien zu erweitern.