-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rules for sudo CVE-2021-3156 #1540
Labels
Comments
Wdyt @Kaizhe ? |
Great and timely idea, Lore! Just one thought: would it make sense to restrict this rule by also checking the arguments? IMHO, it could. I mean, to my understanding, the CVE exists in case a command-line argument to sudoedit -s '\' `perl -e 'print "A" x 65536'` |
@fntlnz thanks starting it. And sorry to replying late in the thread. We will make a PR. |
poiana
pushed a commit
that referenced
this issue
Feb 17, 2021
See #1540 Signed-off-by: darryk5 <stefano.chierici@sysdig.com> Co-authored-by: Lorenzo Fontana <lo@linux.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
Yesterday CVE-2021-3156 was disclosed against
sudo
. I believe that the Falco community should provide a rule against this threat.Feature
Create a specific rule to catch usage of
sudoedit
from a non-root user.I know that you usually use those from a non-root user but I also notice that their usage is usually very limited in a system and specifically since this vulnerability exists we should probably always alert when that is done.
The rule here could look something like this:
Alternatives
Don't do anything.
Additional context
RedHat did something similar with stap by proposing that as a mitigation.
The text was updated successfully, but these errors were encountered: