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

Unable to retrieve proofs #213

Closed
Red5d opened this issue Apr 5, 2016 · 2 comments
Closed

Unable to retrieve proofs #213

Red5d opened this issue Apr 5, 2016 · 2 comments

Comments

@Red5d
Copy link
Contributor

Red5d commented Apr 5, 2016

The VulnerabilityInstance class is currently unused: https://github.com/rapid7/nexpose-client/blob/c7f976c58229b80057ea158ec48c2c603e7cf1c5/lib/nexpose/vuln.rb

It lists a "proof" attribute, but I don't see a way to get the proofs for a vulnerability on an asset since it doesn't look like that class is used anywhere else.

@sgreen-r7
Copy link
Contributor

Alright, so after a bit of looking - we finally found the answer.

nsc = Nexpose::Connection.new 'nexpose', 'user', 'pass'
nsc.login
nsc.list_assets -- This will actually return your assets, but using the Device class, which will not give you vuln info.

asset = Nexpose::Asset.load(nsc, 1) insert your asset_id instead of 1.
asset.vulnerability_instances -- this is what you're looking for.

Basically you'll need to have the Asset class loaded in order to grab the proof via the VulnerabilityInstance class. Sorry for the confusion, we're going to go ahead and add some comments into the VulnerabilityInstance class pointing back to the Asset class.

Let us know if that gets you passed your sticking point. Thanks.

@sgreen-r7
Copy link
Contributor

Heya @Red5d

We went ahead and updated the documentation on the VulnerabilityInstance class to make it a bit easier next time. 9039229

Feel free to reopen this issue, or a new one if you have anymore questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants