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
processing being enabled on a publicly facing server is not considered
to be a common setup.
Policy processing is enabled by passing the -policy' argument to the command line utilities or by calling the
X509_VERIFY_PARAM_set1_policies()’ function.
Update (31 March 2023): The description of the policy processing enablement
was corrected based on CVE-2023-0466.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Alpine | edge-main | noarch | openssl | < 3.0.7-r2 | UNKNOWN |
Alpine | 3.15-main | noarch | openssl3 | < 3.0.8-r0 | UNKNOWN |
Alpine | 3.16-main | noarch | openssl3 | < 3.0.8-r0 | UNKNOWN |
Alpine | 3.17-main | noarch | openssl | < 3.0.7-r2 | UNKNOWN |
Alpine | 3.18-main | noarch | openssl | < 3.0.7-r2 | UNKNOWN |
Alpine | 3.19-main | noarch | openssl | < 3.0.7-r2 | UNKNOWN |
Alpine | 3.20-main | noarch | openssl | < 3.0.7-r2 | UNKNOWN |