You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
uv is found in the working directory through an empty or relative PATH entry #72
findOnPath resolves every PATH entry with Path(it, name), so an empty entry (a leading/trailing : or ::, e.g. PATH=/usr/bin:) or . resolves to the JVM working directory — a uv executable planted there (e.g. among an agent's generated files) is then run as the installer of every dependency.
Reproduction: PATH=/usr/bin:, an executable ./uv in the JVM working directory, run a script with # /// script dependencies — the planted ./uv runs.
Possible fix: skip empty and relative PATH entries (as shells do not do, but ProcessBuilder-based lookups should for a security-sensitive tool), resolving only absolute directories.
The same threat as #24 and #45 (files in the working directory steering the installer), found during the review of the fix for #45 — pre-existing on main.
Activity
Skip empty and relative PATH entries when looking for uv (#72)
Look for uv only as a regular file, and only as uv.exe on Windows (#72)