Produkt Clustered data ontap antivirus connector (...) - CVEMAP.ORG

Podatności dla
'Clustered data ontap antivirus connector'

2022-03-15

CVE-2022-0778

CWE-835

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

2021-08-24

CVE-2021-3711

CWE-120

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. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).

CVE-2021-3712

CWE-125

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).

2017-11-13

CVE-2016-8610

CWE-400

A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL protocol defined processing of ALERT packets during a connection handshake. A remote attacker could use this flaw to make a TLS/SSL server consume an excessive amount of CPU and fail to accept connections from other clients.

>>> Vendor: Netapp 93 Produkty

Oncommand balance

Oncommand workflow automation

Clustered data ontap

Oncommand system manager

Snap creator framework

Metrocluster tiebreaker

Oncommand insight

Virtual storage console for vmware vsphere

Snapcenter server

Oncommand unified manager for clustered data ontap

Ontap select administration utility

Oncommand unified manager core package

Storagegrid webscale

Service level manager

Hyper converged infrastructure

Solidfire element os

Oncommand unified manager

Santricity smi-s provider

Cn1610 firmware

Data ontap edge

Element software management node

Solidfire element os management node

Element software

Santricity cloud connector

E-series santricity os controller

Ontap select deploy

Steelstore cloud integrated storage

Storage automation store

Ontap select deploy utility

Active iq performance analytics services

Ontap select deploy administration utility

Element software management

Fas/aff baseboard management controller

E-series santricity management plug-ins

E-series santricity web services proxy

Service processor

Aff baseboard management controller

Fas baseboard management controller

Storagegrid webscale nas bridge

Oncommand api services

E-series santricity management

E-series santricity storage manager

E-series santricity web services

Brocade network advisor

Virtual storage console

Hyper converged infrastructure compute node

Clustered data ontap antivirus connector

Hci storage nodes

Data ontap operating in 7-mode

Oncommand unified manger

Baseboard management controller firmware

E-series santricity unified manager

Oncommand cloud manager

Active iq unified manager

Element healthtools

Hci management node

Hci storage node

Element plug-in for vcenter server

Management services for element software and netapp hci

Solidfire \& hci management node

Brocade fabric os

Manageability software development kit

Storage encryption

Santricity unified manager

Ontap system manager

Brocade san navigator

Cloud insights acquisition unit

Cloud secure agent

Cloud volumes ontap mediator

Copyright 2024, cxsecurity.com