MS-2910: Remote Vuln Read Update Delete #20
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for vuln read, update and delete operations when using a remote data store. The
vulns
command was modified to output the vuln data in table format to be consistent with the other commands. An undocumentedvulns
command option for delete was added:vulns --delete
- Delete vulns that match the address range and search termIn addition, this PR fixes an existing issue in the
report_vuln
method where multiple calls for the same vuln results in the creation of duplicateVulnRef
records, except for the CVE refs.Verification
msfconsole
msfdb_ws
on a remote systemdata_services --add <address>
use exploit/unix/irc/unreal_ircd_3281_backdoor
against Metasploitable3 VM.vulns
andvulns --info
show the newly added vulnerabilitiesreport_vuln
method inlib/msf/core/auxiliary/report.rb
. For example,use auxiliary/scanner/ssl/openssl_heartbleed
against a vulnerable VM.vulns
andvulns --info
show the newly added vulnerabilitiesvulns --delete --search <search term>
) or delete all vulns (vulns --delete
)vulns
shows the correct vulnerabilities after the delete operationcurl -H "Content-Type: application/json" -X PUT -d '{"info": "test update"}' {server}:{port}/api/v1/vulns/{id}
vulns --info
shows the correct vulnerability data after the update operation