apk package
chainguard/openssl-provider-fips
pkg:apk/chainguard/openssl-provider-fips
Vulnerabilities (43)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-0401 | — | < 3.0.8-r0 | 3.0.8-r0 | Feb 8, 2023 | A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initializat | ||
| CVE-2022-3996 | — | < 3.0.8-r0 | 3.0.8-r0 | Dec 13, 2022 | If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results in a denial of service when the affected process hangs. Policy proce | ||
| CVE-2022-3602 | Hig | 7.5 | < 3.0.8-r0 | 3.0.8-r0 | Nov 1, 2022 | 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 the malicious certificate or for the application to continue |
- CVE-2023-0401Feb 8, 2023affected < 3.0.8-r0fixed 3.0.8-r0
A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initializat
- CVE-2022-3996Dec 13, 2022affected < 3.0.8-r0fixed 3.0.8-r0
If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results in a denial of service when the affected process hangs. Policy proce
- affected < 3.0.8-r0fixed 3.0.8-r0
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 the malicious certificate or for the application to continue
Page 3 of 3