fortra / fortra/No-Consolation

Doesn't work with Go binaries

Open
#6 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
702
Forks
89
PR merge metrics
No merged PRs in 30d

Description

Hi, I'm attempting to use No-Consolation with Go binaries. Unfortunately, any attempt to run them is causing my beacons to crash.

For the purpose of this issue, I compiled a Windows Go binary with the following code:

```
package main

import (
"fmt"
)

func main() {
fmt.Println("Test")
}
```

Upon executing the binary with No-Consolation, my beacon calls back and then crashes.

```
[10/16 21:13:12] beacon> noconsolation /files/go-example.exe
[10/16 21:13:57] [+] host called home, sent: 2056363 bytes
```

Other C/C++ binaries work totally fine for me.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the crash with the provided Windows Go example and the `noconsolation /files/go-example.exe` command, then compare its behavior with a working C or C++ binary. Investigate the binary-loading path responsible for the beacon crash; done means the Go binary runs successfully without crashing the beacon.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, go
Domain
reverse-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.