Unsafe at Any Copy: Name Collisions from Mixing Case Sensitivities
summary
Work builds an auditd-based detector and a test suite that drives copy utilities (cp, rsync, tar) and reproduces the Git CVE; experiments on ext4 with per-directory case insensitivity and WSL show silent data loss, metadata overlay, and symlink traversal that writes outside the target directory. A crafted double-collision with rsync copies confidential files out of the target. Proposed defenses include an openat2 flag to reject collisions, a canonicalize syscall, and a filesystem query API.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:20Case Diversity is an actual concern
- 5:39Real-world Implications
- 7:13How to detect collisions?
- 10:29Test Suite to drive utilities
related talks
33mA Deep Dive into A Vulnerability Apple Deems Unexploitable
29mOn the Security of Copying To and From Live Containers
54mSecurity Holes in Git
44mPath Safety in the Trenches
19mCounterexamples in Safe Rust
29mSecuring Container Runtimes -- How Hard Can It Be?
01h 10mHow 10 open source projects manage unsafe code
42mUnderstanding Data Races in the Linux Kernel