filelock is vulnerable to Uncontrolled Resource Consumption
25
CVE Score
Low
Uncontrolled Resource Consumption
filelock reads a SoftFileLock lock file in its stale-lock detection and PID inspection paths using a symlink-following, unbounded text read. When a lock becomes stale, a local attacker with write access to the lock directory can replace the lock file with a symlink, a FIFO, or an oversized file. A peer process that then reads the lock follows the symlink to an unintended target, blocks indefinitely on the FIFO, or exhausts memory reading the large file, causing denial of service. The fix opens the lock file with O_NOFOLLOW and O_NONBLOCK and caps the read size so hostile replacements are rejected instead of followed.
Upgrade the filelock library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and your application uses SoftFileLock with a lock directory writable by other local users.
3.22.0 - 3.29.0
Fixed in 3.29.1filelock is vulnerable to Uncontrolled Resource Consumption in versions 3.22.0 - 3.29.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.