57
Critical Git vulnerability allows RCE when cloning repositories with submodules (CVE-2024-32002)
(www.helpnetsecurity.com)
this post was submitted on 17 May 2024
57 points (100.0% liked)
Cybersecurity
5648 readers
200 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nice, came here to dunk on submodules, and find there's no need.
Yeah. I wanted to like submodules, but submodules, to me, ended up feeling like one feature too many in
git.I mainly run into submodules that have been setup accidentally by cloning inside an existing clone. That situation is, of course, not great.
Even for the many reasonable use cases for submodules, I generally end up letting my actual package manager do the work, instead. I'm generally happier for it, since life tends to be simpler when my package manager of choice knows about any required libraries.
Agreed. Haven't yet found a use case that isn't better handled by either build tools or "don't do that"