skillctl
Affected
- introduced
0, fixed0.1.2(semver)
Fixed versions
0.1.2
Fix
- Fixed version
0.1.2cargo update -p skillctl --precise 0.1.2
Advisory
Also known as: None
skillctl: Path traversal and symlink-follow in skillctl allow arbitrary file disclosure and deletion
Impact
skillctl 0.1.0 and 0.1.1 contained four path-safety vulnerabilities that, in combination, allowed an attacker to:
niania → /home/user/.aws/credentials). The symlink fell through entry.file_type().is_dir() in fs_util::copy_dir_all, was dereferenced by fs::copy, and the target's content was copied into the project. A subsequent skillctl push would have published the secret to the (possibly public) library — what the reporter called "round-trip path exfiltration"..skills.toml with a malicious destination or source_path field. Both were deserialized as PathBuf with zero validation. Because Path::join lets an absolute right-hand side replace the base, destination = "/home/user/.ssh" made cwd.join(...) resolve outside the project; .. traversal was equally unguarded. Downstream remove_dir_all in replace_folder_contents then wiped arbitrary writable directories on skillctl pull / push / detect. .skills.toml is the exact kind of file teams commit and exchange via PR; a single merged malicious PR was sufficient to weaponise the maintainer's next skillctl pull --all.--target ../../../etc would have written outside the library root... would have produced a Path::join resolving to the parent directory and fs::rename could have clobbered it.Patches
Fixed in v0.1.2:
.skills.toml destination and source_path are validated at load time and reject absolute paths, .. components, and Windows-prefix components.path_safety::safe_join helper is wired (defense-in-depth) at every destructive call site in pull.rs / push.rs.detect --target and the interactive custom-path prompt go through the same validate_relative_subpath helper.validate_fork_name explicitly rejects . and ...Threat-model note: the fix is purely lexical (component-level) plus an explicit symlink check at copy time. No filesystem canonicalize calls were added, avoiding TOCTOU windows.
Credit
Reported privately on 2026-05-19 by firebaguette via the Umanio Discord (the reporter declined GitHub credit, so this advisory carries no structured credits field).
High Basis: The source's own band: HIGH
0, fixed 0.1.2 (semver)0.1.2
0.1.2cargo update -p skillctl --precise 0.1.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0