Bug 2533153 (CVE-2025-24890) - CVE-2025-24890 gix-sec: gix-sec: Privilege escalation via incorrect repository trust on Windows
Summary: CVE-2025-24890 gix-sec: gix-sec: Privilege escalation via incorrect repositor...
Keywords:
Status: NEW
Alias: CVE-2025-24890
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2535015 2535016
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-14 15:33 UTC by OSIDB Bzimport
Modified: 2026-09-16 07:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-14 15:33:22 UTC
gitoxide is an implementation of git written in Rust. Prior to 0.13.3, the gix-sec crate on Windows incorrectly treats repositories controlled by another user as trusted when an administrator runs a dependent program with an unfiltered elevated token. In gix-sec/src/identity.rs, gix_sec::identity::is_path_owned_by_current_user obtains folder_owner and token_owner, but its administrator-specific IsWellKnownSid and CheckTokenMembership checks examine the running token rather than confirming the directory owner. This bypasses safe.directory-style protection for repositories owned and configured by a limited user, allowing repository configuration or hooks to execute commands with the administrator's privileges when an affected operation is performed. Exploitation requires Windows, an elevated administrator, a program that relies on gix-sec trust results, and interaction with a repository controlled by another user. An unelevated UAC process is not affected, and cloning is not affected because repository configuration and hooks are not copied. This issue is fixed in version 0.13.3.


Note You need to log in before you can comment on or make changes to this bug.