Essbase vulnerabilitiesRanked by how likely they are to be used.
Essbase is made by Oracle. We track 23 published vulnerabilities listed under that exact name, across 7 versions. None of them is on the list of flaws known to be exploited today. Oracle lists newer releases under their own names, such as Essbase Administration Services, so check those pages too.
We keep watching the known-exploited list.
Is Essbase listed under other names? Yes.
Oracle also lists Essbase under more specific names, such as Essbase Administration Services and Essbase Analytic Provider Services. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Essbase vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Essbase's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Essbase 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().
- 64%CVE-2021-3449Medium
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client.
- 64%CVE-2021-22901High
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection.
- 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.
- 16%CVE-2019-12402High
The file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs.
- 9.8%CVE-2020-8285High
curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcard match parsing.
- 7.4%CVE-2021-23841Medium
The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate.
- 7.1%CVE-2020-1971Medium
The X.509 GeneralName type is a generic type for representing different types of names.
- 5.3%CVE-2020-7760High
This affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2.
- 5.3%CVE-2021-22876Medium
curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header.
Running Essbase? 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
- Essbase 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 Essbase, across 7 versions.
None of Essbase's vulnerabilities is on the list of flaws known to be exploited today.
Oracle also lists Essbase under more specific names, such as Essbase Administration Services and Essbase Analytic Provider Services. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Essbase. 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.