VEX (Vulnerability Exploitability eXchange)
Что такое VEX (Vulnerability Exploitability eXchange)?
VEX (Vulnerability Exploitability eXchange)A machine-readable companion to the SBOM that tells consumers whether a listed CVE actually affects a given product — distinguishing 'present in the bill of materials' from 'reachable and exploitable'.
VEX (Vulnerability Exploitability eXchange) is a class of attestation document, formalized by CISA and the U.S. NTIA in 2022–2023, designed to suppress SBOM noise. When a customer scans a vendor's product, they typically discover every CVE listed against every transitive dependency — most of which are not actually exploitable because the affected code path is unused, mitigated, or compiled out. A VEX statement, signed by the vendor or downstream maintainer, declares one of four statuses for each (product, CVE) pair: not_affected, affected, fixed, or under_investigation, plus a justification (e.g. 'vulnerable_code_not_in_execute_path'). VEX is format-agnostic and is currently produced as OpenVEX (a minimal JSON profile), CSAF VEX (an OASIS-standardized profile), or embedded in CycloneDX vulnerability extensions. It is becoming a contractual deliverable alongside SBOMs in regulated sectors.
● Примеры
- 01
A library upgrade adds a transitive dep flagged with five CVEs; the vendor ships an OpenVEX document marking four as 'not_affected: vulnerable_code_not_in_execute_path'.
- 02
An automated scanner consumes the customer's SBOM plus the vendor's VEX statements and reduces 200 raw CVE findings to 7 actionable ones.
● Частые вопросы
Что такое VEX (Vulnerability Exploitability eXchange)?
A machine-readable companion to the SBOM that tells consumers whether a listed CVE actually affects a given product — distinguishing 'present in the bill of materials' from 'reachable and exploitable'. Относится к категории Безопасность приложений в кибербезопасности.
Что означает VEX (Vulnerability Exploitability eXchange)?
A machine-readable companion to the SBOM that tells consumers whether a listed CVE actually affects a given product — distinguishing 'present in the bill of materials' from 'reachable and exploitable'.
Как работает VEX (Vulnerability Exploitability eXchange)?
VEX (Vulnerability Exploitability eXchange) is a class of attestation document, formalized by CISA and the U.S. NTIA in 2022–2023, designed to suppress SBOM noise. When a customer scans a vendor's product, they typically discover every CVE listed against every transitive dependency — most of which are not actually exploitable because the affected code path is unused, mitigated, or compiled out. A VEX statement, signed by the vendor or downstream maintainer, declares one of four statuses for each (product, CVE) pair: not_affected, affected, fixed, or under_investigation, plus a justification (e.g. 'vulnerable_code_not_in_execute_path'). VEX is format-agnostic and is currently produced as OpenVEX (a minimal JSON profile), CSAF VEX (an OASIS-standardized profile), or embedded in CycloneDX vulnerability extensions. It is becoming a contractual deliverable alongside SBOMs in regulated sectors.
Как защититься от VEX (Vulnerability Exploitability eXchange)?
Защита от VEX (Vulnerability Exploitability eXchange) обычно сочетает технические меры и операционные практики, как описано в определении выше.
Какие есть другие названия VEX (Vulnerability Exploitability eXchange)?
Распространённые альтернативные названия: Vulnerability Exploitability eXchange, OpenVEX, CSAF VEX.
● Связанные термины
- appsec№ 1185
Software Bill of Materials (SBOM)
Формальный машиночитаемый перечень компонентов, библиотек и зависимостей, образующих программное обеспечение, с указанием версий и их связей.
- appsec№ 297
CycloneDX
An OWASP-curated open standard for software, SaaS, ML, and crypto bills of materials, designed from the start for security use cases and now widely used to ship SBOMs alongside releases.
- appsec№ 1190
SPDX (Software Package Data Exchange)
A Linux Foundation-maintained, ISO/IEC 5962-standardized open format for software bills of materials, originally focused on license metadata and now broadly used for SBOMs.
- vulnerabilities№ 285
CVE (Common Vulnerabilities and Exposures)
Публичный каталог, присваивающий уникальный идентификатор каждой раскрытой уязвимости ПО или оборудования для однозначных ссылок в индустрии.
- vulnerabilities№ 428
EPSS (Exploit Prediction Scoring System)
Модель на основе данных, поддерживаемая FIRST, оценивающая вероятность эксплуатации конкретной CVE в дикой природе в ближайшие 30 дней.
- vulnerabilities№ 663
Известная эксплуатируемая уязвимость (KEV)
CVE, активная эксплуатация которой подтверждена CISA США и которая включена в публичный каталог KEV, что устанавливает сроки устранения для федеральных ведомств США.