7.1 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Local (L)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Local (L)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): None (N)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
ntfs3: reject direct userspace writes to reserved $LX* xattrs
In the Linux kernel, the following vulnerability has been resolved: ntfs3: reject direct userspace writes to reserved $LX* xattrs NTFS3 uses $LXUID, $LXGID, $LXMOD and $LXDEV as internal WSL permission metadata and reloads them into i_uid, i_gid and i_mode from ntfs_get_wsl_perm(). Because the empty-prefix xattr handler also lets file owners call setxattr() on these names directly, an unprivileged writer on a writable ntfs3 mount can plant root ownership and S_ISUID on their own file and gain euid 0 after inode reload. Reject direct userspace writes to the reserved $LX* names. Internal ntfs3 metadata updates are unchanged because ntfs_save_wsl_perm() writes them via ntfs_set_ea() directly. [almaz.alexandrovich@paragon-software.com: added an additional check for non privileged users]
References
Affected products
- <e574af95234afc3c725988bbc1fdeb46b9f386a4
- <5e658b9245a52d838ef93729a7bc07de8e19deb7
- =<6.18.*
- <5b08dccecf825cbf905f348bc6ccb497507e28e2
- <5.15
- =<5.15.*
- =<6.12.*
- <2c3cd6da4a14380ef79e34bd9dff7caf46687477
- =<7.1.*
- ==5.15
- =<6.1.*
- =<6.6.*
- =<*
- <f8d420949b335a4b51d06ab276beee6b8dfdc909
- <293a84fa40b3a1b3471c0545722724bc10973f76
- <e8852ae29868e449fdb47eebc28f35fb80741a5f