You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+45-15Lines changed: 45 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,25 +13,17 @@ The original post about GoExec v0.1.0 can be found [here](https://www.falconops.
13
13
To build this project from source, you will need Go version 1.23.* or greater and a 64-bit target architecture. More information on managing Go installations can be found [here](https://go.dev/doc/manage-install)
14
14
15
15
```shell
16
-
# Install goexec
17
-
CGO_ENABLED=0 go install -ldflags="-s -w" github.com/FalconOpsLLC/goexec@latest
16
+
# Install goexec (release)
17
+
go install -ldflags="-s -w"-trimpath "github.com/FalconOpsLLC/goexec@latest"
18
18
```
19
19
20
20
#### Manual Installation
21
21
22
22
For pre-release features, fetch the latest commit and build manually.
23
23
24
24
```shell
25
-
# (Linux) Install GoExec manually from source
26
-
# Fetch source
27
-
git clone https://github.com/FalconOpsLLC/goexec
28
-
cd goexec
29
-
30
-
# Build goexec (Go >= 1.23)
31
-
CGO_ENABLED=0 go build -ldflags="-s -w"
32
-
33
-
# (Optional) Install goexec to /usr/local/bin/goexec
34
-
sudo install goexec /usr/local/bin
25
+
# Install goexec (development)
26
+
go install -ldflags="-s -w" -trimpath "github.com/FalconOpsLLC/goexec@main"
35
27
```
36
28
37
29
### Install with Docker
@@ -44,8 +36,8 @@ We've provided a Dockerfile to build and run GoExec within Docker containers.
44
36
git clone https://github.com/FalconOpsLLC/goexec
45
37
cd goexec
46
38
47
-
# Build goexec image (as root/docker group)
48
-
docker build . --tag goexec --network host
39
+
# Build goexec image; Must be root or docker group member.
-[Lateral Movement via DCOM: Round 2](https://enigma0x3.net/2017/01/23/lateral-movement-via-dcom-round-2/) - [Matt Nelson](https://github.com/enigma0x3)
The `shellbrowserwindow` method uses the exposed [ShellBrowserWindow](https://strontic.github.io/xcyclopedia/library/clsid_c08afd90-f2a1-11d1-8455-00a0c91f3880.html) DCOM object to call `Document.Application.ShellExecute` and spawn the provided process. The potential constraints of this method are similar to the [ShellWindows method](#shellwindows-method-dcom-shellwindows).
-[Lateral Movement via DCOM: Round 2](https://enigma0x3.net/2017/01/23/lateral-movement-via-dcom-round-2/) - [Matt Nelson](https://github.com/enigma0x3)
The `htafile` method uses the exposed HTML Application object to call [`IPersistMoniker.Load`](https://learn.microsoft.com/en-us/previous-versions/aa458529(v=msdn.10)) with a client-supplied [URL moniker](https://learn.microsoft.com/en-us/openspecs/office_file_formats/ms-oshared/4948a119-c4e4-46b6-9609-0525118552e8). The URL can point to a URL of any format supported by `mshta.exe`.
The `tsch` module makes use of the Windows Task Scheduler service ([MS-TSCH](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-tsch/)) to spawn processes on the remote target.
0 commit comments