View Issue Details

IDProjectCategoryView StatusLast Update
0008261Kali LinuxGeneral Bugpublic2023-04-17 14:18
ReporterRemoteLoginCracker Assigned Tosbrun  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2023.1 
Fixed in Version2023.2 
Summary0008261: PowerShell Empire isn't run as root when run from the graphical tools menu
Description

PowerShell Empire is not run as root or require authentication to run when clicked on from the graphical tools menu. However, PowerShell Empire requires root privileges to run, even to print the help description, which is the default behavior when it is started from the graphical tools menu. When PowerShell Empire is run from the graphical tools menu, instead of printing the help description, it exits with an error of "Error: /usr/bin/powershell-empire must be run as root." For PowerShell Empire to be run correctly, it should require root privileges to run like other tools such as Social Engineering Toolkit and should have "(root)" next to its name to indicate its root privilege requirements.

Steps To Reproduce
  1. Open the tools menu by clicking on the Kali icon in the top menu bar.
  2. Hover your mouse over Post Exploitation.
  3. Click on PowerShell Empire.
Attached Files
Kali Linux bug.jpg (24,534 bytes)   
Kali Linux bug.jpg (24,534 bytes)   

Activities

RemoteLoginCracker

RemoteLoginCracker

2023-04-13 11:50

reporter   ~0017799

I did not mean to set the severity to "crash!" This bug most definitely does NOT cause Kali Linux to crash. I clicked the wrong item and didn't notice it until after the report was submitted.

sbrun

sbrun

2023-04-17 14:18

manager   ~0017809

Fixed in kali-menu version 2023.2.0

Issue History

Date Modified Username Field Change
2023-04-13 11:47 RemoteLoginCracker New Issue
2023-04-13 11:47 RemoteLoginCracker File Added: Kali Linux bug.jpg
2023-04-13 11:50 RemoteLoginCracker Note Added: 0017799
2023-04-17 14:01 sbrun Assigned To => sbrun
2023-04-17 14:01 sbrun Status new => assigned
2023-04-17 14:01 sbrun Severity crash => minor
2023-04-17 14:18 sbrun Status assigned => resolved
2023-04-17 14:18 sbrun Resolution open => fixed
2023-04-17 14:18 sbrun Fixed in Version => 2023.2
2023-04-17 14:18 sbrun Note Added: 0017809