Impact
Vulnerability Type: Local Privilege Escalation (LPE) / Arbitrary Code Execution.
The application loads custom Python rules and configuration files from user-writable locations (e.g., ~/.config/theshit/) without validating ownership or permissions when executed with elevated privileges.
If the tool is invoked with sudo or otherwise runs with an effective UID of root, it continues to trust configuration files originating from the unprivileged user's environment. This allows a local attacker to inject arbitrary Python code via a malicious rule or configuration file, which is then executed with root privileges.
Who is impacted:
Any system where this tool is executed with elevated privileges is affected. In environments where the tool is permitted to run via sudo without a password (NOPASSWD), a local unprivileged user can escalate privileges to root without additional interaction.
Patches
The issue has been fixed in version 0.1.1.
The patch introduces strict ownership and permission checks for all configuration files and custom rules. The application now enforces that rules are only loaded if they are owned by the effective user executing the tool.
When executed with elevated privileges (EUID=0), the application refuses to load any files that are not owned by root or that are writable by non-root users. When executed as a non-root user, it similarly refuses to load rules owned by other users. This prevents both vertical and horizontal privilege escalation via execution of untrusted code.
Workarounds
If upgrading is not possible, users should avoid executing the pplication with sudo or as the root user.
As a temporary mitigation, ensure that directories containing custom rules and configuration files are owned by root and are not writable by non-root users. Administrators may also audit existing custom rules before running the tool with elevated privileges.
References
- Commit fixing the issue
- CWE-269: Improper Privilege Management
- CWE-284: Improper Access Control
- CWE-829: Inclusion of Functionality from Untrusted Control Sphere
AsfhtgkDavid Remediation developer
Impact
Vulnerability Type: Local Privilege Escalation (LPE) / Arbitrary Code Execution.
The application loads custom Python rules and configuration files from user-writable locations (e.g.,
~/.config/theshit/) without validating ownership or permissions when executed with elevated privileges.If the tool is invoked with
sudoor otherwise runs with an effective UID of root, it continues to trust configuration files originating from the unprivileged user's environment. This allows a local attacker to inject arbitrary Python code via a malicious rule or configuration file, which is then executed with root privileges.Who is impacted:
Any system where this tool is executed with elevated privileges is affected. In environments where the tool is permitted to run via
sudowithout a password (NOPASSWD), a local unprivileged user can escalate privileges to root without additional interaction.Patches
The issue has been fixed in version 0.1.1.
The patch introduces strict ownership and permission checks for all configuration files and custom rules. The application now enforces that rules are only loaded if they are owned by the effective user executing the tool.
When executed with elevated privileges (
EUID=0), the application refuses to load any files that are not owned by root or that are writable by non-root users. When executed as a non-root user, it similarly refuses to load rules owned by other users. This prevents both vertical and horizontal privilege escalation via execution of untrusted code.Workarounds
If upgrading is not possible, users should avoid executing the pplication with
sudoor as the root user.As a temporary mitigation, ensure that directories containing custom rules and configuration files are owned by root and are not writable by non-root users. Administrators may also audit existing custom rules before running the tool with elevated privileges.
References