filelock vulnerabilities (PyPI)
20 vulnerabilities.
-
filelockPyPI filelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live hold 5.3 Medium -
filelockPyPI filelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACL 5.3 Medium -
filelockPyPI filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses 5.8 Medium -
filelockPyPI filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database 3.3 Low -
filelockPyPI filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale break 2.5 Low -
filelockPyPI filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock 3.3 Low -
filelockPyPI filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files 7.1 High -
filelockPyPI filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker 4.7 Medium -
filelockPyPI filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name 6.1 Medium -
filelockPyPI filelock: ReadWriteLock follows a symlink at the lock path into SQLite 6.1 Medium -
filelockPyPI filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders 4.7 Medium -
filelockPyPI filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record 6.1 Medium -
filelockPyPI filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout 5.5 Medium -
filelockPyPI filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory 5.3 Medium -
filelockPyPI filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker 2.5 Low -
filelockPyPI filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion 6.3 Medium -
filelockPyPI filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path 6.1 Medium -
filelockPyPI filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse 4.7 Medium -
filelockPyPI filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock 5.3 Medium -
filelockPyPI filelock has TOCTOU race condition that allows symlink attacks during lock file creation 6.3 Medium