filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tox-dev | filelock | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tox-dev | Filelock |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-jqc4-5cvw-7w85 | filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.162% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tox-dev
Tox-dev filelock |
|
| Vendors & Products |
Tox-dev
Tox-dev filelock |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1. | |
| Title | filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name | |
| Weaknesses | CWE-367 | |
| References |
| |
| Metrics |
cvssV3_1
|