CVSS2
Attack Vector
LOCAL
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:L/AC:M/Au:N/C:P/I:N/A:N
EPSS
Percentile
5.3%
L3 CPU shared cache architecture is susceptible to a Flush+Reload side-channel attack, resulting in information leakage. allowing a local attacker to derive the contents of memory not belonging to the attacker.
Common L3 CPU shared cache architecture is susceptible to a Flush+Reload side-channel attack, as described in “Flush+Reload: a High Resolution, Low Noise, L3 Cache Side-Channel Attack” by Yarom and Falkner.
By manipulating memory stored in the L3 cache by a target process and observing timing differences between requests for cached and non-cached memory, an attacker can derive specific information about the target process. The paper demonstrates an attack against GnuPG on an Intel Ivy Bridge platform that recovers over 98% of the bits of an RSA private key.
This vulnerability is an example of CWE-200: Information Exposure.
A local attacker can derive the contents of memory shared with another process on the same L3 cache (same physical CPU). Virtualization and cryptographic software are examples that are likely to be vulnerable.
An attacker on the same host operating system only needs read access to the executable file or a shared library component of the target process.
An attacker on a different virtual machine similarly needs access to an exact copy of the executable or shared library used by the target process, and the hypervisor needs to have memory page de-duplication enabled.
Apply an Update
See the Vendor Information section below for additional information.
GnuPG has released GnuPG version 1.4.14 and Libgcrypt 1.5.3 to to address this vulnerability. CVE-2013-4242 has been assigned to the specific GnuPG vulnerability described in the Yarom/Falkner paper. The CVSS score below applies specifically to CVE-2013-4242.
Disable Memory Page De-duplication
To prevent this attack on virtualization platforms, disable hypervisor memory page de-duplication.
Any shared cache architecture may be susceptible to side-channel or timing attacks. CPU vendors are listed as “Not Affected” since the cache architecture is functioning as designed. It is generally up to an operating system or application to take appropriate measures to protect sensitive information.
976534
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Javascript is disabled. Click here to view vendors.
Notified: August 15, 2013 Updated: August 16, 2013
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: September 13, 2013 Updated: September 13, 2013
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: August 16, 2013
Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: October 29, 2013
Not Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
AMD generally uses an exclusive cache architecture and is therefore not vulnerable to this specific attack.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23976534 Feedback>).
Notified: August 16, 2013 Updated: September 03, 2013
Not Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Not Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Not Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Not Affected
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: September 03, 2013
Unknown
We have not received a statement from the vendor.
We are not aware of further vendor information regarding this vulnerability.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
Notified: August 16, 2013 Updated: August 16, 2013
Unknown
We have not received a statement from the vendor.
View all 23 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | 2.4 | AV:L/AC:H/Au:S/C:P/I:P/A:N |
Temporal | 1.9 | E:POC/RL:OF/RC:C |
Environmental | 2.3 | CDP:ND/TD:M/CR:H/IR:H/AR:ND |
Thanks to Yuval Yarom and Katrina Falkner for reporting this vulnerability and for help writing this document.
This document was written by Adam Rauf.
CVE IDs: | CVE-2013-4242 |
---|---|
Date Public: | 2013-09-05 Date First Published: |