Security Holes in Git
summary
Specific exploits show how Git lets attackers write into the repository metadata and run code: case-insensitive and Unicode filename tricks let commits create files in the .git area (overwriting object files to poison the object DB), 8.3 and HFS+ normalization allow hidden hooks to appear and execute, and a recursive-clone submodule with a malicious URL or path causes SSH to run arbitrary commands (demonstrated via CVE-2014-9390 and CVE-2018-11235). Tools used in response include Valgrind, Coverity and libgit2 patches.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:37Edward Thomson
- 3:13Top 3 reasons to write an application in C
- 9:24Desktop Usage
- 51:15Protect Yourself: Stay Patched
related talks
28mOn Omitting Commits and Committing Omissions: Preventing Git Metadata...
36mGithub Actions Security Landscape
23mBreaking the Build: How Attackers Abuse GitHub Actions
30mHidden Vulnerabilities in Open Source
01h 02mPrompt-Jacking: The Rise of a New Supply Chain Risk
13mFive Ways to Break a Git Repository
28mUnveiling Remote Code Execution: How Vulnerabilities Lead to System Takeovers
39mWhat Have We Found in Git Repos?
