Tox-dev filelock
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
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a writable adjacent hot journal is additionally required for attacker-chosen content overwrites. This issue is fixed in version 4.2.1.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-363
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
tox-dev filelock
- >= 3.20.4, < 4.2.1
Fixed in 4.2.1
Mitigation
Upgrade filelock to 4.2.1 or later.
References
- Vendor advisory github.com/tox-dev/filelock/security/advisorie…
- Patch github.com/tox-dev/filelock/pull/834
- Patch github.com/tox-dev/filelock/commit/5e3f2ec0c5f…
1 more
- Release notes github.com/tox-dev/filelock/releases/tag/4.2.1
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.