Advisory Fields
Reference
The fields of an advisory in the Security Advisory Application, as shown on the advisory page.
| Field | Description |
|---|---|
| Title | Title of the advisory. Required. |
| Assignee | User in charge of the advisory. See Assignee. |
| Prevent override | When checked, importing the advisory from GitHub again does not overwrite its data. |
| product | Impacted product, such as xwiki-platform. Free text. |
| Advisory Link | Link to the GitHub security advisory. |
| compute embargo | When checked, which is the default, the application computes the embargo date. |
| Embargo date | Date from which the advisory can be made public. Computed when "compute embargo" is checked, set by hand otherwise. |
| CVSS Vector | Full CVSS vector, such as CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. |
| CVSS Score | Score matching the CVSS vector. |
| Description | Full content of the advisory. |
| CVE | CVE identifier, filled by the GitHub import. |
| status | Step of the advisory in its lifecycle, changed as described in Change the Status of an Advisory. |
Impacted Packages
An advisory lists one entry per impacted package.
| Field | Description |
|---|---|
| Ecosystem | Package ecosystem, such as Maven or NPM. |
| Package Identifier | Identifier of the vulnerable package. |
| Vulnerable versions range | Range of the package versions affected by the vulnerability. |
| Patched versions | Versions of the package that fix the vulnerability. |
| Patched versions that are released | Patched versions found released, as described in Embargo Date. Computed. |
| Date of latest released version | Release date of the latest released patched version. Computed. |
Assignee
An advisory created in the wiki is assigned to its creator, except when the creator is the user importing the GitHub advisories (SPAPP-42). An advisory imported from GitHub is assigned to the XWiki user mapped to the first of its GitHub users that has a mapping, in this order: author, publisher, collaborators. An import never replaces an existing assignee.
When none of these GitHub users is mapped, the advisory page lists them. An administrator either clicks "Link to this user" to map one to an XWiki user, which assigns every advisory without assignee that involves this GitHub user, or clicks "Ignore" to stop proposing that GitHub user on any advisory, for instance an external reporter. "Ignore" is undone in the configuration. Other users ask an administrator, or select the assignee by hand.

Advisory List
The home page of the application lists the advisories. It shows only the disclosed ones by default: remove the "status" filter to see the others. The "CVE" column links to the CVE record, and the "Patched versions" column can be filtered.
