Log

AVG-1336 deleted at 24 Aug 2021 14:15:03
Packages
- openssl-1.0
Issues
- CVE-2020-1971
- CVE-2021-3601
Status
- Vulnerable
Severity
- High
Affected
- 1.0.2.u-1
Fixed
Ticket
Advisory qualified
- Yes
References
Notes
- OpenSSL 1.0.2 is out of support and no longer receiving public updates, so these issues will not be fixed.
CVE-2021-3712 edited at 24 Aug 2021 14:13:10
Severity
- Unknown
+ Medium
Remote
- Unknown
+ Remote
Type
- Unknown
+ Information disclosure
Description
+ A security issue has been found in OpenSSL before version 1.1.1l. 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).
References
+ https://www.openssl.org/news/secadv/20210824.txt
+ https://github.com/openssl/openssl/commit/94d23fcff9b2a7a8368dfe52214d5c2569882c11
+ https://github.com/openssl/openssl/commit/ccb0a11145ee72b042d10593a64eaf9e8a55ec12
Notes
AVG-2315 edited at 24 Aug 2021 14:10:55
Severity
- Medium
+ High
CVE-2021-3711 edited at 24 Aug 2021 14:10:55
Severity
- Medium
+ High
AVG-2315 edited at 24 Aug 2021 14:10:27
Severity
- Unknown
+ Medium
CVE-2021-3711 edited at 24 Aug 2021 14:10:27
Severity
- Unknown
+ Medium
Remote
- Unknown
+ Remote
Type
- Unknown
+ Arbitrary code execution
Description
+ A security issue has been found in OpenSSL 1.1.1 before version 1.1.1l. In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter.
+
+ A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small.
+
+ A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated.
References
+ https://www.openssl.org/news/secadv/20210824.txt
+ https://github.com/openssl/openssl/commit/59f5e75f3bced8fc0e130d72a3f582cf7b480b46
Notes
AVG-2315 created at 24 Aug 2021 14:07:48
Packages
+ openssl
Issues
+ CVE-2021-3711
+ CVE-2021-3712
Status
+ Vulnerable
Severity
+ Unknown
Affected
+ 1.1.1.k-1
Fixed
Ticket
Advisory qualified
+ Yes
References
Notes
CVE-2021-3712 created at 24 Aug 2021 14:07:48
AVG-2315 created at 24 Aug 2021 14:07:48
Packages
+ openssl
Issues
+ CVE-2021-3711
+ CVE-2021-3712
Status
+ Vulnerable
Severity
+ Unknown
Affected
+ 1.1.1.k-1
Fixed
Ticket
Advisory qualified
+ Yes
References
Notes
CVE-2021-3711 created at 24 Aug 2021 14:07:48
CVE-2021-3587 deleted at 24 Aug 2021 11:35:38
Severity
- Low
Remote
- Local
Type
- Denial of service
Description
- There is a null pointer dereference in llcp_sock_getname in net/nfc/llcp_sock.c of the Linux kernel. An unprivileged user can trigger this bug and cause denial of service.
References
- https://www.openwall.com/lists/oss-security/2021/06/01/1
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.12.10&id=0c4559736d9a4ec1ca58ba98ca34e7c4da4c422b
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.43&id=48ee0db61c8299022ec88c79ad137f290196cac2
Notes
- This CVE has been rejected as a duplicate of CVE-2021-38208.
CVE-2021-3587 edited at 24 Aug 2021 11:35:34
Notes
+ This CVE has been rejected as a duplicate of CVE-2021-38208.
AVG-2066 edited at 24 Aug 2021 11:35:16
Issues
CVE-2021-3564
CVE-2021-3573
- CVE-2021-3587
+ CVE-2021-38208
AVG-2065 edited at 24 Aug 2021 11:35:09
Issues
CVE-2021-3564
CVE-2021-3573
- CVE-2021-3587
+ CVE-2021-38208