search

mitre / caldera

Automated Adversary Emulation Platform
https://caldera.mitre.org
Apache License 2.0
5.67k stars 1.08k forks source link

Issue with login loop on AWS Ubuntu 22.04 #3053

Open noob2020-alt opened 2 months ago

noob2020-alt commented 2 months ago

Describe the bug Caldera on Ubuntu Server 22.04 via AWS EC2 instance has the following issues: Does not load plugins Auto logs in upon setup (python3 server.py --insecure --build) Switches loops back to login page automatically Clicking tabs do not work

To Reproduce Steps to reproduce the behavior:

  1. Installed both the master and the 5.0.0 and only the 5.0.0 works.
  2. I changed the following files:

plugin/magma/.env -- I changed the IP address to the EC2 private IP EX: VITE_CALDERA_URL=http://AWS-Private-IP:8888

conf/default.yml host: AWS-Private-IP

Ran the command:

python3 server.py --insecure --build

I received no start up errors:

image

I was automatically logged in without having to enter user pass and no plugins were listed:

image

After about a minute or so, Caldera automatically goes to the login page without clicking anything:

image

When I try to login I get an error under the user | pass input fields "TypeError: n.response is undefined"

Then Caldera logs in and nothing works still.

Clicking any tab on the left has no affect:

image

Expected behavior I expected to log in and set up agents as I have done on Ubuntu 22.04 server running in ESXi. When I click on any tab I should get the following:

image

Desktop (please complete the following information):

Additional context I have tried several configurations:

I have tried using the master and 5.0.0 builds, with partial success in the 5.0.0 build. NodeJS is installed All dependencies, based on the ESXi vm version I tested are installed NOTE: I was able to successfully run all the commands on ESXI vm and get Caldera fully functioning including sending multiple simulations.

Running the same commands in AWS Ubuntu server left me with the issues above.

Thank you for your help.

uruwhy commented 1 month ago

Can you confirm your NodeJS version? And what do you mean by "partial success in the 5.0.0 build"?

You can also try pulling from master to see if this fixes the problem

jasonmull commented 1 month ago

I'm having the exact same issue in AWS. NodeJS version is v12.22.9. Same behavior with Docker as well.

uruwhy commented 1 month ago

Try updating your NodeJS version to 16+ and then rebuild the server using python3 server.py --build