View Issue Details

IDProjectCategoryView StatusLast Update
0008272Kali LinuxGeneral Bugpublic2023-05-08 22:40
ReporterRemoteLoginCracker Assigned Tosteev  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionnot fixable 
Product Version2023.1 
Summary0008272: ShellNoob crashes instantly when run from the Kali Menu
Description

When clicked on from the graphical Kali tools menu, ShellNoob always prints an error and crashes in less than 1 second. After the crash, the terminal window always closes, so I can't provide an exact error message or a screenshot. Before the crash, I did see the text "Traceback (most recent call last)," indicating a Python error. When ShellNoob is run from the terminal, and not from the Kali Menu, it works fine and does not crash, with or without any switches. If ShellNoob is run differently when run from the menu, this is most likely causing the crash.

I have run ShellNoob from the Kali Menu many times, and the result is always the same.

Steps To Reproduce
  1. Open the Kali Menu.
  2. Mouse over "08 - Exploitation Tools."
  3. Click on shellnoob. It will run in the terminal and crash almost instantly, closing the terminal window.
Attached Files

Activities

arnaudr

arnaudr

2023-04-24 04:18

manager   ~0017821

I tried on a up-to-date Kali rolling system, and I can't reproduce the issue. Works for me. I can run it from the menu.

Can you try to run shellnoob -i in a terminal? This is the command that actually runs when you click on the icon in the menu.

Alternatively, just make sure your system is up-to-date (with the usual pair of commands: sudo apt update && sudo apt full-upgrade).

RemoteLoginCracker

RemoteLoginCracker

2023-04-25 01:22

reporter   ~0017826

@arnaudr My system is fully up-to-date, I checked with the pair of commands you posted. I am running a clean installation of Kali Linux. I have ran shellnoob -i in the terminal, and the same error occurs. When run in the terminal via shellnoob -i instead of the menu, however, the terminal window doesn't instantly close, allowing me to screenshot the error. Because I am running Kali Linux in a Virtual Machine, I can't copy-and-paste the error text into this post, but I can provide the screenshot.

ShellNoob Kali Bug.jpg (290,637 bytes)
arnaudr

arnaudr

2023-04-25 05:01

manager   ~0017828

Hey, thanks for the feedback. One possibility, with this kind of error, is that you installed some libraries on your system with pip or another Python tool, as root. Do you remember doing that?

This being said, looking at the code, shellnoob doesn't depend on any python library, so I don't think it's the problem here...

The error message from shellnoob is: « objdump_options not found for the current setup ». So what's special about your setup? You said you run Kali in a VM, so what VM engine is it? Did you set it up using the Kali installer, or did you use a pre-built VM?

Additionally, can you please paste the output of "uname -a" ?

Also, you could try to run with the flag '--64' and/or with the flag '--intel' to see if you get more luck. I', not familiar with shellnoob so I don't know what those flags really do, and if they make sense for what you want to do. But they have an influence of the code that fais, so please give it a try and tell me if that works. Thanks!

RemoteLoginCracker

RemoteLoginCracker

2023-04-28 01:29

reporter   ~0017841

@arnaudr I have not installed any libraries with pip or any other Python tools, as root or as a normal user. I'm using UTM to run Kali Linux, which is based on QEMU. I set it up using the Kali installer from the official website. The installer image I used was from the Apple Silicon (ARM64) tab of https://www.kali.org/get-kali/#kali-installer-images because my host computer is using an Apple Silicon chip. I used the normal installer, not Weekly or NetInstaller. As I said in my previous post, I'm unable to use copy and paste from my Kali Linux VM, so I've typed the output of uname -a below:
Linux kali 6.1.0-kali7-arm64 0000001 SMP Debian 6.1.20-2kali1 (2023-04-18) aarch64 GNU/Linux
Running shellnoob -i with '--64' or '--intel', as well as running it with both of these, causes the same error to occur.

Also, note that « objdump_options not found for the current setup » is not the only error that occurs: ShellNoob also encounters an error while attempting to handle that error and print an error message. The handling error is minor, but it is still a bug.

I've attached a screenshot of some of my UTM VM information below in case it helps you figure more out about my setup.

Kali Linux VM.jpg (192,859 bytes)   
Kali Linux VM.jpg (192,859 bytes)   
steev

steev

2023-04-28 05:34

manager   ~0017845

Last edited: 2023-04-28 05:39

It would appear that shellnoob does not support interactive mode on arm64 (possibly even arm64, if I am reading the source correctly, it only supports arm, but hard to say without looking much closer).

steev

steev

2023-04-28 06:14

manager   ~0017847

I just grabbed one of my RPis with armhf on it (so 32bit ARM), and shellnoob runs just fine there. Unfortunately, it seems that shellnoob just doesn't support arm64. I'll try to find some time tomorrow to look and see if it's just doing something silly like assuming 64bit is intel, but this likely needs to go upstream for them to add arm64 support, and we might have to just drop arm64 from the keywords.

steev

steev

2023-05-08 22:40

manager   ~0017900

Issue submitted upstream at https://github.com/reyammer/shellnoob/issues/11 - this is something out of our control, so we will disable installing shellnoob on arm64 for now.

Issue History

Date Modified Username Field Change
2023-04-21 20:19 RemoteLoginCracker New Issue
2023-04-24 04:18 arnaudr Note Added: 0017821
2023-04-25 01:22 RemoteLoginCracker File Added: ShellNoob Kali Bug.jpg
2023-04-25 01:22 RemoteLoginCracker Note Added: 0017826
2023-04-25 05:01 arnaudr Note Added: 0017828
2023-04-28 01:29 RemoteLoginCracker File Added: Kali Linux VM.jpg
2023-04-28 01:29 RemoteLoginCracker Note Added: 0017841
2023-04-28 05:34 steev Note Added: 0017845
2023-04-28 05:39 steev Note Edited: 0017845
2023-04-28 06:14 steev Note Added: 0017847
2023-05-08 22:40 steev Assigned To => steev
2023-05-08 22:40 steev Status new => closed
2023-05-08 22:40 steev Resolution open => not fixable
2023-05-08 22:40 steev Note Added: 0017900