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

Armitage: Auxiliary failed: Net::SSH::Disconnect connection closed by remote host #18991

Open
alyaparan opened this issue Mar 22, 2024 · 2 comments
Labels
bug Stale Marks an issue as stale, to be closed if no action is taken

Comments

@alyaparan
Copy link

alyaparan commented Mar 22, 2024

msf6 auxiliary(scanner/ssh/ssh_version) > run -j
[*] Auxiliary module running as background job 19.
[-] Auxiliary failed: Net::SSH::Disconnect connection closed by remote host
[-] Call stack:
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:57:in `rescue in block (2 levels) in negotiate!'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:53:in `block (2 levels) in negotiate!'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:52:in `loop'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:52:in `block in negotiate!'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:50:in `loop'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:50:in `negotiate!'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/server_version.rb:33:in `initialize'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/session.rb:85:in `new'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/net-ssh-7.2.1/lib/net/ssh/transport/session.rb:85:in `initialize'
[-]   /usr/share/metasploit-framework/modules/auxiliary/scanner/ssh/ssh_version.rb:224:in `new'
[-]   /usr/share/metasploit-framework/modules/auxiliary/scanner/ssh/ssh_version.rb:224:in `block in run_host'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/timeout-0.4.1/lib/timeout.rb:186:in `block in timeout'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/timeout-0.4.1/lib/timeout.rb:41:in `handle_timeout'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/timeout-0.4.1/lib/timeout.rb:195:in `timeout'
[-]   /usr/share/metasploit-framework/modules/auxiliary/scanner/ssh/ssh_version.rb:223:in `run_host'
[-]   /usr/share/metasploit-framework/lib/msf/core/auxiliary/scanner.rb:128:in `block (2 levels) in run'
[-]   /usr/share/metasploit-framework/lib/msf/core/thread_manager.rb:105:in `block in spawn'
[-]   /usr/share/metasploit-framework/vendor/bundle/ruby/3.1.0/gems/logging-2.3.1/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'
@alyaparan alyaparan added the bug label Mar 22, 2024
@adfoster-r7
Copy link
Contributor

Does nmap work?

nmap -p 22 your_target_here

Copy link

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 Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Stale Marks an issue as stale, to be closed if no action is taken
Projects
Status: No status
Development

No branches or pull requests

2 participants