Communications Session Border Controller vulnerabilitiesRanked by how likely they are to be used.
Communications Session Border Controller is made by Oracle. We track 22 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Communications Session Border Controller, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Communications Session Border Controller vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Session Border Controller's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Session Border Controller 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.
- 95%CVE-2015-0235Critical
Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1)...
- 88%CVE-2021-3711Critical
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt().
- 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.
- 18%CVE-2019-5482Critical
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
- 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...
- 9.7%CVE-2021-33909High
fs/seq_file.c in the Linux kernel 3.16 through 5.13.x before 5.13.4 does not properly restrict seq buffer allocations, leading to an integer overflow, an Out-of-bounds Write, and escalation to root by an unprivileged...
- 7.5%CVE-2019-5481Critical
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
- 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.
Running Communications Session Border Controller? 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
Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1) gethostbyname or (2) gethostbyname2 function, aka "GHOST."
- Matched to
- Communications Session Border Controller 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 22 published vulnerabilities listed under the name Communications Session Border Controller, across 12 versions.
None of Communications Session Border Controller's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Communications Session Border Controller. 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.