-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
feat: add detection rules for CVE-2025-32463 sudo chroot vulnerability #5671
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the sudo execution with -R/--chroot
is a bit iffy but it also shouldn't be that common in general. I am fine to try it as level: medium
rules-emerging-threats/2025/Exploits/CVE-2025-32463/file_event_lnx_exploit_cve_2025_32463.yml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds detection rules for CVE-2025-32463, a local privilege escalation vulnerability in sudo versions 1.9.14 to 1.9.17 that allows loading arbitrary shared libraries from user-controlled directories during chroot operations.
- Adds process creation detection for sudo commands using --chroot or -R options
- Adds file event detection for nsswitch.conf creation in non-standard directories
- Provides detection coverage for two different attack vectors of the same CVE
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
proc_creation_lnx_exploit_cve_2025_32463.yml | Detects sudo commands with chroot options that could indicate exploitation attempts |
file_event_lnx_exploit_cve_2025_32463.yml | Detects creation of nsswitch.conf files in non-standard locations |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
...s-emerging-threats/2025/Exploits/CVE-2025-32463/proc_creation_lnx_exploit_cve_2025_32463.yml
Outdated
Show resolved
Hide resolved
rules-emerging-threats/2025/Exploits/CVE-2025-32463/file_event_lnx_exploit_cve_2025_32463.yml
Outdated
Show resolved
Hide resolved
...s-emerging-threats/2025/Exploits/CVE-2025-32463/proc_creation_lnx_exploit_cve_2025_32463.yml
Show resolved
Hide resolved
maybe it could be a general rule --chroot execution with user-writeable paths like '/tmp' et. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: phantinuss <79651203+phantinuss@users.noreply.github.com>
only really necessary if that results in a rule of |
Summary of the Pull Request
Changelog
new: Non-Standard Nsswitch.Conf Creation - Potential CVE-2025-32463 Exploitation
new: Potential Sudo Chroot CVE-2025-32463 Vulnerability Exploitation
Example Log Event
Fixed Issues
SigmaHQ Rule Creation Conventions