-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CVSS vector is not populated when finding is created from a template #10162
Labels
Comments
this may be fixed by just adding the cvss field here: https://github.com/DefectDojo/django-DefectDojo/blob/dev/dojo/finding/views.py#L1897 |
devsecopsale
added a commit
to devsecopsale/django-DefectDojo
that referenced
this issue
May 9, 2024
this line will keep template finding cvssv3 field in the new created finding
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Slack us first!
The easiest and fastest way to help you is via Slack. There's a free and easy signup to join our #defectdojo channel in the OWASP Slack workspace: Get Access.
If you're confident you've found a bug, or are allergic to Slack, you can submit an issue anyway.
Be informative
When a finding is created from a finding template, cvss vector field is not kept in the newly created finding.
Bug description
cvss vector is saved in the finding template but not populated to the new finding created from it.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
CVSS vector field should be saved as part of all other fields of the new finding.
Deployment method (select with an
X
)Environment information
Logs
Use
docker-compose logs
(or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).Sample scan files
If applicable, add sample scan files to help reproduce your problem.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context (optional)
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: