Libarchive through 3.6.2 can cause directories to have world-writable permissions. The umask() call inside archive_write_disk_posix.c changes the umask of the whole process for a very short period of time; a race condition with another thread can lead to a permanent umask 0 setting. Such a race condition could lead to implicit directory creation with permissions 0777 (without the sticky bit), which means that any low-privileged local user can delete and rename files inside those directories.
References
Link | Resource |
---|---|
https://github.com/libarchive/libarchive/issues/1876 | Issue Tracking |
https://groups.google.com/g/libarchive-announce | Release Notes |
https://github.com/libarchive/libarchive/issues/1876 | Issue Tracking |
https://groups.google.com/g/libarchive-announce | Release Notes |
Configurations
History
No history.
Information
Published : 2023-05-29 20:15
Updated : 2025-01-14 17:15
NVD link : CVE-2023-30571
Mitre link : CVE-2023-30571
CVE.ORG link : CVE-2023-30571
JSON object : View
Products Affected
libarchive
- libarchive
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')