CVE-2023-45287

{"id": "CVE-2023-45287", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2023-12-05T17:15:08.570", "references": [{"url": "https://go.dev/cl/326012/26", "tags": ["Issue Tracking"], "source": "security@golang.org"}, {"url": "https://go.dev/issue/20654", "tags": ["Issue Tracking"], "source": "security@golang.org"}, {"url": "https://groups.google.com/g/golang-announce/c/QMK8IQALDvA", "tags": ["Mailing List", "Release Notes"], "source": "security@golang.org"}, {"url": "https://people.redhat.com/~hkario/marvin/", "tags": ["Third Party Advisory"], "source": "security@golang.org"}, {"url": "https://pkg.go.dev/vuln/GO-2023-2375", "tags": ["Vendor Advisory"], "source": "security@golang.org"}, {"url": "https://security.netapp.com/advisory/ntap-20240112-0005/", "source": "security@golang.org"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-203"}]}], "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."}, {"lang": "es", "value": "Antes de Go 1.20, los intercambios de claves TLS basados en RSA utilizaban la librer\u00eda math/big, que no es un tiempo constante. Se aplic\u00f3 blinding RSA para prevenir ataques sincronizados, pero el an\u00e1lisis muestra que esto puede no haber sido completamente efectivo. En particular, parece que la eliminaci\u00f3n del relleno PKCS#1 puede filtrar informaci\u00f3n de tiempo, que a su vez podr\u00eda usarse para recuperar bits de clave de sesi\u00f3n. En Go 1.20, la librer\u00eda crypto/tls cambi\u00f3 a una implementaci\u00f3n RSA de tiempo completamente constante, que no creemos que muestre ning\u00fan canal lateral de temporizaci\u00f3n."}], "lastModified": "2024-01-12T14:15:48.310", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "A96BDB4B-F1DA-4948-8E56-8B4933BB8BC2", "versionEndExcluding": "1.20.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@golang.org"}