Bug 2535015 - CVE-2025-24890 rust: gix-sec: Privilege escalation via incorrect repository trust on Windows [fedora-all]
Summary: CVE-2025-24890 rust: gix-sec: Privilege escalation via incorrect repository t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rust
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Rust SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["efc2ef0c-6a29-4a69-acb2-e...
Depends On:
Blocks: CVE-2025-24890
TreeView+ depends on / blocked
 
Reported: 2026-09-16 07:32 UTC by Ganesh
Modified: 2026-09-16 07:47 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-09-16 07:35:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-09-16 07:32:20 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.