data/reports: add GO-2023-2375.yaml
Aliases: CVE-2023-45287
Fixes #2375
Change-Id: I4f3adf4721edcf21acee4fe07a830b8b7af5c872
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/547015
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Tatiana Bradley <tatianabradley@google.com>
diff --git a/data/cve/v5/GO-2023-2375.json b/data/cve/v5/GO-2023-2375.json
new file mode 100644
index 0000000..60318ff
--- /dev/null
+++ b/data/cve/v5/GO-2023-2375.json
@@ -0,0 +1,97 @@
+{
+ "dataType": "CVE_RECORD",
+ "dataVersion": "5.0",
+ "cveMetadata": {
+ "cveId": "CVE-2023-45287"
+ },
+ "containers": {
+ "cna": {
+ "providerMetadata": {
+ "orgId": "1bb62c36-49e3-4200-9d77-64a1400537cc"
+ },
+ "title": "Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel",
+ "descriptions": [
+ {
+ "lang": "en",
+ "value": "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."
+ }
+ ],
+ "affected": [
+ {
+ "vendor": "Go standard library",
+ "product": "crypto/tls",
+ "collectionURL": "https://pkg.go.dev",
+ "packageName": "crypto/tls",
+ "versions": [
+ {
+ "version": "0",
+ "lessThan": "1.20.0",
+ "status": "affected",
+ "versionType": "semver"
+ }
+ ],
+ "programRoutines": [
+ {
+ "name": "rsaKeyAgreement.processClientKeyExchange"
+ },
+ {
+ "name": "rsaKeyAgreement.generateClientKeyExchange"
+ },
+ {
+ "name": "Conn.Handshake"
+ },
+ {
+ "name": "Conn.HandshakeContext"
+ },
+ {
+ "name": "Conn.Read"
+ },
+ {
+ "name": "Conn.Write"
+ },
+ {
+ "name": "Dial"
+ },
+ {
+ "name": "DialWithDialer"
+ },
+ {
+ "name": "Dialer.Dial"
+ },
+ {
+ "name": "Dialer.DialContext"
+ }
+ ],
+ "defaultStatus": "unaffected"
+ }
+ ],
+ "problemTypes": [
+ {
+ "descriptions": [
+ {
+ "lang": "en",
+ "description": "CWE-208: Observable Timing Discrepancy"
+ }
+ ]
+ }
+ ],
+ "references": [
+ {
+ "url": "https://go.dev/issue/20654"
+ },
+ {
+ "url": "https://go.dev/cl/326012/26"
+ },
+ {
+ "url": "https://groups.google.com/g/golang-announce/c/QMK8IQALDvA"
+ },
+ {
+ "url": "https://people.redhat.com/~hkario/marvin/"
+ },
+ {
+ "url": "https://pkg.go.dev/vuln/GO-2023-2375"
+ }
+ ]
+ }
+ }
+}
\ No newline at end of file
diff --git a/data/osv/GO-2023-2375.json b/data/osv/GO-2023-2375.json
new file mode 100644
index 0000000..557bb8c
--- /dev/null
+++ b/data/osv/GO-2023-2375.json
@@ -0,0 +1,72 @@
+{
+ "schema_version": "1.3.1",
+ "id": "GO-2023-2375",
+ "modified": "0001-01-01T00:00:00Z",
+ "published": "0001-01-01T00:00:00Z",
+ "aliases": [
+ "CVE-2023-45287"
+ ],
+ "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.\n\nIn 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.",
+ "affected": [
+ {
+ "package": {
+ "name": "stdlib",
+ "ecosystem": "Go"
+ },
+ "ranges": [
+ {
+ "type": "SEMVER",
+ "events": [
+ {
+ "introduced": "0"
+ },
+ {
+ "fixed": "1.20.0"
+ }
+ ]
+ }
+ ],
+ "ecosystem_specific": {
+ "imports": [
+ {
+ "path": "crypto/tls",
+ "symbols": [
+ "Conn.Handshake",
+ "Conn.HandshakeContext",
+ "Conn.Read",
+ "Conn.Write",
+ "Dial",
+ "DialWithDialer",
+ "Dialer.Dial",
+ "Dialer.DialContext",
+ "rsaKeyAgreement.generateClientKeyExchange",
+ "rsaKeyAgreement.processClientKeyExchange"
+ ]
+ }
+ ]
+ }
+ }
+ ],
+ "references": [
+ {
+ "type": "REPORT",
+ "url": "https://go.dev/issue/20654"
+ },
+ {
+ "type": "FIX",
+ "url": "https://go.dev/cl/326012/26"
+ },
+ {
+ "type": "WEB",
+ "url": "https://groups.google.com/g/golang-announce/c/QMK8IQALDvA"
+ },
+ {
+ "type": "ARTICLE",
+ "url": "https://people.redhat.com/~hkario/marvin/"
+ }
+ ],
+ "database_specific": {
+ "url": "https://pkg.go.dev/vuln/GO-2023-2375"
+ }
+}
\ No newline at end of file
diff --git a/data/reports/GO-2023-2375.yaml b/data/reports/GO-2023-2375.yaml
new file mode 100644
index 0000000..c88cca3
--- /dev/null
+++ b/data/reports/GO-2023-2375.yaml
@@ -0,0 +1,40 @@
+id: GO-2023-2375
+modules:
+ - module: std
+ versions:
+ - fixed: 1.20.0
+ vulnerable_at: 1.19.0
+ packages:
+ - package: crypto/tls
+ symbols:
+ - rsaKeyAgreement.processClientKeyExchange
+ - rsaKeyAgreement.generateClientKeyExchange
+ derived_symbols:
+ - Conn.Handshake
+ - Conn.HandshakeContext
+ - Conn.Read
+ - Conn.Write
+ - Dial
+ - DialWithDialer
+ - Dialer.Dial
+ - Dialer.DialContext
+summary: |-
+ Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a
+ timing side channel
+description: |-
+ 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.
+references:
+ - report: https://go.dev/issue/20654
+ - fix: https://go.dev/cl/326012/26
+ - web: https://groups.google.com/g/golang-announce/c/QMK8IQALDvA
+ - article: https://people.redhat.com/~hkario/marvin/
+cve_metadata:
+ id: CVE-2023-45287
+ cwe: 'CWE-208: Observable Timing Discrepancy'
