ait-testbed / ait-testbed/attackmate-api-server

am_instance gets empty config

Offen
#5 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
0
Forks
1
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

In attackmate_api_server/routers/playbooks.py:

```async def execute_playbook_from_yaml(
...
playbook = Playbook.model_validate(playbook_dict)
logger.info(f'Creating transient AttackMate instance, ID: {instance_id}')
am_instance = AttackMate(playbook=playbook, config=attackmate_config, varstore=None)
```

attackmate_config is empty, and msfrpcd connection does not work because of it.

I inserted this before am_instance:

```
if state.attackmate_config is None:
raise HTTPException(status_code=500, detail="AttackMate configuration is not loaded.")
```

and got the 500 upon trying.

Also,

`am_instance = AttackMate(playbook=playbook, config=attackmate_config, varstore=None)`

does not work, which I changed to:

`am_instance = AttackMate(playbook=playbook, config=attackmate_config, varstore=None, is_api_instance=True)`

for testing, which works. Otherwise the attackmate-client can't connect to the remote-api.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.