|
|
I reproduced this issue with metasploit version >= 5.0.14 |
|
|
I am currently using metasploit 5.0.16 and the issue is still in full effect |
|
|
Not sure if this actually will help , and I feel it has nothing to do with the issue. But just in case, I do not run Gnome like the majority of the planet. I am running K.D.E |
|
|
Confirm still an issue, did apt update && apt -y full-upgrade and see the same behavior |
|
|
There are a few forks of armitage on GitHub with patches past what armitage's main repo has. Unfortunately, I haven't had time to look through all of them. One of them may have a patch to support msf5, without an open pull request just yet. e.g. https://github.com/kimocoder/armitage |
|
|
I checked the forks on GiHtub. There are some patches we don't have in Kali. But they are not for msf5. I tested them even so and I still have the issue. |
|
|
the issue is still confirmed..stilll having the same problem over here too |
|
|
Same issue, performed a full update yet it wasn't fixed |
|
|
Until this bug is marked as resolved, unfortunately, the bug is not yet fixed. |
|
|
The issue appears to rely on the ranking of exploits. Selecting poor or manually adding low to preferences you will get it to function. This all smells of a difference in db structure changes or/and something related to new postgresql and rpc. I have done clean ant, rebuilt from original with changes but check changes in msf database since this tool simply synchs it. |
|
|
Good work Nafwa03 |
|
|
I have the same issue. Recreating db does not fix this. Is there a workaround ? Armitage has been useless since April updates. |
|
|
See nafwa03’s comment for a workaround until we get this fixed @gromek82 |
|
|
@steev - that did the trick - many thanks. |
|
|
Here's the upstream ticket FWIW, nothing new compared to the discussion here so far. And no sign of upstream activity either: https://github.com/rsmudge/armitage/issues/224 |
|
|
I'm pretty confident that major or minor issues with metasploit and armitage are the postgresql binding to localhost. That could be a deep or non-deep problem but its my two cents.. |
|
|
1.JPG (44,704 bytes)
2.JPG (55,253 bytes) |
|
|
I think i found a work around from this issue... On Armitage - Go to set exploit rank and change to POOR Try to find attacks...you will see this working now.. Please let me know if this works for you |
|
|
Yes, as noted by Nafwa03, that does work.
image.png (21,358 bytes) |
- Anonymous