Vulnerability from bitnami_vulndb
Published
2024-03-06 10:52
Modified
2025-05-20 10:02
Summary
Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel
Details

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "golang",
        "purl": "pkg:bitnami/golang"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.20.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-45287"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.",
  "id": "BIT-golang-2023-45287",
  "modified": "2025-05-20T10:02:07.006Z",
  "published": "2024-03-06T10:52:27.963Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://go.dev/cl/326012/26"
    },
    {
      "type": "WEB",
      "url": "https://go.dev/issue/20654"
    },
    {
      "type": "WEB",
      "url": "https://groups.google.com/g/golang-announce/c/QMK8IQALDvA"
    },
    {
      "type": "WEB",
      "url": "https://people.redhat.com/~hkario/marvin/"
    },
    {
      "type": "WEB",
      "url": "https://pkg.go.dev/vuln/GO-2023-2375"
    },
    {
      "type": "WEB",
      "url": "https://security.netapp.com/advisory/ntap-20240112-0005/"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-45287"
    }
  ],
  "schema_version": "1.5.0",
  "summary": "Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.