Insurance Rules Palette vulnerabilitiesRanked by how likely they are to be used.

Product24 versions
The short answer

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

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Insurance Rules Palette vulnerabilities are being exploited?

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

None of Insurance Rules Palette's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Insurance Rules Palette 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. 90%

    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...

    CVSS9.8Published17 Apr 2017
  2. 89%

    In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a...

    CVSS7.5Published17 Jan 2020
  3. 77%

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through...

    CVSS9.8Published6 Apr 2018
  4. 57%

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through...

    CVSS9.8Published11 Apr 2018
  5. 34%

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g.

    CVSS5.9Published6 Apr 2018
  6. 18%

    A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly.

    CVSS7.5Published3 Dec 2020
  7. 17%

    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.

    CVSS8.1Published7 Jan 2021
  8. 13%

    FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in...

    CVSS8.1Published27 Dec 2020
  9. 12%

    In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the...

    CVSS6.5Published19 Sep 2020
  10. 11%

    In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to...

    CVSS4.8Published13 Apr 2021
Precursor Intelligence

Running Insurance Rules Palette? 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 34 published vulnerabilities listed under the name Insurance Rules Palette, across 24 versions.

None of Insurance Rules Palette's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Insurance Rules Palette. 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.