Communications Eagle Lnp Application Processor vulnerabilitiesRanked by how likely they are to be used.
Communications Eagle Lnp Application Processor is made by Oracle. We track 6 published vulnerabilities in it, across 6 versions. None of them is on the list of flaws known to be exploited today. If you run Communications Eagle Lnp Application Processor, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Communications Eagle Lnp Application Processor vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Eagle Lnp Application Processor's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Eagle Lnp Application Processor 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)...
- 55%CVE-2017-3730High
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash.
- 11%CVE-2020-10543High
Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.
- 6.0%CVE-2020-12723High
regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.
- 5.3%CVE-2021-21783Critical
A code execution vulnerability exists in the WS-Addressing plugin functionality of Genivia gSOAP 2.8.107.
- 4.9%CVE-2020-10878High
Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation.
Running Communications Eagle Lnp Application Processor? 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 Eagle Lnp Application Processor 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 6 published vulnerabilities listed under the name Communications Eagle Lnp Application Processor, across 6 versions.
None of Communications Eagle Lnp Application Processor's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Communications Eagle Lnp Application Processor. 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.