ghsa-f43f-q929-x2qf
Vulnerability from github
Published
2022-05-17 01:33
Modified
2022-05-17 01:33
Details

GnuPG 1.x before 1.4.16 generates RSA keys using sequences of introductions with certain patterns that introduce a side channel, which allows physically proximate attackers to extract RSA keys via a chosen-ciphertext attack and acoustic cryptanalysis during decryption. NOTE: applications are not typically expected to protect themselves from acoustic side-channel attacks, since this is arguably the responsibility of the physical device. Accordingly, issues of this type would not normally receive a CVE identifier. However, for this issue, the developer has specified a security policy in which GnuPG should offer side-channel resistance, and developer-specified security-policy violations are within the scope of CVE.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2013-4576",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2013-12-20T21:55:00Z",
      severity: "LOW",
   },
   details: "GnuPG 1.x before 1.4.16 generates RSA keys using sequences of introductions with certain patterns that introduce a side channel, which allows physically proximate attackers to extract RSA keys via a chosen-ciphertext attack and acoustic cryptanalysis during decryption. NOTE: applications are not typically expected to protect themselves from acoustic side-channel attacks, since this is arguably the responsibility of the physical device. Accordingly, issues of this type would not normally receive a CVE identifier. However, for this issue, the developer has specified a security policy in which GnuPG should offer side-channel resistance, and developer-specified security-policy violations are within the scope of CVE.",
   id: "GHSA-f43f-q929-x2qf",
   modified: "2022-05-17T01:33:03Z",
   published: "2022-05-17T01:33:03Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2013-4576",
      },
      {
         type: "WEB",
         url: "https://exchange.xforce.ibmcloud.com/vulnerabilities/89846",
      },
      {
         type: "WEB",
         url: "http://lists.gnupg.org/pipermail/gnupg-devel/2013-December/028102.html",
      },
      {
         type: "WEB",
         url: "http://osvdb.org/101170",
      },
      {
         type: "WEB",
         url: "http://rhn.redhat.com/errata/RHSA-2014-0016.html",
      },
      {
         type: "WEB",
         url: "http://seclists.org/oss-sec/2013/q4/520",
      },
      {
         type: "WEB",
         url: "http://seclists.org/oss-sec/2013/q4/523",
      },
      {
         type: "WEB",
         url: "http://www.cs.tau.ac.il/~tromer/acoustic",
      },
      {
         type: "WEB",
         url: "http://www.debian.org/security/2013/dsa-2821",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/64424",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1029513",
      },
      {
         type: "WEB",
         url: "http://www.tau.ac.il/~tromer/papers/acoustic-20131218.pdf",
      },
      {
         type: "WEB",
         url: "http://www.ubuntu.com/usn/USN-2059-1",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
}


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.