ghsa-q7xg-gmg7-59f4
Vulnerability from github
Published
2022-05-14 03:58
Modified
2022-05-14 03:58
Severity ?
5.1 (Medium) - CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Details

The MOD_EXP_CTIME_COPY_FROM_PREBUF function in crypto/bn/bn_exp.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g does not properly consider cache-bank access times during modular exponentiation, which makes it easier for local users to discover RSA keys by running a crafted application on the same Intel Sandy Bridge CPU core as a victim and leveraging cache-bank conflicts, aka a "CacheBleed" attack.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2016-0702",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-200",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2016-03-03T20:59:00Z",
      severity: "MODERATE",
   },
   details: "The MOD_EXP_CTIME_COPY_FROM_PREBUF function in crypto/bn/bn_exp.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g does not properly consider cache-bank access times during modular exponentiation, which makes it easier for local users to discover RSA keys by running a crafted application on the same Intel Sandy Bridge CPU core as a victim and leveraging cache-bank conflicts, aka a \"CacheBleed\" attack.",
   id: "GHSA-q7xg-gmg7-59f4",
   modified: "2022-05-14T03:58:17Z",
   published: "2022-05-14T03:58:17Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2016-0702",
      },
      {
         type: "WEB",
         url: "https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf",
      },
      {
         type: "WEB",
         url: "https://git.openssl.org/?p=openssl.git;a=commit;h=708dc2f1291e104fe4eef810bb8ffc1fae5b19c1",
      },
      {
         type: "WEB",
         url: "https://h20566.www2.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03741en_us",
      },
      {
         type: "WEB",
         url: "https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05052990",
      },
      {
         type: "WEB",
         url: "https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05376917",
      },
      {
         type: "WEB",
         url: "https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05390722",
      },
      {
         type: "WEB",
         url: "https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA40168",
      },
      {
         type: "WEB",
         url: "https://security.FreeBSD.org/advisories/FreeBSD-SA-16:12.openssl.asc",
      },
      {
         type: "WEB",
         url: "https://security.gentoo.org/glsa/201603-15",
      },
      {
         type: "WEB",
         url: "https://www.openssl.org/news/secadv/20160301.txt",
      },
      {
         type: "WEB",
         url: "http://cachebleed.info",
      },
      {
         type: "WEB",
         url: "http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10759",
      },
      {
         type: "WEB",
         url: "http://lists.fedoraproject.org/pipermail/package-announce/2016-March/178358.html",
      },
      {
         type: "WEB",
         url: "http://lists.fedoraproject.org/pipermail/package-announce/2016-March/178817.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00001.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00002.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00003.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00004.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00005.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00006.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00007.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00009.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00010.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00012.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00025.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00038.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00015.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00017.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00018.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00029.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00030.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00036.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00055.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00019.html",
      },
      {
         type: "WEB",
         url: "http://marc.info/?l=bugtraq&m=145889460330120&w=2",
      },
      {
         type: "WEB",
         url: "http://openssl.org/news/secadv/20160301.txt",
      },
      {
         type: "WEB",
         url: "http://rhn.redhat.com/errata/RHSA-2016-2957.html",
      },
      {
         type: "WEB",
         url: "http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160302-openssl",
      },
      {
         type: "WEB",
         url: "http://www.debian.org/security/2016/dsa-3500",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html",
      },
      {
         type: "WEB",
         url: "http://www.oracle.com/technetwork/topics/security/linuxbulletinjan2016-2867209.html",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1035133",
      },
      {
         type: "WEB",
         url: "http://www.ubuntu.com/usn/USN-2914-1",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.