| Damien Neil | b5cb765 | 2022-08-18 15:09:12 -0700 | [diff] [blame] | 1 | modules: |
| Tatiana Bradley | 555d995 | 2022-05-24 11:58:05 -0400 | [diff] [blame] | 2 | - module: std |
| Tatiana Bradley | 555d995 | 2022-05-24 11:58:05 -0400 | [diff] [blame] | 3 | versions: |
| 4 | - fixed: 1.12.11 |
| 5 | - introduced: 1.13.0 |
| 6 | fixed: 1.13.2 |
| Damien Neil | b5cb765 | 2022-08-18 15:09:12 -0700 | [diff] [blame] | 7 | packages: |
| 8 | - package: crypto/dsa |
| 9 | symbols: |
| 10 | - Verify |
| Tatiana Bradley | 555d995 | 2022-05-24 11:58:05 -0400 | [diff] [blame] | 11 | description: | |
| 12 | Invalid DSA public keys can cause a panic in dsa.Verify. In particular, |
| 13 | using crypto/x509.Verify on a crafted X.509 certificate chain can lead to a |
| 14 | panic, even if the certificates don't chain to a trusted root. The chain |
| 15 | can be delivered via a crypto/tls connection to a client, or to a server |
| 16 | that accepts and verifies client certificates. net/http clients can be made |
| 17 | to crash by an HTTPS server, while net/http servers that accept client |
| 18 | certificates will recover the panic and are unaffected. |
| 19 | |
| 20 | Moreover, an application might crash invoking |
| 21 | crypto/x509.(*CertificateRequest).CheckSignature on an X.509 certificate |
| 22 | request, parsing a golang.org/x/crypto/openpgp Entity, or during a |
| 23 | golang.org/x/crypto/otr conversation. Finally, a golang.org/x/crypto/ssh |
| 24 | client can panic due to a malformed host key, while a server could panic if |
| 25 | either PublicKeyCallback accepts a malformed public key, or if |
| 26 | IsUserAuthority accepts a certificate with a malformed public key. |
| Damien Neil | 95a417d | 2022-08-17 15:39:45 -0700 | [diff] [blame] | 27 | published: 2022-05-24T20:14:11Z |
| Tatiana Bradley | 555d995 | 2022-05-24 11:58:05 -0400 | [diff] [blame] | 28 | cves: |
| 29 | - CVE-2019-17596 |
| 30 | credit: Daniel Mandragona |
| Damien Neil | 00e94d7 | 2022-08-26 14:59:35 -0700 | [diff] [blame^] | 31 | references: |
| 32 | - fix: https://go.dev/cl/205441 |
| 33 | - fix: https://go.googlesource.com/go/+/552987fdbf4c2bc9641016fd323c3ae5d3a0d9a3 |
| 34 | - report: https://go.dev/issue/34960 |
| 35 | - web: https://groups.google.com/g/golang-announce/c/lVEm7llp0w0/m/VbafyRkgCgAJ |
