Amoffat sh
sh _uid does not drop supplementary groups (incomplete privilege drop)
sh provides Python process launching. Prior to 2.2.4, the _uid option in sh.py performs an incomplete privilege drop on Linux and Unix-like systems. When sh runs from an elevated process and launches a command with _uid set to an unprivileged user, the child changes its UID but can retain the parent process's supplementary groups because the privilege-drop sequence does not fully establish the target user's UID, primary GID, and supplementary groups. The child can therefore retain access to files or resources granted to privileged groups such as root, docker, disk, shadow, or sudo, violating the expected _uid privilege boundary. This issue is fixed in version 2.2.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.2.4
Fixed in 2.2.4
Mitigation
Upgrade sh to 2.2.4 or later.
References
- Vendor advisory github.com/amoffat/sh/security/advisories/GHSA…
- Patch github.com/amoffat/sh/pull/776
- Patch github.com/amoffat/sh/commit/3d855daba91f87a08…
1 more
- Release notes github.com/amoffat/sh/releases/tag/2.2.4
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.