Xen maintains the _GTF_{read,writ}ing bits as appropriate, to inform the guest that a grant is in use. A guest is expected not to modify the grant details while it is in use, whereas the guest is free to modify/reuse the grant entry when it is not in use. Under some circumstances, Xen will clear the status bits too early, incorrectly informing the guest that the grant is no longer in use. A guest may prematurely believe that a granted frame is safely private again, and reuse it in a way which contains sensitive information, while the domain on the far end of the grant is still using the grant. Xen 4.9, 4.8, 4.7, 4.6, and 4.5 are affected.
References
| Link | Resource |
|---|---|
| http://www.debian.org/security/2017/dsa-3969 | |
| http://www.securityfocus.com/bid/100341 | Third Party Advisory VDB Entry |
| http://www.securitytracker.com/id/1039177 | Third Party Advisory VDB Entry |
| http://xenbits.xen.org/xsa/advisory-230.html | Vendor Advisory |
| https://support.citrix.com/article/CTX225941 |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2017-08-15 16:29
Updated : 2024-02-04 19:29
NVD link : CVE-2017-12855
Mitre link : CVE-2017-12855
CVE.ORG link : CVE-2017-12855
JSON object : View
Products Affected
xen
- xen
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor