Find, fix and prevent vulnerabilities in your code.

Overview

Affected versions of this package are vulnerable to Infinite loop where an attacker can cause the application to stop responding by initiating a loop through functions affecting the Path module, such as joinpath, the overloaded division operator, and iterdir.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

• High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

• Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade zipp to version 3.19.1 or higher.

References

• GitHub Commit
• GitHub Issue
• GitHub PR

Overview

Affected versions of this package are vulnerable to Symlink Attack via a race condition in the _acquire method. An attacker can cause lock operations to fail or behave unexpectedly by creating a symlink at the lock file path between the permission check and file creation.

Remediation

Upgrade filelock to version 3.20.3 or higher.

References

• GitHub Commit
• GitHub Commit
• GitHub PR

Overview

Affected versions of this package are vulnerable to Time-of-check Time-of-use (TOCTOU) Race Condition during lock file creation. An attacker can corrupt or truncate arbitrary files by exploiting a race condition between the existence check and file opening with O_TRUNC, allowing the creation of a symlink that is followed and results in the target file being truncated.

Note:

This is only exploitable if the attacker has local filesystem access and the ability to create symlinks in the lock file directory.

Workaround

This vulnerability can be mitigated by using SoftFileLock instead of UnixFileLock/WindowsFileLock, ensuring lock file directories have restrictive permissions (chmod 0700), and monitoring lock file directories for suspicious symlinks before running trusted applications.

Remediation

Upgrade filelock to version 3.20.1 or higher.

References

• GitHub Commit