vulnerability
Amazon Linux 2023: CVE-2025-27613: Important priority package update for git
| Severity | CVSS | Published | Added | Modified |
|---|---|---|---|---|
| 4 | (AV:N/AC:M/Au:N/C:N/I:P/A:N) | Jul 8, 2025 | Jul 30, 2025 | Jul 30, 2025 |
Severity
4
CVSS
(AV:N/AC:M/Au:N/C:N/I:P/A:N)
Published
Jul 8, 2025
Added
Jul 30, 2025
Modified
Jul 30, 2025
Description
Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.
A vulnerability has been identified in the gitk application that could lead to unauthorized file modification or data loss.
This flaw manifests in two primary scenarios:
- Untrusted Repository Cloning: When a user is tricked into cloning an untrusted Git repository and then uses gitk to visualize it without any additional parameters, any writable file on the user's system can be arbitrarily created or truncated. Exploitation via this method also requires the Support per-file encoding option to be explicitly enabled in Gitk's preferences, which is not the default setting.
- 'Show origin of this line' Command: The vulnerability can also be triggered if a user employs the Show origin of this line command within gitk's main window while viewing a malicious repository. This method does not depend on the Support per-file encoding option being enabled.
The primary risk is unauthorized file system modification, which could lead to data integrity issues, data loss, or potentially open avenues for further system compromise.
A vulnerability has been identified in the gitk application that could lead to unauthorized file modification or data loss.
This flaw manifests in two primary scenarios:
- Untrusted Repository Cloning: When a user is tricked into cloning an untrusted Git repository and then uses gitk to visualize it without any additional parameters, any writable file on the user's system can be arbitrarily created or truncated. Exploitation via this method also requires the Support per-file encoding option to be explicitly enabled in Gitk's preferences, which is not the default setting.
- 'Show origin of this line' Command: The vulnerability can also be triggered if a user employs the Show origin of this line command within gitk's main window while viewing a malicious repository. This method does not depend on the Support per-file encoding option being enabled.
The primary risk is unauthorized file system modification, which could lead to data integrity issues, data loss, or potentially open avenues for further system compromise.
Solutions
amazon-linux-2023-upgrade-gitamazon-linux-2023-upgrade-git-allamazon-linux-2023-upgrade-git-coreamazon-linux-2023-upgrade-git-core-debuginfoamazon-linux-2023-upgrade-git-core-docamazon-linux-2023-upgrade-git-credential-libsecretamazon-linux-2023-upgrade-git-credential-libsecret-debuginfoamazon-linux-2023-upgrade-git-cvsamazon-linux-2023-upgrade-git-daemonamazon-linux-2023-upgrade-git-daemon-debuginfoamazon-linux-2023-upgrade-git-debuginfoamazon-linux-2023-upgrade-git-debugsourceamazon-linux-2023-upgrade-git-emailamazon-linux-2023-upgrade-git-guiamazon-linux-2023-upgrade-git-instawebamazon-linux-2023-upgrade-gitkamazon-linux-2023-upgrade-git-p4amazon-linux-2023-upgrade-git-subtreeamazon-linux-2023-upgrade-git-svnamazon-linux-2023-upgrade-gitwebamazon-linux-2023-upgrade-perl-gitamazon-linux-2023-upgrade-perl-git-svn
NEW
Explore Exposure Command
Confidently identify and prioritize exposures from endpoint to cloud with full attack surface visibility and threat-aware risk context.