Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is_known_pipeline faild #14464

Open
thiago0x00 opened this issue Dec 5, 2020 · 13 comments
Open

is_known_pipeline faild #14464

thiago0x00 opened this issue Dec 5, 2020 · 13 comments
Labels
confirmed Issues confirmed by a committer not-stale Label to stop an issue from being auto closed question Questions about Metasploit Usage

Comments

@thiago0x00
Copy link

Hello!

I'm trying to run is_known_pipeline with msf6 and I got an error:
STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.

When I use msf5 it does not occur. Is this a bug?

@thiago0x00 thiago0x00 added the question Questions about Metasploit Usage label Dec 5, 2020
@bcoles
Copy link
Contributor

bcoles commented Dec 5, 2020

When I use msf5 it does not occur.

Does the module work with msf5? Do you get a session?

@adfoster-r7
Copy link
Contributor

When creating an issue, please ensure that the default issue template has been updated with the required details:

https://raw.githubusercontent.com/rapid7/metasploit-framework/master/.github/ISSUE_TEMPLATE/bug_report.md

@thiago0x00
Copy link
Author

name: Bug Report 🐞
about: msf6 does not work correct with exploit is_known_pipeline and when I run in msf5 works perfect.

  1. Start msfconsole
  2. Run the command set loglevel 3
  3. Take the steps necessary recreate your issue
  4. Run the debug command

Module/Datastore

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

Collapse
[framework/core]
log=level 3

[framework/ui/console]
ActiveModule=exploit/linux/samba/is_known_pipename

[linux/samba/is_known_pipename]
DCERPC::fake_bind_multi=false
SHELL=/bin/sh
WORKSPACE=
VERBOSE=false
WfsDelay=0
EnableContextEncoding=false
ContextInformationFile=
DisablePayloadHandler=false
RHOSTS=192.168.10.131
RPORT=445
SSL=false
SSLVersion=Auto
SSLVerifyMode=PEER
SSLCipher=
Proxies=
CPORT=
CHOST=
ConnectTimeout=10
TCP::max_send_size=0
TCP::send_delay=0
DCERPC::max_frag_size=4096
DCERPC::fake_bind_multi_prepend=0
DCERPC::fake_bind_multi_append=0
DCERPC::smb_pipeio=rw
DCERPC::ReadTimeout=10
NTLM::UseNTLMv2=true
NTLM::UseNTLM2_session=true
NTLM::SendLM=true
NTLM::UseLMKey=false
NTLM::SendNTLM=true
NTLM::SendSPN=true
SMB::pipe_evasion=false
SMB::pipe_write_min_size=1
SMB::pipe_write_max_size=1024
SMB::pipe_read_min_size=1
SMB::pipe_read_max_size=1024
SMB::pad_data_level=0
SMB::pad_file_level=0
SMB::obscure_trans_pipe_level=0
SMBDirect=true
SMBUser=
SMBPass=
SMBDomain=.
SMBName=*SMBSERVER
SMB::VerifySignature=false
SMB::ChunkSize=500
SMB::Native_OS=Windows 2000 2195
SMB::Native_LM=Windows 2000 5.0
SMB::ProtocolVersion=1,2,3
SMB::AlwaysEncrypt=true
SMB_SHARE_NAME=
SMB_FOLDER=
PAYLOAD=cmd/unix/interact

History

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

Collapse
174    set log level 3
175    search is_known
176    use 0
177    set rhost 192.168.10.131
178    exploit
179    debug

Framework Errors

The following framework errors occurred before the issue occurred:

