1-minute read
What a defender needs to know
A file excluded by name on a macOS build machine can still enter the resulting archive or upload. CERT/CC’s coordinated note links Unicode pathname collisions to setuptools source distributions, HashiCorp go-slug Terraform uploads, Deno permission rules and libarchive extraction. APFS can resolve two Unicode spellings to one file while a tool’s raw-byte security comparison treats them as different names. The result can be packaged sensitive files or an overwrite within the extraction process’s write permissions; the path must be introduced through local files or material consumed by the job.
Check the versions and the output. Setuptools fixes its MANIFEST.in exclusion bypass in 83.0.0; its exclude, global-exclude, recursive-exclude and prune rules are in scope. HashiCorp go-slug advises evaluating risk and upgrading to v0.18.3 after affected 0.4.0 through 0.18.2. Deno fixes the macOS path comparison behind --deny-read, --deny-write, --deny-run and --deny-ffi in 2.7.14.
On the actual macOS job, compare the generated archive or upload listing with intended exclusions, accounting for filename variants the volume resolves together. Use a disposable test project with a covered variant and confirm that the excluded member is absent from the finished artifact. Limit libarchive extraction to a directory with the write permissions it needs, and check the extracted tree before promoting it into a build.