Difference between revisions of "Characterizing Vulnerabilities in Platform Security"

From Xen
Jump to: navigation, search
(CVE Numbers and CVE Publication Dates)
(CVE Numbers and CVE Publication Dates)
Line 23: Line 23:
  
 
In addition, there are some XSAs, which do not have CVE numbers: this typically applies for  
 
In addition, there are some XSAs, which do not have CVE numbers: this typically applies for  
* '''Unused XSA numbers'''  
+
* '''Unused/Widthdrawn XSA numbers'''  
 
* Warnings about the '''security status of functionality''' - e.g. [http://xenbits.xen.org/xsa/advisory-163.html XSA 163]
 
* Warnings about the '''security status of functionality''' - e.g. [http://xenbits.xen.org/xsa/advisory-163.html XSA 163]
 
* Warnings about the '''security impact of some hardware''' - e.g. [http://xenbits.xen.org/xsa/advisory-124.html XSA 124]
 
* Warnings about the '''security impact of some hardware''' - e.g. [http://xenbits.xen.org/xsa/advisory-124.html XSA 124]

Revision as of 10:28, 11 October 2018

This article provides some information on works related to characterizing Vulnerabilities within the Xen Project Hypervisor, as well as related projects.

Vulnerabilities handled by the Xen Project Security Team

Vulnerability Scope Boundaries

The Xen Project Security Response team follows the project's Security Response Process and publishes security issue via xenbits.xen.org/xsa. Security issues covered by the process include issues within the following vulnerability scope boundaries:

In addition, some vulnerabilities will impact only a subset of Xen versions, a specific architecture (x86 Intel, x86 AMD, Arm 32, Arm 64) or specific configuration and/or virtualization mode (PV, HVM, PVH). Typically products based on Xen will be based on a specific version, subset of features and specific architecture. For example, many Xen based products and services will only support a subset of virtualization modes.

Severity

Unlike other open source projects, the Xen Project always publishes XSAs for security bugs of low severity. The primary reason for this approach is that there are many different products for very different use-cases, ranging from server virtualisation/cloud computing, to desktop applications (such as Qubes OS), to embedded Xen distributions and that severity cannot usually be determined without considering the specific use-case and context.

CVE Numbers and CVE Publication Dates

Note that there is not always a 1-2-1 mapping between CVE numbers and XSAs. Sometimes multiple CVE numbers exist for a single XSA. This typically is the case in the following circumstances:

  • When multiple Hardware vulnerabilities affecting Xen can be addressed by the same mitigation (e.g. XSA 273)
  • When related attack vectors can be addressed by the same mitigation (e.g. XSA 201, XSA 218, XSA 196)

In addition, there are some XSAs, which do not have CVE numbers: this typically applies for

  • Unused/Widthdrawn XSA numbers
  • Warnings about the security status of functionality - e.g. XSA 163
  • Warnings about the security impact of some hardware - e.g. XSA 124
  • Warnings about security issues in example code that may have been productised - e.g. XSA 99

Note that the mapping of CVE numbers to years may not match the XSA publication dates: this frequently happens towards the end of a calendar year.

CVE databases

CVE databases such as CVE Details will consume vulnerability data published by the Xen Project and publish it under a Xen-specific vendor ID (e.g. Xen vendor on CVE Details). This means that vulnerabilities with very different vulnerability scope boundaries (e.g. Xen Hypervisor, Hypervisor toolstack(s), Linux kernel components affecting Xen, Hardware vulnerabilities affecting Xen, QEMU components) will all be listed under the Xen-specific vendor ID. Manual filtering of vulnerabilities is required when considering a specific scope, use-case or architecture.

Upstreams

Security teams of Xen Upstreams (e.g. Linux Distros or QEMU) will notify the Xen Project Security Team of security issues they suspect will impact Xen. However, this usually depends on the wishes of the discoverer of an issue (for example, see QEMU Security Process).

Considerations when Characterizing Xen Vulnerabilities or comparing Hypervisors

When Characterizing Xen Vulnerabilities it is important to consider the following factors

  • Vulnerability Scope Boundaries
  • Use-case and Hypervisor Configurations, CPU Architecture and Virtualization modes that may be used

When comparing Hypervisors (or in general similar software), it is important to note that different Hypervisors have different architectures and different approaches to Software Vulnerability Management. For example, it is common practice amongst many open source software projects to not handle low-severity security issues. Also, for some technologies there is not always a single place from which to obtain a definite list of vulnerabilities affecting the technology.

Prior Work Characterizing Vulnerabilities