{"id":"CVE-2021-3450","aliases":["ALPINE-CVE-2021-3450","BELL-CVE-2021-3450","BIT-node-2021-3450","BIT-node-min-2021-3450","DEBIAN-CVE-2021-3450","EUVD-2021-1641","GHSA-8hfj-xrj2-pm22","MGASA-2021-0176","OESA-2022-1620","RHSA-2021:1024","RHSA-2021:1189","RHSA-2021:1195","RHSA-2021:1199","RHSA-2021:1202","RLSA-2021:1024","RUSTSEC-2021-0056","SUSE-SU-2021:2323-1","SUSE-SU-2021:2326-1","SUSE-SU-2021:2327-1","SUSE-SU-2021:2353-1","UBUNTU-CVE-2021-3450","openSUSE-SU-2021:1059-1","openSUSE-SU-2021:1061-1","openSUSE-SU-2021:2327-1","openSUSE-SU-2021:2353-1","openSUSE-SU-2024:11127-1"],"status":"published","title":"CA certificate check bypass with X509_V_FLAG_X509_STRICT","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","severity":{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.18339,"percentile":0.97246,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-295"],"published":"2021-03-25T00:00:00Z","modified":"2026-11-03T06:32:40Z","exploits":[{"source":"pocgithub","id":"dedellix/MUT-BC-SS-01","title":"dedellix/MUT-BC-SS-01","date":"2026-06-23","url":"https://github.com/dedellix/MUT-BC-SS-01"}],"fixes":[{"ecosystem":"crates.io","package":"openssl-src","fixed_in":["111.15.0"],"sources":["ghsa","osv"]},{"ecosystem":"Alpine:v3.10","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.11","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.12","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.13","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.14","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.9","package":"openssl","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"openssl1.1-compat","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"openssl1.1-compat","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"openssl3","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"openssl3","fixed_in":["1.1.1k-r0"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"node","fixed_in":["10.24.1","12.22.1","14.16.1","15.14.0"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"node-min","fixed_in":["10.24.1","12.22.1","14.16.1","15.14.0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"openssl","fixed_in":["1.1.1k-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"openssl","fixed_in":["1.1.1k-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"openssl","fixed_in":["1.1.1k-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"111.11.0"},{"fixed":"111.15.0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.10","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.11","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.12","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.13","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.14","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.9","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.1.1h"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"openssl1.1-compat","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"openssl1.1-compat","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"openssl3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"openssl3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-r0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"node","ranges":[{"type":"SEMVER","events":[{"introduced":"10.0.0"},{"fixed":"10.24.1"},{"introduced":"12.0.0"},{"fixed":"12.22.1"},{"introduced":"14.0.0"},{"fixed":"14.16.1"},{"introduced":"15.0.0"},{"fixed":"15.14.0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"node-min","ranges":[{"type":"SEMVER","events":[{"introduced":"10.0.0"},{"fixed":"10.24.1"},{"introduced":"12.0.0"},{"fixed":"12.22.1"},{"introduced":"14.0.0"},{"fixed":"14.16.1"},{"introduced":"15.0.0"},{"fixed":"15.14.0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"111.11.0"},{"fixed":"111.15.0"}]}]},{"source":"osv","ecosystem":"Mageia:8","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1k-1.mga8"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-1.oe1"}]}],"bundled":12},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP2","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-1.oe1"}]}],"bundled":12},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.11-1.oe1"}]}],"bundled":12},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-debugsource","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-libs-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:8::baseos","package":"openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_hypervisor:4.4::el8","package":"redhat-virtualization-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.4.5-20210330.0.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_hypervisor:4.4::el8","package":"redhat-virtualization-host-image-update","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.4.5-20210330.0.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.4::el7","package":"jws5-tomcat-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.25-4.redhat_4.el7jws"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.4::el7","package":"jws5-tomcat-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.25-4.redhat_4.el7jws"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.4::el8","package":"jws5-tomcat-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.25-4.redhat_4.el8jws"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:5.4::el8","package":"jws5-tomcat-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.25-4.redhat_4.el8jws"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-manual","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-selinux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-httpd-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_cluster-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.3.14-20.Final_redhat_2.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_cluster-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.3.14-20.Final_redhat_2.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_http2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.15.7-14.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_http2-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.15.7-14.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_jk","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.48-13.redhat_1.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_jk-ap24","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.48-13.redhat_1.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_jk-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.48-13.redhat_1.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_jk-manual","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.48-13.redhat_1.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_md","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.0.8-33.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_md-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.0.8-33.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_proxy_html","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.9.2-60.GA.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_security-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.9.2-60.GA.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_session","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-mod_ssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.37-70.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-nghttp2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.39.2-37.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-nghttp2-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.39.2-37.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-nghttp2-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.39.2-37.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-6.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-chil","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.0.0-5.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-chil-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.0.0-5.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-6.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-6.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-6.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-perl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-6.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-pkcs11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.4.10-20.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-pkcs11-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:0.4.10-20.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_core_services:1::el7","package":"jbcs-httpd24-openssl-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-6.jbcs.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:3.1::el7","package":"tomcat-native","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.23-24.redhat_24.ep7.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:jboss_enterprise_web_server:3.1::el7","package":"tomcat-native-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.2.23-24.redhat_24.ep7.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Rocky Linux:8","package":"openssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.1.1g-15.el8_3"}]}],"bundled":2},{"source":"osv","ecosystem":"crates.io","package":"openssl-src","ranges":[{"type":"SEMVER","events":[{"introduced":"111.11.0"},{"fixed":"111.15.0"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 12","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.39.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 12","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-1.32.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP2","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-4.16.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP3","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-4.16.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP2","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-ESPOS","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-LTSS","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15-LTSS","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP1-BCL","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP1-LTSS","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP1","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.0","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Manager Retail Branch Server 4.0","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Manager Server 4.0","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 6","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-lp152.3.15.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-lp152.2.15.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-4.16.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"nodejs10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.24.1-1.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"openssl-1_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1l-1.2"}]}],"bundled":136}],"products":[{"vendor":"fedoraproject","product":"fedora"},{"vendor":"freebsd","product":"freebsd"},{"vendor":"mcafee","product":"web_gateway"},{"vendor":"mcafee","product":"web_gateway_cloud_service"},{"vendor":"netapp","product":"cloud_volumes_ontap_mediator"},{"vendor":"netapp","product":"oncommand_workflow_automation"},{"vendor":"netapp","product":"ontap_select_deploy_administration_utility"},{"vendor":"netapp","product":"santricity_smi-s_provider_firmware"},{"vendor":"netapp","product":"storagegrid"},{"vendor":"netapp","product":"storagegrid_firmware"},{"vendor":"nodejs","product":"node.js"},{"vendor":"openssl","product":"openssl"},{"vendor":"oracle","product":"commerce_guided_search"},{"vendor":"oracle","product":"enterprise_manager_for_storage_management"},{"vendor":"oracle","product":"graalvm"},{"vendor":"oracle","product":"jd_edwards_enterpriseone_tools"},{"vendor":"oracle","product":"jd_edwards_world_security"},{"vendor":"oracle","product":"mysql_connectors"},{"vendor":"oracle","product":"mysql_enterprise_monitor"},{"vendor":"oracle","product":"mysql_server"},{"vendor":"oracle","product":"mysql_workbench"},{"vendor":"oracle","product":"peoplesoft_enterprise_peopletools"},{"vendor":"oracle","product":"secure_backup"},{"vendor":"oracle","product":"secure_global_desktop"},{"vendor":"oracle","product":"weblogic_server"},{"vendor":"sonicwall","product":"capture_client"},{"vendor":"sonicwall","product":"email_security"},{"vendor":"sonicwall","product":"sma100_firmware"},{"vendor":"sonicwall","product":"sonicos"},{"vendor":"tenable","product":"nessus"},{"vendor":"tenable","product":"nessus_agent"},{"vendor":"tenable","product":"nessus_network_monitor"},{"vendor":"windriver","product":"linux"}],"references":[{"url":"https://www.openssl.org/news/secadv/20210325.txt","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","web","article","report"]},{"url":"https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=2a40b7bc7b94dd7de897a74571e7024f0cf0d63b","tags":["x_refsource_CONFIRM","x_transferred","web"]},{"url":"https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-openssl-2021-GHY28dJd","tags":["vendor-advisory","x_refsource_CISCO","x_transferred","Third Party Advisory","advisory","web"]},{"url":"http://www.openwall.com/lists/oss-security/2021/03/27/1","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"http://www.openwall.com/lists/oss-security/2021/03/27/2","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"http://www.openwall.com/lists/oss-security/2021/03/28/3","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"http://www.openwall.com/lists/oss-security/2021/03/28/4","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://security.gentoo.org/glsa/202103-03","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CCBFLLVQVILIVGZMBJL3IXZGKWQISYNP/","tags":["vendor-advisory","x_refsource_FEDORA","x_transferred","web"]},{"url":"https://www.oracle.com/security-alerts/cpuApr2021.html","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://www.tenable.com/security/tns-2021-09","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://security.netapp.com/advisory/ntap-20210326-0006/","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory"]},{"url":"https://security.FreeBSD.org/advisories/FreeBSD-SA-21:07.openssl.asc","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://www.tenable.com/security/tns-2021-05","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10356","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://www.tenable.com/security/tns-2021-08","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://mta.openssl.org/pipermail/openssl-announce/2021-March/000198.html","tags":["x_refsource_MISC","x_transferred","Mailing List","Vendor Advisory","advisory","web"]},{"url":"https://www.oracle.com//security-alerts/cpujul2021.html","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44845","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0013","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://www.oracle.com/security-alerts/cpuoct2021.html","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://www.oracle.com/security-alerts/cpuapr2022.html","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://www.oracle.com/security-alerts/cpujul2022.html","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","advisory","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-3450","tags":["web","advisory"]},{"url":"https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2a40b7bc7b94dd7de897a74571e7024f0cf0d63b","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CCBFLLVQVILIVGZMBJL3IXZGKWQISYNP/"},{"url":"https://rustsec.org/advisories/RUSTSEC-2021-0056.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-8hfj-xrj2-pm22"},{"url":"https://security.alpinelinux.org/vuln/CVE-2021-3450","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2021-3450","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-3450","tags":["advisory"]},{"url":"https://security.netapp.com/advisory/ntap-20210326-0006","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CCBFLLVQVILIVGZMBJL3IXZGKWQISYNP","tags":["web"]},{"url":"https://github.com/alexcrichton/openssl-src-rs","tags":["package"]},{"url":"https://advisories.mageia.org/MGASA-2021-0176.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=28640","tags":["report"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1620","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-44532","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-44533","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-44531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-27290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-22921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-39134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-39135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-22959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-22960","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2021:1024","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1941547","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1941554","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_1024.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-3449","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-3449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-3449","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2021-3450","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-3450","tags":["advisory","report"]},{"url":"https://access.redhat.com/errata/RHSA-2021:1189","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1892573","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1895832","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1907306","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1907358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1907746","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1918207","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1927395","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1928607","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1940845","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1942040","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1942498","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_1189.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2021:1195","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_1195.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2021:1199","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_1199.json","tags":["advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2021:1202","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_1202.json","tags":["advisory"]},{"url":"https://errata.rockylinux.org/RLSA-2021:1024","tags":["advisory"]},{"url":"https://crates.io/crates/openssl-src","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212323-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1183155","tags":["report"]},{"url":"https://bugzilla.suse.com/1183851","tags":["report"]},{"url":"https://bugzilla.suse.com/1183852","tags":["report"]},{"url":"https://bugzilla.suse.com/1184450","tags":["report"]},{"url":"https://bugzilla.suse.com/1187973","tags":["report"]},{"url":"https://bugzilla.suse.com/1187976","tags":["report"]},{"url":"https://bugzilla.suse.com/1187977","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2020-7774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-23362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-27290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3450","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212326-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212327-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212353-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-3450","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/4ZO2DR7PIGZWRPXIGYAZCAL4X64BSDZJ/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/SR22RRAXGLDTLSDJRAQ4O3Q67G2PNEGJ/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/OFQOZ4RLN343RY5DDFVA2KWFMZHZD2KS/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/SVLFLECFVPSHO4SQBVWDO2CBAU5LB7IS/","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2006-2937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-2940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-3738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-4339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-4343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2006-7250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2007-3108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2007-5135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2008-0891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2008-1672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2008-5077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-0590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-0591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-0789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-1377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-1378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-1379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-1386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2009-1387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2010-0740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2010-0742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2010-1633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2010-2939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2010-3864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2010-5298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2011-0014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2011-3207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2011-4108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2011-4576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2011-4577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2011-4619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-0027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-0050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-0884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-1165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-2110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-2686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2012-4929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2013-0166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2013-0169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2013-4353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2013-6449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2013-6450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-5139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-8275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-0293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-3197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-0701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-0702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-0705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-0797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-0798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-0800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-2183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-3731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-3732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-3735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-3736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-3738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-0732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-0734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-0735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-0737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-0739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-1543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-1547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-1549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-1551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-1563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-1967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-1971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-23840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-23841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3712","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2021-3450","title":"CA certificate check bypass with X509_V_FLAG_X509_STRICT","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-03-25T14:25:14.287Z","modified":"2026-10-08T21:03:32.498Z","updated_at":"2026-11-02T14:33:03.671751Z"}],"euvd":[{"id":"EUVD-2021-1641","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-03-25T14:25:14Z","modified":"2026-10-08T21:03:32Z","updated_at":"2026-11-02T17:27:26.856493Z"}],"ghsa":[{"id":"GHSA-8hfj-xrj2-pm22","title":"Certificate check bypass in openssl-src","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-08-25T20:54:00Z","modified":"2023-08-04T18:38:55Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T14:36:59.456342Z"}],"nvd":[{"id":"CVE-2021-3450","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-03-25T15:15:13.56Z","modified":"2026-10-08T21:17:40.07Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"primary"},{"version":"2.0","score":5.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T14:06:51.197859Z"}],"osv":[{"id":"ALPINE-CVE-2021-3450","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-03-25T15:15:13.56Z","modified":"2026-11-03T06:32:40.663107436Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-03T07:17:02.90744Z"},{"id":"BELL-CVE-2021-3450","title":"CVE-2021-3450 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:13:50.740283Z","modified":"2026-01-26T09:49:05.151992Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:28:16.5265Z"},{"id":"CVE-2021-3450","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-03-25T15:15:13.56Z","modified":"2026-10-24T14:18:06.617630497Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:44:20.13324Z"},{"id":"DEBIAN-CVE-2021-3450","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-03-25T15:15:13.56Z","modified":"2026-10-09T09:47:33.871940694Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:45:35.233346Z"},{"id":"GHSA-8hfj-xrj2-pm22","title":"Certificate check bypass in openssl-src","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2021-08-25T20:54:00Z","modified":"2024-12-16T15:27:14.677621Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T15:46:42.437513Z"},{"id":"OESA-2022-1620","title":"nodejs security update","description":"Node.js is a platform built on Chrome\u0026apos;s JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.\r\n\r\n\r\n\r\nSecurity Fix(es):\r\n\r\nAn issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)(CVE-2020-15366)\r\n\r\nThe X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \u0026quot;purpose\u0026quot; has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \u0026quot;purpose\u0026quot; values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).(CVE-2021-3450)\r\n\r\nNode.js \u0026lt; 12.22.9, \u0026lt; 14.18.3, \u0026lt; 16.13.2, and \u0026lt; 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.(CVE-2021-44532)\r\n\r\nNode.js \u0026lt; 12.22.9, \u0026lt; 14.18.3, \u0026lt; 16.13.2, and \u0026lt; 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node\u0026apos;s ambiguous presentation of certificate subjects may be vulnerable.(CVE-2021-44533)\r\n\r\nAccepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js \u0026lt; 12.22.9, \u0026lt; 14.18.3, \u0026lt; 16.13.2, and \u0026lt; 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.(CVE-2021-44531)\r\n\r\nDue to the formatting logic of the \u0026quot;console.table()\u0026quot; function it was not safe to allow user controlled input to be passed to the \u0026quot;properties\u0026quot; parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be \u0026quot;__proto__\u0026quot;. The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.Node.js \u0026gt;= 12.22.9, \u0026gt;= 14.18.3, \u0026gt;= 16.13.2, and \u0026gt;= 17.3.1 use a null protoype for the object these properties are being assigned to.(CVE-2022-21824)\r\n\r\nssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.(CVE-2021-27290)\r\n\r\nNode.js before 16.4.1, 14.17.2, and 12.22.2 is vulnerable to local privilege escalation attacks under certain conditions on Windows platforms. More specifically, improper configuration of permissions in the installation directory allows an attacker to perform two different escalation attacks: PATH and DLL hijacking.(CVE-2021-22921)\r\n\r\n`@npmcli/arborist`, the library that calculates dependency trees and manages the `node_modules` folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is, in part, accomplished by resolving dependency specifiers defined in `package.json` manifests for dependencies with a specific name, and nesting folders to resolve conflicting dependencies. When multiple dependencies differ only in the case of their name, Arborist\u0026apos;s internal data structure saw them as separate items that could coexist within the same level in the `node_modules` hierarchy. However, on case-insensitive file systems (such as macOS and Windows), this is not the case. Combined with a symlink dependency such as `file:/some/path`, this allowed an attacker to create a situation in which arbitrary contents could be written to any location on the filesystem. For example, a package `pwn-a` could define a dependency in their `package.json` file such as `\u0026quot;foo\u0026quot;: \u0026quot;file:/some/path\u0026quot;`. Another package, `pwn-b` could define a dependency such as `FOO: \u0026quot;file:foo.tgz\u0026quot;`. On case-insensitive file systems, if `pwn-a` was installed, and then `pwn-b` was installed afterwards, the contents of `foo.tgz` would be written to `/some/path`, and any existing contents of `/some/path` would be removed. Anyone using npm v7.20.6 or earlier on a case-insensitive filesystem is potentially affected. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above.(CVE-2021-39134)\r\n\r\n`@npmcli/arborist`, the library that calculates dependency trees and manages the node_modules folder hierarchy for the npm command line interface, aims to guarantee that package dependency contracts will be met, and the extraction of package contents will always be performed into the expected folder. This is accomplished by extracting package contents into a project\u0026apos;s `node_modules` folder. If the `node_modules` folder of the root project or any of its dependencies is somehow replaced with a symbolic link, it could allow Arborist to write package dependencies to any arbitrary location on the file system. Note that symbolic links contained within package artifact contents are filtered out, so another means of creating a `node_modules` symbolic link would have to be employed. 1. A `preinstall` script could replace `node_modules` with a symlink. (This is prevented by using `--ignore-scripts`.) 2. An attacker could supply the target with a git repository, instructing them to run `npm install --ignore-scripts` in the root. This may be successful, because `npm install --ignore-scripts` is typically not capable of making changes outside of the project directory, so it may be deemed safe. This is patched in @npmcli/arborist 2.8.2 which is included in npm v7.20.7 and above. For more information including workarounds please see the referenced GHSA-gmw6-94gg-2rc2.(CVE-2021-39135)\r\n\r\nThe parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp \u0026lt; v2.1.4 and \u0026lt; v6.0.6.(CVE-2021-22959)\r\n\r\nThe parse function in llhttp \u0026lt; 2.1.4 and \u0026lt; 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.(CVE-2021-22960)","status":"published","published":"2022-04-29T11:04:53Z","modified":"2026-08-18T01:16:29.96930633Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:39.528805Z"},{"id":"RHSA-2021:1024","title":"Red Hat Security Advisory: openssl security update","status":"published","published":"2024-09-13T20:24:54Z","modified":"2026-10-09T10:02:18Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:08.071325Z"},{"id":"RHSA-2021:1189","title":"Red Hat Security Advisory: Red Hat Virtualization security, bug fix, and enhancement update","status":"published","published":"2024-09-13T20:25:20Z","modified":"2026-10-09T10:02:20Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:08.071325Z"},{"id":"RHSA-2021:1195","title":"Red Hat Security Advisory: Red Hat JBoss Web Server 5.4.2 Security Update","status":"published","published":"2024-09-13T20:25:27Z","modified":"2026-10-09T10:02:20Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:08.071325Z"},{"id":"RHSA-2021:1199","title":"Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.37 SP7 security update","status":"published","published":"2024-09-13T20:25:32Z","modified":"2026-10-09T10:02:21Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:08.071325Z"},{"id":"RHSA-2021:1202","title":"Red Hat Security Advisory: Red Hat JBoss Web Server 3.1 Service Pack 12 security update","status":"published","published":"2024-09-13T20:25:44Z","modified":"2026-10-09T10:02:22Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:08.071325Z"},{"id":"RLSA-2021:1024","title":"Important: openssl security update","description":"OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: NULL pointer dereference in signature_algorithms processing (CVE-2021-3449)\n\n* openssl: CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.","status":"published","published":"2021-03-29T19:03:22Z","modified":"2026-02-05T09:45:06.801281Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:23.969672Z"},{"id":"RUSTSEC-2021-0056","title":"CA certificate check bypass with X509_V_FLAG_X509_STRICT","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the\ncertificates present in a certificate chain. It is not set by default.\n\nStarting from OpenSSL version 1.1.1h a check to disallow certificates in\nthe chain that have explicitly encoded elliptic curve parameters was added\nas an additional strict check.\n\nAn error in the implementation of this check meant that the result of a\nprevious check to confirm that certificates in the chain are valid CA\ncertificates was overwritten. This effectively bypasses the check\nthat non-CA certificates must not be able to issue other certificates.\n\nIf a \"purpose\" has been configured then there is a subsequent opportunity\nfor checks that the certificate is a valid CA.  All of the named \"purpose\"\nvalues implemented in libcrypto perform this check.  Therefore, where\na purpose is set the certificate chain will still be rejected even when the\nstrict flag has been used. A purpose is set by default in libssl client and\nserver certificate verification routines, but it can be overridden or\nremoved by an application.\n\nIn order to be affected, an application must explicitly set the\nX509_V_FLAG_X509_STRICT verification flag and either not set a purpose\nfor the certificate verification or, in the case of TLS client or server\napplications, override the default purpose.","status":"published","published":"2021-05-01T12:00:00Z","modified":"2024-12-16T15:27:14.677621Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:39.492624Z"},{"id":"UBUNTU-CVE-2021-3450","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"withdrawn","published":"2021-03-25T00:00:00Z","modified":"2025-07-16T07:19:52.802688Z","cvss":[{"version":"3.1","score":7.4,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:54:27.870979Z"},{"id":"BIT-node-2021-3450","title":"CA certificate check bypass with X509_V_FLAG_X509_STRICT","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2024-03-06T11:05:36.509Z","modified":"2026-10-16T09:45:20.686365481Z","updated_at":"2026-11-02T15:28:34.007508Z"},{"id":"BIT-node-min-2021-3450","title":"CA certificate check bypass with X509_V_FLAG_X509_STRICT","description":"The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a \"purpose\" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named \"purpose\" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).","status":"published","published":"2024-12-16T14:04:21.219Z","modified":"2026-10-16T09:45:28.314985464Z","updated_at":"2026-11-02T15:28:34.007508Z"},{"id":"MGASA-2021-0176","title":"Updated openssl packages fix security vulnerability","description":"An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation\nClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits\nthe signature_algorithms extension (where it was present in the initial\nClientHello), but includes a signature_algorithms_cert extension then a NULL\npointer dereference will result, leading to a crash and a denial of service\nattack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled\n(which is the default configuration). OpenSSL TLS clients are not impacted by\nthis issue. (CVE-2021-3449).\n\nThe X509_V_FLAG_X509_STRICT flag enables additional security checks of the\ncertificates present in a certificate chain. It is not set by default.\nStarting from OpenSSL version 1.1.1h a check to disallow certificates in the\nchain that have explicitly encoded elliptic curve parameters was added as an\nadditional strict check. An error in the implementation of this check meant\nthat the result of a previous check to confirm that certificates in the chain\nare valid CA certificates was overwritten. This effectively bypasses the check\nthat non-CA certificates must not be able to issue other certificates. If a\n\"purpose\" has been configured then there is a subsequent opportunity for checks\nthat the certificate is a valid CA. All of the named \"purpose\" values \nimplemented in libcrypto perform this check. Therefore, where a purpose is set\nthe certificate chain will still be rejected even when the strict flag has been\nused. A purpose is set by default in libssl client and server certificate\nverification routines, but it can be overridden or removed by an application.\nIn order to be affected, an application must explicitly set the\nX509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the\ncertificate verification or, in the case of TLS client or server applications,\noverride the default purpose. (CVE-2021-3450).\n","status":"published","published":"2021-04-05T15:54:07Z","modified":"2026-04-16T04:42:02.397715215Z","updated_at":"2026-11-02T15:49:41.509337Z"},{"id":"openSUSE-SU-2021:1059-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- update to 12.22.2:\n- CVE-2021-22918: Out of bounds read (bsc#1187973)\n- CVE-2021-23362: ssri Regular Expression Denial of Service and hosted-git-info (bsc#1187977)\n- CVE-2021-27290: Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- CVE-2020-7774: npm - Update y18n to fix Prototype-Pollution (bsc#1184450)\n\nThis update was imported from the SUSE:SLE-15-SP2:Update update project.","status":"published","published":"2021-07-19T21:03:47Z","modified":"2026-02-04T03:36:33.643807Z","updated_at":"2026-11-02T16:58:31.879684Z"},{"id":"openSUSE-SU-2021:1061-1","title":"Security update for nodejs10","description":"This update for nodejs10 fixes the following issues:\n\nUpdate nodejs10 to 10.24.1.\n\nIncluding fixes for \n\n- CVE-2021-22918: libuv upgrade - Out of bounds read (bsc#1187973)\n- CVE-2021-27290: ssri Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-23362: hosted-git-info Regular Expression Denial of Service (bsc#1187977)\n- CVE-2020-7774: y18n Prototype Pollution (bsc#1184450)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- reduce memory footprint of test-worker-stdio (bsc#1183155)\n\nThis update was imported from the SUSE:SLE-15:Update update project.","status":"published","published":"2021-07-19T21:03:56Z","modified":"2026-02-04T03:25:11.06458Z","updated_at":"2026-11-02T16:58:31.879684Z"},{"id":"openSUSE-SU-2021:2327-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- update to 12.22.2:\n- CVE-2021-22918: Out of bounds read (bsc#1187973)\n- CVE-2021-23362: ssri Regular Expression Denial of Service and hosted-git-info (bsc#1187977)\n- CVE-2021-27290: Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- CVE-2020-7774: npm - Update y18n to fix Prototype-Pollution (bsc#1184450)\n","status":"published","published":"2021-07-14T15:08:18Z","modified":"2026-02-04T03:39:08.248368Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2021:2353-1","title":"Security update for nodejs10","description":"This update for nodejs10 fixes the following issues:\n\nUpdate nodejs10 to 10.24.1.\n\nIncluding fixes for \n\n- CVE-2021-22918: libuv upgrade - Out of bounds read (bsc#1187973)\n- CVE-2021-27290: ssri Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-23362: hosted-git-info Regular Expression Denial of Service (bsc#1187977)\n- CVE-2020-7774: y18n Prototype Pollution (bsc#1184450)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- reduce memory footprint of test-worker-stdio (bsc#1183155)\n","status":"published","published":"2021-07-15T13:18:04Z","modified":"2026-02-04T04:29:59.542005Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2024:11127-1","title":"libopenssl-1_1-devel-1.1.1l-1.2 on GA media","description":"These are all security issues fixed in the libopenssl-1_1-devel-1.1.1l-1.2 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2025-05-07T18:08:19.520287Z","updated_at":"2026-11-02T16:58:34.894275Z"},{"id":"SUSE-SU-2021:2323-1","title":"Security update for nodejs10","description":"This update for nodejs10 fixes the following issues:\n\nUpdate nodejs10 to 10.24.1.\n\nIncluding fixes for \n\n- CVE-2021-22918: libuv upgrade - Out of bounds read (bsc#1187973)\n- CVE-2021-27290: ssri Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-23362: hosted-git-info Regular Expression Denial of Service (bsc#1187977)\n- CVE-2020-7774: y18n Prototype Pollution (bsc#1184450)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n","status":"published","published":"2021-07-14T15:04:31Z","modified":"2026-02-04T04:29:24.406914Z","updated_at":"2026-11-02T15:53:49.138643Z"},{"id":"SUSE-SU-2021:2326-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- update to 12.22.2:\n- CVE-2021-22918: Out of bounds read (bsc#1187973)\n- CVE-2021-23362: ssri Regular Expression Denial of Service and hosted-git-info (bsc#1187977)\n- CVE-2021-27290: Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- CVE-2020-7774: npm - Update y18n to fix Prototype-Pollution (bsc#1184450)\n","status":"published","published":"2021-07-14T15:07:58Z","modified":"2026-02-04T02:45:57.457347Z","updated_at":"2026-11-02T15:53:49.138643Z"},{"id":"SUSE-SU-2021:2327-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- update to 12.22.2:\n- CVE-2021-22918: Out of bounds read (bsc#1187973)\n- CVE-2021-23362: ssri Regular Expression Denial of Service and hosted-git-info (bsc#1187977)\n- CVE-2021-27290: Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- CVE-2020-7774: npm - Update y18n to fix Prototype-Pollution (bsc#1184450)\n","status":"published","published":"2021-07-14T15:08:17Z","modified":"2026-02-04T04:38:49.641996Z","updated_at":"2026-11-02T15:53:49.138643Z"},{"id":"SUSE-SU-2021:2353-1","title":"Security update for nodejs10","description":"This update for nodejs10 fixes the following issues:\n\nUpdate nodejs10 to 10.24.1.\n\nIncluding fixes for \n\n- CVE-2021-22918: libuv upgrade - Out of bounds read (bsc#1187973)\n- CVE-2021-27290: ssri Regular Expression Denial of Service (bsc#1187976)\n- CVE-2021-23362: hosted-git-info Regular Expression Denial of Service (bsc#1187977)\n- CVE-2020-7774: y18n Prototype Pollution (bsc#1184450)\n- CVE-2021-3450: OpenSSL - CA certificate check bypass with X509_V_FLAG_X509_STRICT (bsc#1183851)\n- CVE-2021-3449: OpenSSL - NULL pointer deref in signature_algorithms processing (bsc#1183852)\n- reduce memory footprint of test-worker-stdio (bsc#1183155)\n","status":"published","published":"2021-07-15T13:18:32Z","modified":"2026-02-04T04:22:58.524075Z","updated_at":"2026-11-02T15:53:49.138643Z"}]}}