Patch Changes
-
#132
bb425beThanks @tufantunc! - Recognise the elevation binaries that 2.2.4 stopped catching, and two it never caught.The fix for GHSA-6f54-mjqq-2jp8 replaced four
^-anchored regexes with exact membership in a set of four names./^\s*su\b/had matched betweensuand a hyphen, sosu-execandsudo-rswere classifiedprivileged— by accident of the regex rather than by intent, but the effect was protective. Exact matching dropped them, and on aprod-group profile that turned adenyinto anallow. A security release narrowed a security control, which is not acceptable however narrow the shape.gosuandrun0were caught by neither the old form nor the new one.su-execandgosuare the standard elevation binaries of Alpine and Docker images;sudo-rsis the Rust implementation now shipping as the default sudo on some distributions;run0is systemd's replacement. A host using any of them had no elevation gate at all, before or after 2.2.4.PRIVILEGE_PREFIXESnow listssu-exec,gosu,sudo-rs,run0andpfexecalongsidesudo,su,doasandpkexec. It stays an explicit list rather than a pattern, because a pattern cannot tellsudoedit— which edits a file and is not elevation — fromsudo-rs, which is sudo. That means it has to be maintained by hand as new implementations appear, and the cost of missing one is that its commands classifysafe.Found by @burtherman's work on #130 — reviewing that branch is what surfaced the
\bbehaviour, and the same gap turned out to be in the advisory fix.