Bug in stdin in windows msfconsole

[Onyz107]

Steps to reproduce

How'd you do it?

1. start msfconsole using cmd or powershell
2. type anything then press on the backspace

Were you following a specific guide/tutorial or reading documentation?

no

Expected behavior

to register the backspace

Current behavior

For example when you type in sessions, press on the backspace it still says sessions in msf6 > sessions but it registers it as if you pressed the backspace

let me elaborate

msf6 > sessions
[-] Unknown command: session. Did you mean sessions? Run the help command for more details.

So what happened here is the I typed in sessions and pressed on the backspace. it did not register the backspace on the stdout but it still knows that I pressed on the backspace if that makes sense.

Metasploit version

Framework: 6.4.30-dev-5e2fab24efb826bc77362ceb0a38a38305d8d90d
Console : 6.4.30-dev-5e2fab24efb826bc77362ceb0a38a38305d8d90d

Additional Information

The following global/module datastore, and database setup was configured before the issue occurred:

Collapse

[framework/core]
loglevel=3

Database Configuration

The database contains the following information:

Collapse

Session Type: postgresql selected, no connection

Framework Configuration

The features are configured as follows:

Collapse

name	enabled
wrapped_tables	true
fully_interactive_shells	false
manager_commands	false
datastore_fallbacks	true
metasploit_payload_warnings	true
defer_module_loads	false
smb_session_type	true
postgresql_session_type	true
mysql_session_type	true
mssql_session_type	true
ldap_session_type	false
show_successful_logins	false
dns	true
hierarchical_search_table	true

History

The following commands were ran during the session and before this issue occurred:

Collapse

10     session
11     version
12     set loglevel 3
13     session
14     debug

Framework Errors

The following framework errors occurred before the issue occurred:

Collapse

[10/10/2024 01:19:58] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 03:40:08] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 03:40:16] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 03:40:25] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 03:42:31] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 03:42:41] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 03:42:51] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 03:43:14] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 03:43:22] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 03:43:31] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported

Web Service Errors

The following web service errors occurred before the issue occurred:

Collapse

msf-ws.log does not exist.

Framework Logs

The following framework logs were recorded before the issue occurred:

Collapse

[10/10/2024 01:09:50] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 01:09:57] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 01:10:04] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 01:10:07] [e(0)] core: Failed to open history file: C:/Users/zaid2/.msf4/history with error: No such file or directory @ rb_sysopen - C:/Users/zaid2/.msf4/history
[10/10/2024 01:12:59] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 01:13:09] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 01:13:21] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 01:19:43] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 01:19:50] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 01:19:58] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 03:40:08] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 03:40:16] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 03:40:25] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 03:42:31] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 03:42:41] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 03:42:51] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[10/10/2024 03:43:14] [e(0)] core: Failed to connect to the database: No database YAML file
[10/10/2024 03:43:22] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[10/10/2024 03:43:31] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported

Web Service Logs

The following web service logs were recorded before the issue occurred:

Collapse

msf-ws.log does not exist.

Version/Install

The versions and install method of your Metasploit setup:

Collapse

Framework: 6.4.30-dev-5e2fab24efb826bc77362ceb0a38a38305d8d90d
Ruby: ruby 3.2.5 (2024-07-26 revision 31d0f1a2e7) [x64-mingw-ucrt]
OpenSSL: OpenSSL 3.3.1 4 Jun 2024
Install Root: D:/metasploit-framework/embedded/framework
Session Type: postgresql selected, no connection
Install Method: Omnibus Installer

[adfoster-r7]

Thanks for raising an issue. As a workaround we recommend using Kali or similar which has Metasploit and other tooling pre-installed, or a non-windows system