This issue has been created
There are 3 updates.
 
 
Security Advisory Application / cid:jira-generated-image-avatar-a18ebe43-4ddd-44d0-8709-2fc3a3031ca2 SPAPP-45 Open

Security entries imported before 2.3.0 never get an assignee

 
View issue   ·   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-0e1cb0d3-5953-462b-9267-526a09fb5517 Simon Urli created this issue on 13/Nov/26 11:52
 
Summary: Security entries imported before 2.3.0 never get an assignee
Issue Type: cid:jira-generated-image-avatar-a18ebe43-4ddd-44d0-8709-2fc3a3031ca2 Bug
Affects Versions: 2.3.0
Assignee: Unassigned
Created: 13/Nov/26 11:52
Priority: cid:jira-generated-image-static-major-8ae348ad-f9ca-4b54-b106-f31f912f4648 Major
Reporter: Simon Urli
Description:

Problem

Security entries imported from GitHub before 2.3.0 that were not updated on GitHub since the upgrade have no assignee, and they cannot get one: they are missing the external users (the GitHub users involved in the advisory) that the assignee is resolved from.

Example: GHSA-8469-jx93-r677, last imported on 2026-10-20 (before the 2.3.0 upgrade of 2026-11-04), has no SecurityAdvisoryApplication.Code.ExternalUserClass object and no assignee.

Cause

  • The external users and the assignee are only written when an advisory is imported.
  • The scheduled import only fetches the advisories updated on GitHub since its previous run, so an advisory unchanged on GitHub since the upgrade is never re-imported.
  • The upgrade to 2.3.0 does not backfill the existing entries, so these entries:
    • are not listed among the advisories without assignee,
    • do not contribute their GitHub users to the "GitHub users mapping" administration,
    • are not assigned by the assignee resolution job when a GitHub user gets mapped.

Expected

The upgrade migration should make sure that every entry having an advisory URL gets its assignee metadata: its external users, fetched from the advisory, and the assignee resolved from their mapping when the entry has none yet. It must not change any other data of the entry (title, content, state, CVSS, impacted packages, …), nor an assignee that is already set.

Workaround

Re-import each affected advisory, e.g. with $services.securityadvisory.importAndSaveAdvisory('<advisory URL>'); note that this also overwrites the other imported data of the entry.

 
 

3 updates

 
cid:jira-generated-image-avatar-0e1cb0d3-5953-462b-9267-526a09fb5517 Changes by Simon Urli on 13/Nov/26 11:52
 
Fix Version: 2.3.1
Description: h2. Problem

Security entries imported from GitHub before 2.3.0 that were not updated on GitHub since the upgrade have no assignee, and they cannot get one: they are missing the external users (the GitHub users involved in the advisory) that the assignee is resolved from.

Example:
[GHSA-8469-jx93-r677|https://www.xwiki.org/xwiki/bin/view/SecurityAdvisoryApplication/SecurityEntries/GHSA-8469-jx93-r677], an entry last imported on 2026-10-20 (before the 2.3.0 upgrade of 2026-11-04), has no {{SecurityAdvisoryApplication.Code.ExternalUserClass}} object and no assignee.

h2. Cause

* The external users and the assignee are only written when an advisory is imported.
* The scheduled import only fetches the advisories updated on GitHub since its previous run, so an advisory unchanged on GitHub since the upgrade is never re-imported.
* The upgrade to 2.3.0 does not backfill the existing entries, so these entries:
** are not listed among the advisories without assignee,
** do not contribute their GitHub users to the "GitHub users mapping" administration,
** are not assigned by the assignee resolution job when a GitHub user gets mapped.

h2. Expected

The upgrade migration should make sure that every entry having an advisory URL gets its assignee metadata: its external users, fetched from the advisory, and the assignee resolved from their mapping when the entry has none yet. It must not change any other data of the entry (title, content, state, CVSS, impacted packages, …), nor an assignee that is already set.

h2. Workaround

Re-import each affected advisory, e.g. with {{$services.securityadvisory.importAndSaveAdvisory('<advisory URL>')}}; note that this also overwrites the other imported data of the entry.
Assignee: Simon Urli