VEX takes the noise out of an SBOM by showing which vulnerabilities are irrelevant and which have already been fixed.
A VEX report goes alongside an SBOM and VDR to communicate if and how a vulnerability can impact the security of the software when it’s running.
A VEX report can be summed up in the statements
section of its structure:
"statements": [
{
"vulnerability": {
"@id": "CVE-2019-1010022"
},
"timestamp": "2023-09-18T14:07:00.1097922Z",
"products": [
{
"@id": "pkg:deb/debian/libc6@2.36-9?arch=amd64&upstream=glibc&distro=debian-12",
"identifiers": {
"purl": "pkg:deb/debian/libc6@2.36-9?arch=amd64&upstream=glibc&distro=debian-12"
}
}
],
"status": "not_affected",
"justification": "vulnerable_code_not_in_execute_path",
"impact_statement": "EdgeBit automated analysis indicates that the vulnerable code is dormant and not executed"
},