Flexcube Universal Banking vulnerabilitiesRanked by how likely they are to be used.

Product24 versions
The short answer

Flexcube Universal Banking is made by Oracle. We track 94 published vulnerabilities in it, across 24 versions. None of them is on the list of flaws known to be exploited today. If you run Flexcube Universal Banking, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Flexcube Universal Banking vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Flexcube Universal Banking's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Flexcube Universal Banking 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.

50% or more10% to 49%Under 10%
  1. >99%

    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.

    CVSS5.9Published18 Dec 2021
  2. 13%

    Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel.

    CVSS8.2Published24 Feb 2021
  3. 13%

    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.

    CVSS7.5Published13 Jul 2021
  4. 12%

    When reading a specially crafted 7Z 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.

    CVSS7.5Published13 Jul 2021
  5. 12%

    There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads.

    CVSS6.5Published24 Jan 2022
  6. 12%

    When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop.

    CVSS7.5Published13 Jul 2021
  7. 11%

    When reading a specially crafted TAR 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.

    CVSS7.5Published13 Jul 2021
  8. 6.7%

    jsoup is a Java library for working with HTML.

    CVSS7.5Published18 Aug 2021
  9. 4.6%

    In Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely.

    CVSS6.5Published1 Nov 2021
  10. 3.9%

    When Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an...

    CVSS7.5Published14 Jan 2020
Precursor Intelligence

Running Flexcube Universal Banking? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 94 published vulnerabilities listed under the name Flexcube Universal Banking, across 24 versions.

None of Flexcube Universal Banking's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Flexcube Universal Banking. 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.