LiteSpeed has patched a critical privilege-escalation flaw in its Enterprise web server that could let a low-privilege hosting account gain root access on a shared server, but neither LiteSpeed nor cPanel has assigned the vulnerability a CVE or said whether it has been exploited.
cPanel, whose control panel software runs on many of the shared servers where LiteSpeed is deployed, said in a Sept. 14 advisory that it had received notice of the flaw.
An attacker with a low-privilege website account could potentially escape the account’s restricted environment and gain root-level access, it said, bypassing account isolation controls including CloudLinux’s CageFS, which walls off each hosting account’s filesystem from the others.
From there, cPanel said, an attacker could access or alter other hosted sites and the server itself. The advisory named affected versions as LiteSpeed Web Server Enterprise before 6.3.7 and told administrators to upgrade, but gave no CVE, no severity score, and no indication of whether the flaw has been used in attacks.
Tracing the fix through the changelog
LiteSpeed released 6.3.7 on Sept. 11, three days ahead of the advisory, and pushed the same security fixes into a 6.4.0 release candidate on Sept. 14. Patching both branches before disclosure is what a coordinated fix looks like.
The entries are enhanced lscgid request authentication and validation, stronger validation of internal redirect URLs, and blocking the setting of internal-use environment variables from .htaccess. None is tied to the vulnerability.
Nor is the connection made anywhere else. LiteSpeed’s announcement of the release candidate went out the same day as the advisory and mentions neither a vulnerability nor cPanel’s warning.
One can be ruled out, however. The .htaccess restriction already shipped in 6.3.6 build 8 on Aug. 17, leaving two changes new in 6.3.7. lscgid is LiteSpeed’s setuid CGI daemon (the component a privilege-escalation attack would need to reach).
LiteSpeed’s documentation says new releases normally wait a week or two before being pushed to auto-update. On Sept. 15 its download page still listed 6.3.6 as the stable release, with 6.3.7 available separately.
Administrators can force the fixed version from the command line rather than wait. LiteSpeed notes that forcing a version stops the installation following the Stable Tier (LiteSpeed’s automatic update tier), so a scheduled update job will do nothing until an administrator restores the marker by hand.