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

[enhancement] Add the entire CVE "blob" to the JSON-export #35

Closed
p0dalirius opened this issue Sep 25, 2023 · 1 comment · Fixed by #36
Closed

[enhancement] Add the entire CVE "blob" to the JSON-export #35

p0dalirius opened this issue Sep 25, 2023 · 1 comment · Fixed by #36
Assignees
Labels
enhancement New feature or request

Comments

@p0dalirius
Copy link
Owner

p0dalirius commented Sep 25, 2023

In theory, it might be useful to add the entire CVE "blob" to the JSON-export and leave further filtering to the user which uses it later, but I leave you to decide that. If you think that's a good idea, then I'll rework it towards that.

Downside to that: the 3 exports would differ in that way.

Originally posted by @Sandr0x00 in #34 (comment)

I think you are right, this is a good idea.

@Sandr0x00
Copy link
Contributor

Sandr0x00 commented Sep 25, 2023

You'll get another PR tomorrow fixing that :)
Feel free to assign it to me

@p0dalirius p0dalirius added the enhancement New feature or request label Sep 26, 2023
Sandr0x00 added a commit to Sandr0x00/ApacheTomcatScanner that referenced this issue Sep 26, 2023
p0dalirius pushed a commit that referenced this issue Sep 26, 2023
* Fixes to export functions, add finding-cves also to JSON output

* Fixes #35: add entire JSON-CVE-Blob to json output

* added pycache to gitignore

---------

Co-authored-by: Sandro Bauer <sandro.bauer@smart-cybersecurity.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants