zuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directory

Özet

Türkçe özeti henüz hazır değil; şimdilik kaynağın kendi açıklamasını gösteriyoruz.

Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.4.0, @zuke/cli uses lstat to inspect scaffold names but then performs link-following reads, writes, and permission changes in zuke setup and zuke import. An attacker who supplies an untrusted cloned repository, template, or archive with a symbolic link at a scaffolded name can cause setup to overwrite a target outside the selected directory with the invoking user's permissions. The .gitignore path requires no flag, while --force permits a linked launcher target to be written and made executable; import can also read link-target content and incorporate it into the generated build file. This issue is fixed in version 1.4.0.

Etkilenen sürümler1 yazılım

Kaynaklar6 kaynak

• CVE.org kaydı
• NVD kaydı
• github.com/…d/zuke/security/advisories/GHSA-hc8w-3fgv-22pw Diğer
• github.com/zuke-build/zuke/pull/542 Diğer
• github.com/…ommit/4257b0bc5ef5e387a44f913349646d4baccd1654 Diğer
• github.com/zuke-build/zuke/releases/tag/cli-v1.4.0 Diğer

Kayıt geçmişi

1. 30 Eki 2026 18:52Yayımlandı

İlgili açıklar

• 7,5 CVE-2026-119290Zuke: Resolved secret() values are written to GITHUB_STEP_SUMMARY in the clear, disclosing them to anyone who can view the workflow run
• 7,1 CVE-2026-119289Zuke: githubWorkflow adopts any workflow run whose title matches its marker, so anyone who can dispatch the workflow can satisfy or block a release gate
• 7,0 CVE-2026-119288Zuke: Argument injection on Windows: batch shims are launched through cmd.exe, which re-parses the command line
• 8,0 CVE-2026-119287Zuke: Command-form registry descriptors bypass the MCP launch policy
• 6,8 CVE-2026-119704Bastille through 1.4.4 Jail Escape via Symlink Following in cp, rcp, jcp
• 5,3 CVE-2026-119364ProFTPD through 1.3.9e and 1.3.10rc4 mod_copy Symlink Following Write Bypass