Clustered Data Ontap Antivirus Connector vulnerabilitiesRanked by how likely they are to be used.
Clustered Data Ontap Antivirus Connector is made by Netapp. We track 23 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Clustered Data Ontap Antivirus Connector, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Clustered Data Ontap Antivirus Connector vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Clustered Data Ontap Antivirus Connector's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Clustered Data Ontap Antivirus Connector flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 88%CVE-2021-3711Critical
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt().
- 83%CVE-2022-1292High
The c_rehash script does not properly sanitise shell metacharacters to prevent command injection.
- 73%CVE-2022-0778High
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.
- 50%CVE-2021-3712High
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.
- 41%CVE-2022-40303High
An issue was discovered in libxml2 before 2.10.3.
- 40%CVE-2016-8610High
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.
- 22%CVE-2021-3518High
There's a flaw in libxml2 in versions before 2.9.11.
- 17%CVE-2019-1559Medium
If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0...
- 17%CVE-2021-3517High
There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11.
- 7.1%CVE-2020-1971Medium
The X.509 GeneralName type is a generic type for representing different types of names.
Running Clustered Data Ontap Antivirus Connector? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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).
- Matched to
- Clustered Data Ontap Antivirus Connector on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 23 published vulnerabilities listed under the name Clustered Data Ontap Antivirus Connector, across 0 versions.
None of Clustered Data Ontap Antivirus Connector's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Clustered Data Ontap Antivirus Connector. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.