Communications Network Integrity vulnerabilitiesRanked by how likely they are to be used.
Communications Network Integrity is made by Oracle. We track 24 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Communications Network Integrity, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Communications Network Integrity vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Network Integrity's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Network Integrity 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.
- >99%CVE-2021-45105Medium
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.
- 90%CVE-2017-5645Critical
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when...
- 89%CVE-2019-2729Critical
Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Web Services).
- 81%CVE-2021-4104High
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.
- 70%CVE-2019-17571Critical
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when...
- 67%CVE-2022-23305Critical
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout.
- 64%CVE-2022-23302High
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker...
- 54%CVE-2022-23307High
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw.
- 28%CVE-2019-10086High
In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects.
Running Communications Network Integrity? 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
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
- Matched to
- Communications Network Integrity 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 24 published vulnerabilities listed under the name Communications Network Integrity, across 3 versions.
None of Communications Network Integrity's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Communications Network Integrity. 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.