Collapse
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/05/2020 07:58:34] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.
[12/05/2020 17:00:00] [e(0)] core: Failed to connect to the database: No database YAML file
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/05/2020 17:03:49] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.

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
[12/03/2020 15:30:41] [d(0)] core: Negotiated SMB version: SMB3
[12/03/2020 15:30:41] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.
[12/03/2020 15:41:46] [d(0)] core: Module generic/custom is incompatible with multi/samba/usermap_script for PayloadType: limiter was cmd
[12/03/2020 15:41:46] [d(0)] core: Module generic/shell_bind_tcp is incompatible with multi/samba/usermap_script for PayloadType: limiter was cmd
[12/03/2020 15:41:46] [d(0)] core: Module generic/shell_reverse_tcp is incompatible with multi/samba/usermap_script for PayloadType: limiter was cmd
[12/03/2020 15:46:53] [d(0)] core: SMB version(s) to negotiate: [1]
[12/03/2020 15:46:53] [d(0)] core: Negotiated SMB version: SMB1
[12/03/2020 16:20:20] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/03/2020 16:20:20] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/03/2020 16:20:20] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/03/2020 16:20:20] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/03/2020 16:21:27] [e(0)] core: Exploit failed (linux/samba/is_known_pipename) - Msf::IncompatiblePayloadError linux/x86/shell/reverse_tcp is not a compatible payload.
[12/03/2020 16:21:41] [e(0)] core: Failed to connect to the database: No database YAML file
[12/03/2020 16:21:43] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/03/2020 16:21:43] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/03/2020 16:21:43] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/03/2020 16:21:43] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/03/2020 16:21:43] [w(0)] core: The module linux/remote/42084 is ambiguous with linux/remote/42084.
[12/03/2020 16:23:39] [d(0)] core: SMB version(s) to negotiate: [1, 2, 3]
[12/03/2020 16:23:39] [d(0)] core: Negotiated SMB version: SMB3
[12/03/2020 16:23:39] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.
[12/03/2020 21:20:05] [e(0)] core: Failed to connect to the database: No database YAML file
[12/03/2020 21:20:09] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/03/2020 21:20:09] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/03/2020 21:20:09] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/03/2020 21:20:09] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/03/2020 21:20:09] [w(0)] core: The module linux/remote/42084 is ambiguous with linux/remote/42084.
[12/03/2020 21:21:12] [d(0)] core: Module generic/custom is incompatible with unix/webapp/drupal_coder_exec for PayloadType: limiter was cmd cmd_bash
[12/03/2020 21:21:12] [d(0)] core: Module generic/shell_bind_tcp is incompatible with unix/webapp/drupal_coder_exec for PayloadType: limiter was cmd cmd_bash
[12/03/2020 21:21:12] [d(0)] core: Module generic/shell_reverse_tcp is incompatible with unix/webapp/drupal_coder_exec for PayloadType: limiter was cmd cmd_bash
[12/03/2020 21:24:28] [d(0)] core: Perl Command Encoder result: perl -e 'system(pack(qq,H186,,qq,6d6b6669666f202f746d702f62746a646a3b206e63203137322e31362e31362e34203434343420303c2f746d702f62746a646a207c202f62696e2f7368203e2f746d702f62746a646a20323e26313b20726d202f746d702f62746a646a,))'
[12/03/2020 21:24:28] [i(0)] core: cmd/unix/reverse_netcat: iteration 1: Successfully encoded with encoder cmd/perl (size is 223)
[12/05/2020 07:57:57] [e(0)] core: Failed to connect to the database: No database YAML file
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/05/2020 07:58:00] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/05/2020 07:58:01] [w(0)] core: The module linux/remote/42084 is ambiguous with linux/remote/42084.
[12/05/2020 07:58:34] [d(0)] core: SMB version(s) to negotiate: [1, 2, 3]
[12/05/2020 07:58:34] [d(0)] core: Negotiated SMB version: SMB3
[12/05/2020 07:58:34] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.
[12/05/2020 17:00:00] [e(0)] core: Failed to connect to the database: No database YAML file
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/05/2020 17:00:04] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/05/2020 17:00:05] [w(0)] core: The module linux/remote/42084 is ambiguous with linux/remote/42084.
[12/05/2020 17:03:49] [d(0)] core: SMB version(s) to negotiate: [1, 2, 3]
[12/05/2020 17:03:49] [d(0)] core: Negotiated SMB version: SMB3
[12/05/2020 17:03:49] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.

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.0.16-dev
Ruby: ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux-gnu]
Install Root: /usr/share/metasploit-framework
Session Type: postgresql selected, no connection
Install Method: Other - Please specify

@thiago0x00
Copy link
Author

Follow the prints.
msf5-workfine
msf6-bad

@thiago0x00
Copy link
Author

someone?

@dwelch-r7
Copy link
Contributor

@thiago6826 it looks like you have a typo in your command setting the log level, loglevel is all one word
setg loglevel 3 that might give us some more information on the issue

@thiago0x00
Copy link
Author

===8<=== CUT AND PASTE EVERYTHING BELOW THIS LINE ===8<===

Module/Datastore

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

Collapse
[framework/core]
loglevel=3

[framework/ui/console]
ActiveModule=exploit/linux/samba/is_known_pipename

