BC-SECURITY / Empire

Empire is a post-exploitation and adversary emulation framework that is used to aid Red Teams and Penetration Testers.
https://bc-security.gitbook.io/empire-wiki/
BSD 3-Clause "New" or "Revised" License
4.21k stars 575 forks source link

[BUG] ERROR: Error processing command: Invalid isoformat string: #728

Open masmsec opened 4 months ago

masmsec commented 4 months ago

Is there an existing issue for this?

Empire Version

5.10.2

Python Version

3.10.13

Operating System

Debian

Database

MySQL

Current Behavior

(Empire) > agents ERROR: Error processing command: Invalid isoformat string: '2024-05-07T09:54:57Z' (Empire) > agents ERROR: Error processing command: Invalid isoformat string: '2024-05-07T09:58:08Z' (Empire) > modules (Empire) > agents ERROR: Error processing command: Invalid isoformat string: '2024-05-07T09:59:11Z' (Empire) > listeners ERROR: Error processing command: Invalid isoformat string: '2024-05-07T09:13:16Z' (Empire) >

Expected Behavior

It is suppose to show the agents, listeners when ever I type .

Steps To Reproduce

Before I started the Listener, When I type Listener command, it shows the listener table. If I start a listener, It no longer shows the table giving me the below error. (Empire) > listeners ERROR: Error processing command: Invalid isoformat string: '2024-05-07T09:13:16Z'

This same thing happens when I type agents. When there is no agent, it displays the table but when an agent connets, It displays the below. (Empire) > agents ERROR: Error processing command: Invalid isoformat string: '2024-05-07T09:59:11Z'

Anything else?

error_empire

Cx01N commented 4 months ago

Can you try a few things please:

  1. Does a server reset with `--reset`` make a difference?
  2. Can you try running with Python 3.12 and see if that gets rid of the error?
masmsec commented 4 months ago

Does a server reset with `--reset`` make a difference? This did not work .

Can you try running with Python 3.12 and see if that gets rid of the error? I started with Python 3.12 then downgraded to 3.10

I think the error has to do with date/time formatting. This only happens when an agent comes it and possibly, unable to process the time.

I have been using the web version instead of console .