This article is more than 1 year old
Proof of concept code published for latest Saltstack CVE: Don't be an update laggard
Any user could become root, warns Immersive Labs researcher
Proof of concept code has been published for a vulnerability in popular data centre security management tool Saltstack, which was discovered after a developer at Immersive Labs found a privilege escalation bug allowing any old user to become root.
SaltStack offers open-source, Python-based automation tools and was acquired by VMware in October last year.
The latest CVE is a command injection flaw leading to the priv-esc flaw, according to Immersive Labs, whose Matt Rollings found the vuln.
Numbered CVE-2020-28243, the bug has a CVSSv3.0 rating of 7.0. Not only does it affect all versions of Salt between 2016.3.0rc2 and 3002.2, but it also “could be performed from within a container to gain command execution as root on the host machine,” as Rollings warned.
More Salt in their wounds: DigiCert hit as hackers wriggle through (patched) holes in buggy config toolREAD MORE
“This allowed any local user to escalate their privileges to root, provided they were able to create files on the minion in a directory that was not explicitly forbidden,” wrote Rollings in a blog post with his findings.
Salt runs through a master-minion setup. Minions receive and execute commands from the master Salt device, which is a server that issues commands to the minions connected to it.
Minions occasionally summon a process called restartcheck. Crafted process names could be fed to restartcheck. This can be done “when the process has open file descriptors associated with (deleted) at the end of a filename” as Rollings warned, adding: “Note, the leading space is required for the injection to function.”
The Salt Project itself patched the vuln in February, at the time warning: “In the recent past, we have gone above and beyond our lifecycle policy in good faith to fix critical issues in versions no longer supported. Going forward, this will be the exception and not standard practice.”
Proof of concept code for the exploit has also been published on Github, meaning orgs using Saltstack really should update it immediately if they haven’t already done so. ®