A vulnerability in the filelock library's ReadWriteLock and AsyncReadWriteLock components allows a local user with write access to the lock database file path to cause every acquire operation to stall or hang indefinitely, ignoring timeout and blocking settings. This is achieved by placing a crafted SQLite database file at the lock path, which causes the lock acquisition to consume excessive CPU or memory resources, resulting in denial of service. The issue affects filelock versions 3.20.4 through 4.2.0 and has no impact on confidentiality or integrity, only availability.
A symlink swap vulnerability in filelock's SoftFileLock writability check allows a local user to leak one bit of information about whether a path exists and is writable by the lock user. This occurs due to a time-of-check to time-of-use (TOCTOU) race condition involving os.lstat and os.access calls that handle symlinks differently. The vulnerability affects filelock versions 3.32.6 through 4.2.0 and requires the attacker to have write access to the lock directory and the ability to observe the lock user's acquire outcome. Linux kernel setting fs.protected_symlinks mitigates this in typical sticky world-writable directories like /tmp, but not in others. The issue is rated low severity with a CVSS score of 2.5.
A vulnerability in filelock versions 4.1.0 through 4.2.0 allows a local unprivileged user to evict a lock file held by another user by exploiting inode reuse and coarse clock timestamp manipulation on ext4 or overlayfs filesystems. This causes two processes of the lock owner to enter a critical section simultaneously, violating lock integrity without affecting confidentiality or availability. The attack requires specific timing conditions and filesystem behavior, making it a high complexity local attack with medium severity.
On Windows, certain soft file lock implementations in filelock versions 3.22.0 through 4.2.0 can be blocked indefinitely by another local user holding an oplock on the lock marker file. This occurs when a stale marker file is left unclosed and another account with read access requests a Level 1 oplock and does not respond to break notifications. The lock acquire attempts then wait past their timeout, causing partial availability impact without compromising confidentiality or integrity.
A vulnerability in filelock versions >=3.30.0 and <=4.2.0 allows a local user with write access to a shared directory to swap a symbolic link in place of the lock coordination directory during a narrow timing window. This causes the lock user's process to create claim files in a directory chosen by the attacker, potentially disrupting other locks by causing them to time out until manually force-broken. The issue requires the ability to rename the <path>.filelock directory and affects environments without sticky bit protections or where the attacker created the lock directory first in sticky directories. The vulnerability has medium severity with a CVSS score of 5.8.
A command injection vulnerability exists in GitPython's Remote.pull() method used by the opentimestamps-client. The method improperly forwards a positional refspec argument directly to the git pull command without properly filtering unsafe options like --upload-pack. An attacker controlling the refspec can inject arbitrary commands executed with the privileges of the calling process when using local-path or SSH transports. This vulnerability is fixed in opentimestamps-client version 0.7.2_8.