[linux/samba/is_known_pipename]
DCERPC::fake_bind_multi=false
SHELL=/bin/sh
WORKSPACE=
VERBOSE=false
WfsDelay=0
EnableContextEncoding=false
ContextInformationFile=
DisablePayloadHandler=false
RHOSTS=192.168.10.131
RPORT=445
SSL=false
SSLVersion=Auto
SSLVerifyMode=PEER
SSLCipher=
Proxies=
CPORT=
CHOST=
ConnectTimeout=10
TCP::max_send_size=0
TCP::send_delay=0
DCERPC::max_frag_size=4096
DCERPC::fake_bind_multi_prepend=0
DCERPC::fake_bind_multi_append=0
DCERPC::smb_pipeio=rw
DCERPC::ReadTimeout=10
NTLM::UseNTLMv2=true
NTLM::UseNTLM2_session=true
NTLM::SendLM=true
NTLM::UseLMKey=false
NTLM::SendNTLM=true
NTLM::SendSPN=true
SMB::pipe_evasion=false
SMB::pipe_write_min_size=1
SMB::pipe_write_max_size=1024
SMB::pipe_read_min_size=1
SMB::pipe_read_max_size=1024
SMB::pad_data_level=0
SMB::pad_file_level=0
SMB::obscure_trans_pipe_level=0
SMBDirect=true
SMBUser=
SMBPass=
SMBDomain=.
SMBName=*SMBSERVER
SMB::VerifySignature=false
SMB::ChunkSize=500
SMB::Native_OS=Windows 2000 2195
SMB::Native_LM=Windows 2000 5.0
SMB::ProtocolVersion=1,2,3
SMB::AlwaysEncrypt=true
SMB_SHARE_NAME=
SMB_FOLDER=
PAYLOAD=cmd/unix/interact
loglevel=3

History

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

Collapse
89     search is_known
90     use 0
91     set loglevel 3
92     setg loglevel 3
93     set RHOSTS 192.168.10.131
94     exploit
95     debug

Framework Errors

The following framework errors occurred before the issue occurred:

Collapse
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/08/2020 11:49:13] [e(0)] core: Unexpected output running /usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py:
Traceback (most recent call last):
  File "/usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py", line 178, in <module>
    ntfea9000 = (pack('<BBH', 0, 0, 0) + '\x00')*0x260  # with these fea, ntfea size is 0x1c80
TypeError: can't concat str to bytes

[12/08/2020 11:49:13] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py - LoadError  Try running file manually to check for errors or dependency issues.
[12/08/2020 11:49:14] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/host_id.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:49:14] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/exchange_enum.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:49:14] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/onprem_enum.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:51:34] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.
Call stack:
/usr/share/metasploit-framework/lib/rex/proto/smb/simpleclient.rb:124:in `login'
/usr/share/metasploit-framework/lib/msf/core/exploit/smb/client.rb:155:in `smb_login'
/usr/share/metasploit-framework/modules/exploits/linux/samba/is_known_pipename.rb:394:in `smb_connect'
/usr/share/metasploit-framework/modules/exploits/linux/samba/is_known_pipename.rb:403:in `exploit'
/usr/share/metasploit-framework/lib/msf/core/exploit_driver.rb:215:in `job_run_proc'
/usr/share/metasploit-framework/lib/msf/core/exploit_driver.rb:169:in `run'
/usr/share/metasploit-framework/lib/msf/base/simple/exploit.rb:140:in `exploit_simple'
/usr/share/metasploit-framework/lib/msf/base/simple/exploit.rb:164:in `exploit_simple'
/usr/share/metasploit-framework/lib/msf/ui/console/command_dispatcher/exploit.rb:56:in `exploit_single'
/usr/share/metasploit-framework/lib/msf/ui/console/command_dispatcher/exploit.rb:212:in `cmd_exploit'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:525:in `run_command'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:476:in `block in run_single'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:470:in `each'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:470:in `run_single'
/usr/share/metasploit-framework/lib/rex/ui/text/shell.rb:158:in `run'
/usr/share/metasploit-framework/lib/metasploit/framework/command/console.rb:48:in `start'
/usr/share/metasploit-framework/lib/metasploit/framework/command/base.rb:82:in `start'
/usr/bin/msfconsole:23:in `<main>'

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
[12/08/2020 09:17:11] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/08/2020 09:17:11] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/08/2020 09:17:11] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/08/2020 09:17:11] [e(0)] core: Unexpected output running /usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py:
Traceback (most recent call last):
  File "/usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py", line 178, in <module>
    ntfea9000 = (pack('<BBH', 0, 0, 0) + '\x00')*0x260  # with these fea, ntfea size is 0x1c80
TypeError: can't concat str to bytes

[12/08/2020 09:17:11] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py - LoadError  Try running file manually to check for errors or dependency issues.
[12/08/2020 09:17:13] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/host_id.go - Errno::ENOENT No such file or directory - go
[12/08/2020 09:17:13] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/exchange_enum.go - Errno::ENOENT No such file or directory - go
[12/08/2020 09:17:13] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/onprem_enum.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:49:06] [e(0)] core: Failed to connect to the database: No database YAML file
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/encrypted_shell_reverse_tcp is not supported
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/x64/encrypted_shell_reverse_tcp is not supported
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/x64/encrypted_reverse_tcp is not supported
[12/08/2020 11:49:12] [e(0)] core: Dependency for windows/encrypted_reverse_tcp is not supported
[12/08/2020 11:49:13] [e(0)] core: Unexpected output running /usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py:
Traceback (most recent call last):
  File "/usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py", line 178, in <module>
    ntfea9000 = (pack('<BBH', 0, 0, 0) + '\x00')*0x260  # with these fea, ntfea size is 0x1c80
