Skip to content

Update stuff#47

Open
eoksum wants to merge 4 commits intoscipag:masterfrom
eoksum:master
Open

Update stuff#47
eoksum wants to merge 4 commits intoscipag:masterfrom
eoksum:master

Conversation

@eoksum
Copy link

@eoksum eoksum commented Mar 9, 2022

Update CVE and ExploitDB databases,
Update README.

@marcruef marcruef self-assigned this Mar 11, 2022
* securityfocus.csv - https://www.securityfocus.com/bid/
* xforce.csv - https://exchange.xforce.ibmcloud.com/
* expliotdb.csv - https://www.exploit-db.com
* exploitdb.csv - https://www.exploit-db.com
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this!

Copy link
Member

@marcruef marcruef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixing the typo is great, thanks.

But we do not accept external db updates. They are generated with a tool that implements pre-filtering to optimize performance of scanning. Thank you for your understanding.

Copy the files into your vulscan folder:

/vulscan/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part needs to remain as we will resume regular updates in the future.

@eoksum
Copy link
Author

eoksum commented Mar 11, 2022

Thanks, but I would recommend updating them yourself then as they are very very obsolete.
I created seperate tool in Python to automatically obtain vulnerablities from ExploitDB and CVE, convert them to vulscan's format and puts them in files. If you want, I can also share that tool.

@perlland
Copy link

Please share the tool

@eoksum
Copy link
Author

eoksum commented Jun 25, 2022

Please share the tool

Sure. Check these out:
https://pastebin.com/ADn4hi5a
https://pastebin.com/c5uEvCNB

@ocervell
Copy link

Using the ./update.sh script, the latest CVEs I get are from 2013 ... This makes vulscan super obsolete. I agree it's time to download the CSVs directly from their source using the corresponding APIs.

Any updates here ?

@yuunnn
Copy link

yuunnn commented May 17, 2023

Please share the tool

Sure. Check these out: https://pastebin.com/ADn4hi5a https://pastebin.com/c5uEvCNB

Hi, the Python code for accessing the CVE database works fine, but the code for ExploitDB seems to be down. Can you please provide it again? Thanks!

@gigachad80
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

@destiny-creates
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

Unfortunately they ended CSV support. It's all JSON now... gotta love it.

@gigachad80
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

Unfortunately they ended CSV support. It's all JSON now... gotta love it.

Exactly that's what causing issues. Still can't figure it out automated approach on how to process them in CSV format . If only there's any way or workflow to automate

@destiny-creates
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

Unfortunately they ended CSV support. It's all JSON now... gotta love it.

Exactly that's what causing issues. Still can't figure it out automated approach on how to process them in CSV format . If only there's any way or workflow to automate

Try the first comment here:

https://stackoverflow.com/questions/1871524/how-can-i-convert-json-to-csv

@gigachad80
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

Unfortunately they ended CSV support. It's all JSON now... gotta love it.

Exactly that's what causing issues. Still can't figure it out automated approach on how to process them in CSV format . If only there's any way or workflow to automate

Try the first comment here:

https://stackoverflow.com/questions/1871524/how-can-i-convert-json-to-csv

This looks good. I hope this solves the issue. Maybe I'll need to integrate it with a GitHub workflow to resolve it. Thanks @destiny-creates for this answer. I'll update my tool in my free time.

@destiny-creates
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

Unfortunately they ended CSV support. It's all JSON now... gotta love it.

Exactly that's what causing issues. Still can't figure it out automated approach on how to process them in CSV format . If only there's any way or workflow to automate

Try the first comment here:
https://stackoverflow.com/questions/1871524/how-can-i-convert-json-to-csv

This looks good. I hope this solves the issue. Maybe I'll need to integrate it with a GitHub workflow to resolve it. Thanks @destiny-creates for this answer. I'll update my tool in my free time.

keep us posted cause we might like to use it, if anything make a PR to this repo and implement it as a built in tool.

@gigachad80
Copy link

@ocervell I've designed a workflow on updated version of Vulscan and thinking of making it open source after implementation. It will solve all issues .I thought of rewriting in Go but there aren't any Go packages which will solve issue , so I will stick to Lua. Don't know how much time it will take. I am not getting any medium to contact CVE or MITRE org. Once they answer some questions, then I will get an idea how to update it and modify the workflow .

Unfortunately they ended CSV support. It's all JSON now... gotta love it.

Exactly that's what causing issues. Still can't figure it out automated approach on how to process them in CSV format . If only there's any way or workflow to automate

Try the first comment here:
https://stackoverflow.com/questions/1871524/how-can-i-convert-json-to-csv

This looks good. I hope this solves the issue. Maybe I'll need to integrate it with a GitHub workflow to resolve it. Thanks @destiny-creates for this answer. I'll update my tool in my free time.

keep us posted cause we might like to use it, if anything make a PR to this repo and implement it as a built in tool.

Sure brother 🙌

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

7 participants