Communications Billing and Revenue Management vulnerabilitiesRanked by how likely they are to be used.
Communications Billing and Revenue Management is made by Oracle. We track 66 published vulnerabilities listed under that exact name, across 10 versions. None of them is on the list of flaws known to be exploited today. Oracle lists newer releases under their own names, such as Communications Billing and Revenue Management Elastic Charging Engine, so check those pages too.
We keep watching the known-exploited list.
Is Communications Billing and Revenue Management listed under other names? Yes.
Oracle also lists Communications Billing and Revenue Management under more specific names, such as Communications Billing and Revenue Management Elastic Charging Engine. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Communications Billing and Revenue Management vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Billing and Revenue Management's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Billing and Revenue Management 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.
- >99%CVE-2020-11022Medium
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e.
- 87%CVE-2019-11358Medium
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution.
- 38%CVE-2017-7525Critical
A deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input...
- 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.
- 20%CVE-2018-7489Critical
FasterXML jackson-databind before 2.7.9.3, 2.8.x before 2.8.11.1 and 2.9.x before 2.9.5 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw.
- 18%CVE-2020-25649High
A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly.
- 17%CVE-2020-36179High
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.
- 13%CVE-2021-36090High
When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.
- 13%CVE-2018-14718Critical
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization.
Running Communications Billing and Revenue Management? 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 Billing and Revenue Management 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 66 published vulnerabilities listed under the name Communications Billing and Revenue Management, across 10 versions.
None of Communications Billing and Revenue Management's vulnerabilities is on the list of flaws known to be exploited today.
Oracle also lists Communications Billing and Revenue Management under more specific names, such as Communications Billing and Revenue Management Elastic Charging Engine. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Communications Billing and Revenue Management. 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.