TypeError: can't concat str to bytes

[12/08/2020 11:49:13] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/exploits/windows/smb/ms17_010_eternalblue_win8.py - LoadError  Try running file manually to check for errors or dependency issues.
[12/08/2020 11:49:14] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/host_id.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:49:14] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/exchange_enum.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:49:14] [e(0)] core: Unable to load module /usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/onprem_enum.go - Errno::ENOENT No such file or directory - go
[12/08/2020 11:51:34] [d(0)] core: SMB version(s) to negotiate: [1, 2, 3]
[12/08/2020 11:51:34] [d(0)] core: Negotiated SMB version: SMB3
[12/08/2020 11:51:34] [e(0)] core: Exploit failed (linux/samba/is_known_pipename): Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information. - Rex::Proto::SMB::Exceptions::LoginError Login Failed: (0xc000006d) STATUS_LOGON_FAILURE: The attempted logon is invalid. This is either due to a bad username or authentication information.
Call stack:
/usr/share/metasploit-framework/lib/rex/proto/smb/simpleclient.rb:124:in `login'
/usr/share/metasploit-framework/lib/msf/core/exploit/smb/client.rb:155:in `smb_login'
/usr/share/metasploit-framework/modules/exploits/linux/samba/is_known_pipename.rb:394:in `smb_connect'
/usr/share/metasploit-framework/modules/exploits/linux/samba/is_known_pipename.rb:403:in `exploit'
/usr/share/metasploit-framework/lib/msf/core/exploit_driver.rb:215:in `job_run_proc'
/usr/share/metasploit-framework/lib/msf/core/exploit_driver.rb:169:in `run'
/usr/share/metasploit-framework/lib/msf/base/simple/exploit.rb:140:in `exploit_simple'
/usr/share/metasploit-framework/lib/msf/base/simple/exploit.rb:164:in `exploit_simple'
/usr/share/metasploit-framework/lib/msf/ui/console/command_dispatcher/exploit.rb:56:in `exploit_single'
/usr/share/metasploit-framework/lib/msf/ui/console/command_dispatcher/exploit.rb:212:in `cmd_exploit'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:525:in `run_command'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:476:in `block in run_single'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:470:in `each'
/usr/share/metasploit-framework/lib/rex/ui/text/dispatcher_shell.rb:470:in `run_single'
/usr/share/metasploit-framework/lib/rex/ui/text/shell.rb:158:in `run'
/usr/share/metasploit-framework/lib/metasploit/framework/command/console.rb:48:in `start'
/usr/share/metasploit-framework/lib/metasploit/framework/command/base.rb:82:in `start'
/usr/bin/msfconsole:23:in `<main>'

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.0.18-dev
Ruby: ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux-gnu]
Install Root: /usr/share/metasploit-framework
Session Type: postgresql selected, no connection
Install Method: Other - Please specify

@github-actions
Copy link

github-actions bot commented Jan 7, 2021

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Jan 7, 2021
@dwelch-r7 dwelch-r7 added not-stale Label to stop an issue from being auto closed and removed Stale Marks an issue as stale, to be closed if no action is taken labels Jan 7, 2021
@adfoster-r7
Copy link
Contributor

cc @cdelafuente-r7 I haven't replicated this, but from the issue description and bug report it looks like this might be a regression issue with msf6/SMB? 🤔

@adfoster-r7
Copy link
Contributor

Thanks for raising an issue; this looks to be a duplicate of #14355 - but I'll keep this open for now until that work is resolved and this issue can be confirmed as fixed too 👍

@adfoster-r7 adfoster-r7 added the confirmed Issues confirmed by a committer label Feb 10, 2021
@cdelafuente-r7
Copy link
Contributor

cdelafuente-r7 commented Feb 10, 2021

Yes, that's correct. This issue looks like the same than #14355. I'm working on it 👍

@nkakouros
Copy link

@cdelafuente-r7 Would you happen to have an update on this?

@adfoster-r7
Copy link
Contributor

I think other users have been hitting this issue, there was another request about it in the metasploit slack today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed Issues confirmed by a committer not-stale Label to stop an issue from being auto closed question Questions about Metasploit Usage
Projects
None yet
Development

No branches or pull requests

6 participants