The vulnerability arises from improper verification of repository ownership in the gix-sec crate of gitoxide on Windows. Specifically, the is_path_owned_by_current_user function checks token membership rather than confirming actual directory ownership, leading to a trust bypass. This allows repository configurations or hooks owned by a limited user to execute with administrator privileges if an administrator runs a dependent program with an unfiltered elevated token. The flaw does not affect unelevated UAC processes or cloning operations. The issue is resolved in gitoxide version 0.13.3.

An attacker with access to a repository controlled by a limited user can cause repository configuration or hooks to execute commands with administrator privileges if an administrator runs a dependent program with an unfiltered elevated token on Windows. This can lead to privilege escalation with high confidentiality and integrity impact and low availability impact. The vulnerability requires specific conditions including Windows OS, elevated administrator token, and interaction with a repository owned by another user.

This vulnerability is fixed in gitoxide version 0.13.3. Users should upgrade to version 0.13.3 or later to remediate this issue. No additional mitigations are indicated by the vendor advisory.