Hi @panajo1017
Thanks for reporting this issue. I have just created a patch to handle this situation in a better way.
Feel free to create a github issue in the corresponding project’s issue tracker next time
Best regards,
greenbone:main
← greenbone:severity-vector
opened 07:37AM - 19 Oct 22 UTC
**What**:
Fix: improve handling of malformed severity vectors.
Jira: SC-706
<… !--
Describe what changes are being made, e.g. which feature/bug is being
developed/fixed in this PR?
-->
**Why**:
Ospd-openvas handles base metrics only. If there are any optional metric the task fails.
With this patch, the error is handled in a way that task can continue.
**How**:
Modify the severity vector of an existing VT including optional metrics. Update the feed and run a scan. Be sure that you include the modify VT in the plugin list and that it generates an alarm/result.
Without the patch the task crashes. With the patch the task finished as expected.
<!--
How did you verify the changes in this PR?
If this PR contains tests this section can be considered done.
Otherwise please write down the steps on how you did test your changes and
verified that the changes are working as expected.
See https://www.ministryoftesting.com/dojo/lessons/community-stories-to-shift-left-start-right
for some background.
-->
**Checklist**:
- [x] Tests
- [x] PR merge commit message adjusted
5 Likes