Most recent entries from all

bdu:2021-01845

2026-10-02T14:00:51.297031+00:00

bdu:2021-01845

Withdrawn: BELL-CVE-2021-3450 — CVE-2021-3450 does not affect BellSoft software

2026-10-02T14:00:51.297075+00:00

Withdrawn by the publisher.

BIT-node-2021-3450 — CA certificate check bypass with X509_V_FLAG_X509_STRICT

2026-10-02T14:00:51.297094+00:00

Affected: Bitnami: node

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 Ope…

certfr-2021-avi-221 — De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles permettent à un attaquant de provoquer un problème…

2026-10-02T14:00:51.297139+00:00

certfr-2021-avi-221

cisco-sa-openssl-2021-GHY28dJd — Multiple Vulnerabilities in OpenSSL Affecting Cisco Products: March 2021

2026-10-02T14:00:51.297155+00:00

On March 25, 2021, the OpenSSL Project released a security advisory, OpenSSL Security Advisory [25 March 2021], ["https://www.openssl.org/news/secadv/20210325.txt"] that disclosed two vulnerabilities. Exploitation of these vulnerabilities could allow an attacker to use a valid non-certificate authority (CA) certificate to act as a CA and sign a certificate for an arbitrary organization, user or device, or to cause a denial of service (DoS) condition.

Withdrawn: CLEANSTART-2026-GK72927 — Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflo…

2026-10-02T14:00:51.297179+00:00

Withdrawn by the publisher.

Affected: CleanStart: openssl

Multiple security vulnerabilities affect the openssl package. Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. See references for individual vulnerability details.

cnvd-2021-39525

2026-10-02T14:00:51.297201+00:00

cnvd-2021-39525

EUVD-2026-183188

2026-10-02T14:00:51.297213+00:00

EUVD-2026-183188

fkie_cve-2021-3450

2026-10-02T14:00:51.297224+00:00

GHSA-8hfj-xrj2-pm22 — Certificate check bypass in openssl-src

2026-10-02T14:00:51.297256+00:00

Affected: crates.io: openssl-src

gsd-2021-3450

2026-10-02T14:00:51.297292+00:00

gsd-2021-3450

ICSA-22-069-09 — Siemens SINEC INS

2026-10-02T14:00:51.297305+00:00

SQLite 3.30.1 mishandles pExpr->y.pTab, as demonstrated by the TK_COLUMN case in sqlite3ExprCodeTarget in expr.c. Select in select.c in SQLite 3.30.1 allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage. lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact. SQLite 3.30.1 mishandles certain SELECT statements with a nonexistent VIEW, leading to an application crash. alter.c in SQLite through 3.30.1 allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements. pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns. exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled. flattenSubquery in select.c in SQLite 3.30.1 mishandles certain uses of SELECT DISTINCT involving a LEFT JOIN in which the right-hand side is a view. This can cause a NULL pointer dereference (or incorrect results). SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling. zipfileUpdate in ext/misc/zipfile.c in SQLite…

OESA-2022-1620 — nodejs security update

2026-10-02T14:00:51.297571+00:00

Affected: openEuler:20.03-LTS-SP1: nodejs, openEuler:20.03-LTS-SP2: nodejs, openEuler:20.03-LTS-SP3: nodejs

Node.js is a platform built on Chrome'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. Security Fix(es): An 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) 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…

openSUSE-SU-2021:1059-1 — Security update for nodejs12

2026-10-02T14:00:51.297632+00:00

Security update for nodejs12

RHSA-2021:1189 — Red Hat Security Advisory: Red Hat Virtualization security, bug fix, and enhancement update

2026-10-02T14:00:51.297651+00:00

openssl: NULL pointer dereference in signature_algorithms processing openssl: CA certificate check bypass with X509_V_FLAG_X509_STRICT

RUSTSEC-2021-0056 — CA certificate check bypass with X509_V_FLAG_X509_STRICT

2026-10-02T14:00:51.297671+00:00

Affected: crates.io: openssl-src

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.

SUSE-SU-2021:2323-1 — Security update for nodejs10

2026-10-02T14:00:51.297702+00:00

Security update for nodejs10

Withdrawn: UBUNTU-CVE-2021-3450

2026-10-02T14:00:51.297721+00:00

Withdrawn by the publisher.

Affected: Ubuntu:16.04:LTS: openssl, Ubuntu:18.04:LTS: openssl, Ubuntu:18.04:LTS: openssl1.0, Ubuntu:20.04:LTS: openssl

VDE-2021-025 — PHOENIX CONTACT: Security Advisory for PLCNext, ILC 2050 BI, FL MGUARD DM UNLIMITED, TC ROUTER und CLOUD CLIENT products

2026-10-02T14:00:51.297754+00:00

A Denial of Service and a CA Check Problem have been identified in multiple openSSL 1.1.1 versions, which are utilized in the Phoenix Contact products listed above.

WID-SEC-W-2022-0671 — OpenSSL: Mehrere Schwachstellen

2026-10-02T14:00:51.297771+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenSSL ausnutzen, um einen Denial of Service Angriff durchzuführen und um kryptografische Sicherheitsmechanismen zu umgehen.