ALPINE-CVE-2022-3786
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Alpine:v3.18 | openssl | *, 3.0.2-r0, 3.0.1-r1 |
| Alpine:v3.16 | openssl3 | 3.0.5-r1, 3.0.0-r3, 3.0.0-r4 |
| Alpine:v3.22 | nodejs | 0, 0, 0 |
| Alpine:v3.24 | openssl | 3.0.0, 3.0.0 |
| Alpine:v3.24 | nodejs | 0, 0 |
| Alpine:v3.20 | nodejs | 6.10.3-r0, 6.11.0-r0, 6.11.1-r0 |
| Alpine:v3.19 | openssl | 1.1.1-r5, 1.1.1-r3, 1.1.1-r2 |
| Alpine:v3.15 | openssl3 | 3.0.5-r1, 3.0.5-r0, 3.0.3-r0 |
| Alpine:v3.20 | openssl | 1.1.1a-r0, 1.1.1-r3, 1.1.1-r2 |
| Alpine:v3.21 | nodejs | 0, 0, 0 |
| Alpine:v3.23 | nodejs | 0, 0, 0 |
| Alpine:v3.18 | nodejs | 0, 0, 10.14.0-r0 |
| Alpine:v3.19 | nodejs | 16.14.2-r1, 12.18.2-r0, 12.18.0-r2 |
| Alpine:v3.21 | openssl | 1.1.1, 1.1.1-r5, 1.1.1-r4 |
| Alpine:v3.22 | openssl | 1.1.1-r2, 1.1.1-r1, 1.1.1-r0 |
| Alpine:v3.17 | openssl | 1.1.1a-r0, 0, 3.0.0 |
| Alpine:v3.23 | openssl | 1.1.1-r0, 1.1.1-r2, 1.1.1b-r1 |
| Alpine:v3.17 | nodejs | 8.10.0-r0, 6.9.5-r1, 6.9.5-r0 |
Timeline
- Nov 1, 2022 CVE Published
- Jul 8, 2026 CVE Updated
- Aug 8, 2026 Distribution Patch