Communications Brm - Elastic Charging Engine vulnerabilitiesRanked by how likely they are to be used.
Communications Brm - Elastic Charging Engine is made by Oracle. We track 14 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 Brm - Elastic Charging Engine, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Communications Brm - Elastic Charging Engine vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Brm - Elastic Charging Engine's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Brm - Elastic Charging Engine 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.
- 98%CVE-2021-44832Medium
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP...
- 77%CVE-2021-29505High
XStream is software for serializing Java objects to XML and back again.
- 50%CVE-2021-21342Medium
XStream is a Java library to serialize objects to XML and back again.
- 9.2%CVE-2018-15756High
Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources...
- 9.2%CVE-2020-11612High
The ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream.
- 7.9%CVE-2021-43859High
XStream is an open source java library to serialize objects to XML and back again.
- 6.6%CVE-2021-37137High
The Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage.
- 6.2%CVE-2021-38153Medium
Some components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful.
- 5.9%CVE-2021-37136High
The Bzip2 decompression decoder function doesn't allow setting size restrictions on the decompressed output data (which affects the allocation size used during decompression).
- 4.9%CVE-2021-21409Medium
Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Running Communications Brm - Elastic Charging Engine? 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-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
- Matched to
- Communications Brm - Elastic Charging Engine 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 14 published vulnerabilities listed under the name Communications Brm - Elastic Charging Engine, across 6 versions.
None of Communications Brm - Elastic Charging Engine's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Communications Brm - Elastic Charging Engine. 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.