emp3r0r is a C2 designed by Linux users for Linux environments. Prior to version 3.21.2, multiple shared maps are accessed without consistent synchronization across goroutines. Under concurrent activity, Go runtime can trigger `fatal error: concurrent map read and map write`, causing C2 process crash (availability loss). Version 3.21.2 fixes this issue.

Affected: Go: github.com/jm33-m0/emp3r0r/core

## Summary

Multiple shared maps are accessed without consistent synchronization across goroutines. Under concurrent activity, Go runtime can trigger `fatal error: concurrent map read and map write`, causing C2 process crash (availability loss).

## Vulnerable Component(with code examples)

Operator relay map had mixed access patterns (iteration and mutation without a single lock policy):

```go // vulnerable pattern (operator session map) for sessionID, op := range OPERATORS { // iteration path ... }

// concurrent mutation path elsewhere OPERATORS[operatorSession] = &operator_t{...} delete(OPERATORS, operatorSession) ```

Port-forwarding session map had read/write paths guarded inconsistently:

```go // vulnerable pattern (port forward map) if sess, ok := PortFwds[id]; ok { // read path ... }

PortFwds[id] = newSession // write path delete(PortFwds, id) // delete path ```

FTP stream map similarly mixed concurrent iteration with mutation:

```go // vulnerable pattern (FTP stream map) for token, stream := range FTPStreams { // iteration path ... }

FTPStreams[token] = stream // write path delete(FTPStreams, token) // delete path ```

## Attack Vector

1. Attacker (or stress traffic in authenticated flows) triggers high concurrency in normal control paths. 2. Operator sessions connect/disconnect while message forwarding and file-transfer workflows are active. 3. Concurrent read/write hits shared maps. 4. Go runtime panics with concurrent map read/write erro…