Enterprise Communications Broker vulnerabilitiesRanked by how likely they are to be used.
Enterprise Communications Broker is made by Oracle. We track 28 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Enterprise Communications Broker, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Enterprise Communications Broker vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Enterprise Communications Broker's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Enterprise Communications Broker 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().
- 82%CVE-2019-9513High
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service.
- 60%CVE-2019-9511High
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service.
- 56%CVE-2014-9708Medium
Embedthis Appweb before 4.6.6 and 5.x before 5.2.1 allows remote attackers to cause a denial of service (NULL pointer dereference) via a Range header with an empty value, as demonstrated by "Range: x=,".
- 53%CVE-2021-23017High
A security issue in nginx resolver was identified, which might allow an attacker who is able to forge UDP packets from the DNS server to cause 1-byte memory overwrite, resulting in worker process crash or potential...
- 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.
- 21%CVE-2021-23337High
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
- 11%CVE-2021-29425Medium
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to...
- 7.3%CVE-2020-28500Medium
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
- 7.1%CVE-2018-11236Critical
stdlib/canonicalize.c in the GNU C Library (aka glibc or libc6) 2.27 and earlier, when processing very long pathname arguments to the realpath function, could encounter an integer overflow on 32-bit architectures,...
Running Enterprise Communications Broker? 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
- Enterprise Communications Broker 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 28 published vulnerabilities listed under the name Enterprise Communications Broker, across 12 versions.
None of Enterprise Communications Broker's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Enterprise Communications Broker. 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.