Описание
Security update for git-lfs
This update for git-lfs fixes the following issues:
Changes in git-lfs:
-
update to 3.7.1: (boo#1252259 CVE-2025-26625)
This release introduces security fixes for Linux, macOS, and Windows systems, which have been collectively assigned CVE-2025-26625.
When populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS.
Git LFS has resolved this problem by revising the git lfs checkout and git lfs pull commands so that they check for symbolic links in the same manner as performed by Git before writing to files in the working tree. These commands now also remove existing files in the working tree before writing new files in their place.
As well, Git LFS has resolved a problem whereby the git lfs checkout and git lfs pull commands, when run in a bare repository, could write to files visible outside the repository. While a specific and relatively unlikely set of conditions were required for this to occur, it is no longer possible under any circumstances.
We would like to extend a special thanks to the following open-source contributors: Apple Product Security for reporting this to us responsibly
- Bugs
- Detect symbolic links on checkout and pull (@chrisd8088)
- Misc
- Upgrade to Go 1.25 (@chrisd8088)
- Bugs
-
update to 3.7.0
This release is a feature release which introduces several new options for fetching Git LFS objects, such as the ability to force objects to be re-downloaded and the capacity to output object URLs and HTTP metadata in JSON for external tools to consume. This release also adds a configurable in-memory cache of file path pattern matches, which along with other changes can help reduce the time required to migrate large repositories to Git LFS.
Git LFS now supports the same .netrc files on Windows as Git and curl, retries appropriately after all 429 status code HTTP responses, permits the use of symbolic links to Git's object storage during Git LFS migrations
- Features
- Cache a file path filter match result #6047 (@alexkad0)
- Add --refetch option to fetch #5975 (@redsun82)
- Add --json option to fetch #5974 (@redsun82)
- Add --dry-run option to fetch #5973 (@redsun82)
- Bugs
- Verify TLS/SSL certificates using default Go support for macOS system root CAs #6049 (@chrisd8088)
- Prefer .netrc on windows if present #6055 (@johanvdw)
- Fix migrations where .git/objects is a symlink #6042 (@bk2204)
- Honour 429 object transfer response Retry-After headers #6014 (@chrisd8088)
- Misc
- Update Linux distribution package list for v3.7.0 release (@chrisd8088)
- Report missing objects consistently when pushing #6027 (@chrisd8088)
- Use a git-update-ref script to update references #6048 (@alexkad0)
- Drop unused generic stub function for cloning files #6050 (@chrisd8088)
- Prevent conflicting curl macros in early Git version CI jobs #6040 (@chrisd8088)
- pull: improve error message on failing checkout #5629 (@bk2204)
- Fix language in code snippets in API docs #6035 (@slonopotamus)
- build(deps): bump golang.org/x/net from 0.36.0 to 0.38.0 #6034 (@dependabot[bot])
- Use single-target Makefile patterns for manual pages #6032 (@chrisd8088)
- use direct value nil for error #6024 (@alingse)
- Update minimum required Git version checks #6028 (@chrisd8088)
- build(deps): bump golang.org/x/net from 0.33.0 to 0.36.0 #6012 (@dependabot[bot])
- Upgrading x/crypto to v0.35.0 to solve CVE-2025-22869 bsc#1239322 #5997 (@gergelyfabian)
- Upgrade to Go 1.24 #6013 (@chrisd8088)
- Use constant format strings and fix HTTP error messages #5998 (@chrisd8088)
- Remove command name prefixes from progress messages #5995 (@chrisd8088)
- doc: Add missing "--to" argument in git-lfs-checkout example #6005 (@DarkDefender)
- Replace min/max helpers with built-in min/max #5999 (@Juneezee)
- Add security patch release process documentation #5987 (@chrisd8088)
- Replace unused debug mode with trace logging #5989 (@chrisd8088)
- Use default Ruby provided by Actions runners #5984 (@chrisd8088)
- build(deps): bump azure/trusted-signing-action from 0.5.0 to 0.5.1 #5981 (@dependabot[bot])
- Update workflows to use ARM runners and new Apple signing certificate #5977 (@chrisd8088)
- docs/man/git-lfs-prune.adoc: fix --(no-)verify-unreachable description #5959 (@m3ka24)
- docs/man/git-lfs-migrate.adoc: remove duplicate flag #5944 (@fedirz)
- Upgrade golang.org/x/net from 0.23.0 to 0.33.0 #5940 (@gergelyfabian)
- build(deps): bump golang.org/x/crypto from 0.21.0 to 0.31.0 #5935 (@dependabot[bot])
- Simplify macOS CI jobs and specify Go toolchain version #5931 (@chrisd8088)
- Tighten security of Actions workflows #5930 (@bk2204)
- Corrected Pop!_OS naming #5929 (@LucasDondo)
- Update release process documentation and scripts #5920 (@chrisd8088)
- Update license copyright dates and minimum supported Git version #5921 (@chrisd8088)
- Features
Список пакетов
openSUSE Leap 16.0
Ссылки
- SUSE Security Ratings
- SUSE Bug 1239322
- SUSE Bug 1252259
- SUSE CVE CVE-2025-22869 page
- SUSE CVE CVE-2025-26625 page
Описание
SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.
Затронутые продукты
Ссылки
- CVE-2025-22869
- SUSE Bug 1239322
Описание
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.
Затронутые продукты
Ссылки
- CVE-2025-26625
- SUSE Bug 1252259