CVSS2
Attack Vector
LOCAL
Attack Complexity
HIGH
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:L/AC:H/Au:N/C:P/I:N/A:N
EPSS
Percentile
15.7%
Various implementations of RSA may contain a vulnerability that could allow an attacker to retrieve encryption keys.
Some implementations of RSA may contain a vulnerability that could allow a local attacker to retrieve encryption keys.
OpenSSL is a widely used open source implementation of the SSL and TLS protocols. OpenSSL is based on the SSLeay library. OpenSSL provides support for the RSA encryption algorithm. Note that vendors may include a vulnerable version of OpenSSL in web servers, VPN, or other products.
An attacker could possibly decrypt messages that were encrypted with OpenSSL using RSA algorithm.
Apply a patch
OpenSSL has released a patch to address this issue. See <http://openssl.org/news/patch-CVE-2007-3108.txt> for more details. See the systems affected portion of this document for a partial list of other vendors who may be affected.
724968
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.
Updated: August 02, 2007
Affected
The paper describes another example of a side-channel attack, not specific to OpenSSL, where an untrusted local user may be able to discover private key material that is in use on that system
(CVE-2007-3108).
The OpenSSL team have made the following patch available for OpenSSL 0.9.8 that can mitigate this issue. This patch will be part of a future release (although no new release is currently planned).
<http://openssl.org/news/patch-CVE-2007-3108.txt>
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: August 02, 2007
Unknown
This Vulnerability Note addresses a covert channel issue that represents one particular instance of a large class of side-channel attacks made possible by certain architectural features of modern CPUs. While it’s possible to (probably) work around this one instance, the only fully effective solution that will work against current as well as future attacks of this kind is to not place sensitive data or data-dependent code flow in a position where side- channel attacks are possible. The cryptlib documentation contains guidance on doing this in the section “Safeguarding Cryptographic Operations”.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: July 31, 2007 Updated: July 31, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 13, 2007 Updated: August 13, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 27, 2007 Updated: August 27, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: August 01, 2007 Updated: August 01, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Notified: June 28, 2007 Updated: June 28, 2007
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
View all 64 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | 0 | AV:–/AC:–/Au:–/C:–/I:–/A:– |
Temporal | 0 | E:ND/RL:ND/RC:ND |
Environmental | 0 | CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND |
Thanks to Dr. Onur Aciicmez, Samsung Information Systems America, Samsung Electronics R&D Center, USA, and Prof. Werner Schindler, Bundesamt für Sicherheit in der Informationstechnik (BSI), Germany for reporting this vulnerability.
This document was written by Ryan Giobbi.
CVE IDs: | CVE-2007-3108 |
---|---|
Severity Metric: | 1.77 Date Public: |