Closed emilyanncr closed 1 year ago
Hey @emilyanncr, might you be willing/able to share the XML file you're hitting the error with? If so, plz email to msfdev [at] metasploit [dot] com.
FWIW, if you find yourself in a spot in the future and want to install the latest framework release on Kali, we have some Omnibus builds available (see the section titled "Installing the Metasploit Framework on Linux"):
https://help.rapid7.com/metasploit/Content/installation-and-updates/installing-msf.html
Thx!
Thanks so much! I appreciate it. I was able to upload it using the upload function in metasploit community but when running a module, I get the same errors. I will email the xml file. Thanks so much for your help!!
did you send the XML file?
This issue appears to be specific to Metasploit Pro. The following related issues are likely duplicates:
Closing this issue as there has been no feedback for almost 6 years.
I was not able to reproduce this issue on the open source version of Metasploit.
I'm not sure what Acunetix log format was imported above, nor what format is expected. Acunetix supports multiple different report formats; however, Acunetix reports are all PDF or HTML. Acunetix also supports a few XML exports.
Attached a sample XML export from Acunetix Vulnerability Scanner version 11.0.1732711618 (trial) run against metasploitable2. I terminated the scan before completion but the XML export contains plenty of data. This matches the DBManager::Import::Acunetix
import regex and was imported successfully.
It is worth noting that no vulnerabilities were imported. I've created issue #17932 to track this.
msf6 > db_import acunetix.xml
[*] Importing 'Acunetix' data
[*] Import: Parsing with 'Nokogiri v1.14.2'
[*] Importing host 192.168.200.142
[*] Importing service 192.168.200.142:80
[*] Successfully imported /root/Desktop/metasploit-framework/acunetix.xml
msf6 > hosts
Hosts
=====
address mac name os_name os_flavor os_sp purpose info comments
------- --- ---- ------- --------- ----- ------- ---- --------
192.168.200.142 192.168.200.142 Unknown device
msf6 > services
Services
========
host port proto name state info
---- ---- ----- ---- ----- ----
192.168.200.142 80 tcp http open
msf6 > creds
Credentials
===========
host origin service public private realm private_type JtR Format
---- ------ ------- ------ ------- ----- ------------ ----------
vmsf6 > vulns
Vulnerabilities
===============
Timestamp Host Name References
--------- ---- ---- ----------
msf6 > notes
Notes
=====
Time Host Service Port Protocol Type Data
---- ---- ------- ---- -------- ---- ----
2023-04-25 14:35:56 U 192.168.200.142 host.imported {:filename=>"/root/Desktop/metasploit-framework/acunetix.xml", :type=>"Acunetix", :
TC time=>2023-04-25 14:35:56.345537239 UTC}
msf6 > wmap_vulns -l
msf6 > wmap_sites -l
[*] Available sites
===============
Id Host Vhost Port Proto # Pages # Forms
-- ---- ----- ---- ----- ------- -------
0 192.168.200.142 192.168.200.142 80 http 0 0
msf6 >
Steps to reproduce
When attempting to import a scan using db_import, I get the following error:
System stuff
OS: Kali Linux Version: Kali GNU/Linux Rolling \n \l msf > version\r Framework: 4.15.4-dev Console : 4.15.4-dev Installed with [ ] Commercial/Community installer (from http://www.rapid7.com/products/metasploit/download.jsp)
After the latest upgrade and dist-upgrade something funky was happening when running msfconsole. I ended up uninstalling metasploit all together so I could reinstall and hopefully fix the problem. Installing it from the command line using apt-get install, however, kept giving me an error when trying to start metasploit from the command line. I googled the error and came across an answer which messed things up a bit more. So after some fiddling and troubleshooting I tried installing it again, this time using the installer provided on rapid7. Everything was successful and I was able to start the framework from the command line without error AND without error when running msfconsole. Prior to this update, the db_import command was working just fine so something must of gone awry during this whole process. Or it might have nothing to do with it. I'm too novice to understand the log output, so any help is appreciated.
Thanks in advance!