CVE-2025-59961 is a medium-severity vulnerability in Juniper Networks Junos OS and Junos OS Evolved affecting the DHCP daemon (jdhcpd). It allows a local, low-privileged user to write to the Unix socket managing the DHCP service, enabling administrative control over the DHCP server or relay. This flaw arises from incorrect permission assignments on a critical resource, permitting unauthorized command execution without user interaction. The vulnerability impacts multiple Junos OS versions prior to various patch releases starting from 21.2R3-S10 and corresponding Junos OS Evolved versions. Exploitation requires local access but no elevated privileges or user interaction. Although no known exploits are reported in the wild, the ability to control DHCP services can disrupt network operations and potentially facilitate further attacks. European organizations using affected Juniper devices should prioritize patching to mitigate risks.
## Vulnerability Summary
**Title:** Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock
**Affected Component:** `filelock` package - `SoftFileLock` class
**File:** `src/filelock/_soft.py` lines 17-27
**CWE:** CWE-362, CWE-367, CWE-59
---
## Description
A TOCTOU race condition vulnerability exists in the `SoftFileLock` implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly.
The vulnerability occurs in the `_acquire()` method between `raise_on_not_writable_file()` (permission check) and `os.open()` (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service.
### Attack Scenario
```
1. Lock attempts to acquire on /tmp/app.lock
2. Permission validation passes
3. [RACE WINDOW] - Attacker creates: ln -s /tmp/important.txt /tmp/app.lock
4. os.open() tries to create lock file
5. Lock operates on attacker-controlled target file or fails
```
---
## Impact
_What kind of vulnerability is it? Who is impacted?_
This is a **Time-of-Check-Time-of-Use (TOCTOU) race condition vulnerability** affecting any application using `SoftFileLock` for inter-process synchronization.
**Affected Users:**
- Applications using `filelock.SoftFileLock` directly
- Applications using the fallback `FileLock` on systems without `fcntl` support (e.g., GraalPy)
**Consequences:**
- **Silent lock acquisition failure** - applications may not detect that exclusive resource access is not guaranteed
- **Denial of Service** - attacker can prevent lock file creation by maintaining symlink
- **Resource serialization failures** - multiple processes may acquire "locks" simultaneously
- **Unintended file operations** - lock could operate on attacker-controlled files
**CVSS v4.0 Score:** 5.6 (Medium)
**Vector:** CVSS:4.0/AV:L/AT:L/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
**Attack Requirements:**
- Local filesystem access to the directory containing lock files
- Permission to create symlinks (standard for regular unprivileged users on Unix/Linux)
- Ability to time the symlink creation during the narrow race window
---
## Patches
_Has the problem been patched? What versions should users upgrade to?_
Yes, the vulnerability has been patched by adding the `O_NOFOLLOW` flag to prevent symlink following during lock file creation.
**Patched Version:** Next release (commit: 255ed068bc85d1ef406e50a135e1459170dd1bf0)
**Mitigation Details:**
- The `O_NOFOLLOW` flag is added conditionally and gracefully degrades on platforms without support
- On platforms with `O_NOFOLLOW` support (most modern systems): symlink attacks are completely prevented
- On platforms without `O_NOFOLLOW` (e.g., GraalPy): TOCTOU window remains but is documented
**Users should:**
- Upgrade to the patched version when available
- For critical deployments, consider using `UnixFileLock` or `WindowsFileLock` instead of the fallback `SoftFileLock`
---
## Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
For users unable to update immediately:
1. **Avoid `SoftFileLock` in security-sensitive contexts** - use `UnixFileLock` or `WindowsFileLock` when available (these were already patched for CVE-2025-68146)
2. **Restrict filesystem permissions** - prevent untrusted users from creating symlinks in lock file directories:
```bash
chmod 700 /path/to/lock/directory
```
3. **Use process isolation** - isolate untrusted code from lock file paths to prevent symlink creation
4. **Monitor lock operations** - implement application-level checks to verify lock acquisitions are successful before proceeding with critical operations
---
## References
_Are there any links users can visit to find out more?_
- **Similar Vulnerability:** CVE-2025-68146 (TOCTOU vulnerability in UnixFileLock/WindowsFileLock)
- **CWE-362 (Concurrent Execution using Shared Resource):** https://cwe.mitre.org/data/definitions/362.html
- **CWE-367 (Time-of-check Time-of-use Race Condition):** https://cwe.mitre.org/data/definitions/367.html
- **CWE-59 (Improper Link Resolution Before File Access):** https://cwe.mitre.org/data/definitions/59.html
- **O_NOFOLLOW documentation:** https://man7.org/linux/man-pages/man2/open.2.html
- **GitHub Repository:** https://github.com/tox-dev/filelock
---
**Reported by:** George Tsigourakos (@tsigouris007)
CVE-2025-59529 is an uncontrolled resource consumption vulnerability in Avahi versions up to and including 0.9-rc5. The Avahi simple protocol server ignores the documented client limit and accepts unlimited connections, allowing local unprivileged users to exhaust daemon memory and file descriptors. This leads to a denial of service affecting mDNS/DNS-SD resolution system-wide. The vulnerability does not affect resolution requests via DBus or certain Avahi tools using DBus. No official patch is available at the time of publication, but a candidate fix exists in a pull request. Workarounds include changing permissions on the unix socket or applying access restrictions such as SELinux.
filelock is a platform-independent file lock for Python. In versions prior to 3.20.1, a Time-of-Check-Time-of-Use (TOCTOU) race condition allows local attackers to corrupt or truncate arbitrary user files through symlink attacks. The vulnerability exists in both Unix and Windows lock file creation where filelock checks if a file exists before opening it with O_TRUNC. An attacker can create a symlink pointing to a victim file in the time gap between the check and open, causing os.open() to follow the symlink and truncate the target file. All users of filelock on Unix, Linux, macOS, and Windows systems are impacted. The vulnerability cascades to dependent libraries. The attack requires local filesystem access and ability to create symlinks (standard user permissions on Unix; Developer Mode on Windows 10+). Exploitation succeeds within 1-3 attempts when lock file paths are predictable. The issue is fixed in version 3.20.1. If immediate upgrade is not possible, use SoftFileLock instead of UnixFileLock/WindowsFileLock (note: different locking semantics, may not be suitable for all use cases); ensure lock file directories have restrictive permissions (chmod 0700) to prevent untrusted users from creating symlinks; and/or monitor lock file directories for suspicious symlinks before running trusted applications. These workarounds provide only partial mitigation. The race condition remains exploitable. Upgrading to version 3.20.1 is strongly recommended.
CVE-2025-64750 is a medium severity vulnerability in Sylabs Singularity container platforms (SingularityCE and SingularityPRO) prior to versions 4.3.5 and 4.1.11. It involves a symbolic link (symlink) following issue where an attacker can bypass Linux Security Module (LSM) restrictions by redirecting the mount of /proc to a shared mount controlled by the attacker. Exploitation requires the victim to run a malicious container image that mounts /proc to this attacker-controlled location. The attacker must also have control over the shared mount content, either via another malicious container or host permissions. This vulnerability can lead to partial compromise of confidentiality, integrity, and availability of the container environment. No known exploits are reported in the wild.
OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to version 2.4.15, a client that connects to cupsd but sends slow messages, e.g.only one byte per second, delays cupsd as a whole, such that it becomes unusable by other clients. This issue has been patched in version 2.4.15.
OpenPrinting CUPS is an open source printing system for Linux and other Unix-like operating systems. Prior to version 2.4.15, a user in the lpadmin group can use the cups web ui to change the config and insert a malicious line. Then the cupsd process which runs as root will parse the new config and cause an out-of-bound write. This issue has been patched in version 2.4.15.
A null pointer dereference vulnerability exists in the Common UNIX Printing System (CUPS) in the ipp_read_io() function, which can lead to a remote denial of service (DoS). This issue affects Red Hat Enterprise Linux 8 versions prior to 8.10.0. Red Hat has released a security update to address this vulnerability. The severity of this issue is rated as moderate by Red Hat, and no known exploits are reported in the wild.
Open OnDemand is an open-source HPC portal. Prior to versions 4.0.8 and 3.1.16, users can craft a "Time of Check to Time of Use" (TOCTOU) attack when downloading zip files to access files outside of the OOD_ALLOWLIST. This vulnerability impacts sites that use the file browser allowlists in all current versions of OOD. However, files accessed are still protected by the UNIX permissions. Open OnDemand versions 4.0.8 and 3.1.16 have been patched for this vulnerability.
A low severity vulnerability (CVE-2024-56433) in the shadow-utils package for Red Hat Enterprise Linux 9 involves the default subordinate ID configuration in /etc/login.defs, which could lead to system compromise. Shadow-utils provides utilities for managing user and group accounts and converting UNIX password files to shadow format. Red Hat has released an update to address this issue.
A vulnerability in IBM Db2 versions 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX, and Windows allows an authenticated user to cause a denial of service due to improper release of resources after use.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX and Windows (includes Db2 Connect Server) could allow an authenticated user to cause a denial of service due to improper allocation of resources.
IBM Db2 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX and Windows (includes Db2 Connect Server) clpplus command exposes user credentials to the terminal which could be obtained by a third party with physical access to the system.