Skip to content

The classifier judged this item not relevant to AI security, so it is left out of lists, feeds, the API and dataset releases. If that is wrong, report a correction on this page.

MediumVulnerability

GHSA-m462-7rxw-wvpg: filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses

Published
Record updated
Affected
  • filelock >= 3.30.0, <= 4.2.0
Fixed in
4.2.1
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.

Summary

filelock versions 3.30.0 through 4.2.0 have a symbolic link following flaw in StrictSoftFileLock and AsyncStrictSoftFileLock. A local user who can rename the `<path>.filelock` directory can swap in a symbolic link after the lstat check, so that claims directories and claim files are created in a directory that user chooses, with the lock user's privileges. Pointed at another strict lock's directory, the stranded claims can deny that lock to every process until an operator force-breaks them.

Mitigation

The source does not state a fix yet. Check the original advisory for updates.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

  • filelockPyPINo LLM dependency detected · 42 tracked dependents