CVE-2021-20227: A flaw was found in SQLite's SELECT query functionality (src/select.c). This flaw allows an attacker who is capable of running SQL queries locally on the SQLite database to cause a denial of service or possible code execution by triggering a use-after-free. The highest threat from this vulnerability is to system availability. CVE-2021-3712: ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y). These don't seem to be unbundled, so I assume we're vulnerable? If so, need to stabilize .27.
(In reply to John Helmert III from comment #0) > These don't seem to be unbundled, so I assume we're vulnerable? If so, need > to stabilize .27. My understanding is that these are only bundled on platforms that cannot easily provide them natively, e.g. windows. The community src version that we use does not bundle openssl as far as I can tell and uses normal cmake rules to find it in the system. sqlite is used indirectly through vsqlite++ which dynamically links to sqlite.
(In reply to Hans de Graaff from comment #1) > (In reply to John Helmert III from comment #0) > > > These don't seem to be unbundled, so I assume we're vulnerable? If so, need > > to stabilize .27. > > My understanding is that these are only bundled on platforms that cannot > easily provide them natively, e.g. windows. Got it! > The community src version that we use does not bundle openssl as far as I > can tell and uses normal cmake rules to find it in the system. I guess the ebuilds should have such a dependency, then? > sqlite is used indirectly through vsqlite++ which dynamically links to > sqlite. Ok, nothing for us to do here
