This issue has been created
 
 
Security Advisory Application / cid:jira-generated-image-avatar-2a4ba5ab-ca2a-4a6f-9400-d6216b73d88a SPAPP-41 Open

Allow to provide the impacted packages when creating an advisory

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-c219d9e6-d340-4e73-baf7-478425a8c45c Simon Urli created this issue on 12/Nov/26 10:56
 
Summary: Allow to provide the impacted packages when creating an advisory
Issue Type: cid:jira-generated-image-avatar-2a4ba5ab-ca2a-4a6f-9400-d6216b73d88a Improvement
Affects Versions: 2.3.0
Assignee: Unassigned
Created: 12/Nov/26 10:56
Priority: cid:jira-generated-image-static-major-515d3c14-0ad8-40f8-bf4a-96e3ca4f5a0b Major
Reporter: Simon Urli
Description:

When creating an advisory in the wiki, the edit form doesn't allow to provide its impacted packages (ecosystem, package identifier, vulnerable versions range, patched versions): the form only displays the impacted packages that already exist. The only way to add one is to click "Edit" > "Objects" after saving the advisory and add a SecurityAdvisoryImpactedPackageClass object, which requires the advanced user type.

The patched versions of the impacted packages are needed to compute the embargo date, so an advisory created in the wiki can't get a computed embargo date without going through the object editor.

Expected: the advisory edit form allows to add, edit and remove impacted packages.