VEX statuses and justifications
Affectra uses the values of the OpenVEX specification. The API, the app and every export write them the same way. To record statements, see Assess findings with VEX.
Statuses
Section titled “Statuses”| Value | In the app | Meaning | The finding |
|---|---|---|---|
not_affected |
Not affected | The release is not affected by the vulnerability. Needs a justification or an impact statement. | Resolved |
affected |
Affected | The release is affected. Needs an action statement: what should users do? | Open |
fixed |
Fixed | The vulnerability is fixed in this release. | Resolved |
under_investigation |
Under investigation | You are looking into it. | Open |
A resolved finding leaves the open findings. It still shows under All on the release.
Justifications
Section titled “Justifications”Only not_affected takes a justification. The API accepts these five values:
| Value | Meaning |
|---|---|
component_not_present |
The component is not in this release. |
vulnerable_code_not_present |
The vulnerable code is not in this build. |
vulnerable_code_not_in_execute_path |
The vulnerable code is never run. |
vulnerable_code_cannot_be_controlled_by_adversary |
An attacker cannot reach or control it. |
inline_mitigations_already_exist |
Mitigations in the release prevent it. |
Any other value is refused.
Statement fields
Section titled “Statement fields”| Field | Rule |
|---|---|
vulnerability |
An ID such as CVE-2023-0286, a GHSA ID or DSA-5343-1. Letters, digits and ., _, :, -. It starts with a letter or digit and has at most 100 characters. |
status |
One of the four statuses. |
justification |
One of the five values. Only with not_affected. |
impact_statement |
Free text, at most 4000 characters. not_affected needs this or a justification. |
action_statement |
Free text, at most 4000 characters. affected needs it. |
A statement is never changed. A new one for the same vulnerability replaces the current one, and the history keeps both.
In the exports
Section titled “In the exports”OpenVEX uses the values as they are. CycloneDX VEX renames them:
| Status | CycloneDX analysis state |
|---|---|
not_affected |
not_affected |
affected |
exploitable |
fixed |
resolved |
under_investigation |
in_triage |
| Justification | CycloneDX justification |
|---|---|
component_not_present |
code_not_present |
vulnerable_code_not_present |
code_not_present |
vulnerable_code_not_in_execute_path |
code_not_reachable |
vulnerable_code_cannot_be_controlled_by_adversary |
requires_environment |
inline_mitigations_already_exist |
protected_by_mitigating_control |
CSAF uses the statuses known_not_affected, known_affected, fixed and under_investigation, and gives the justification as a flag.