Insurance Policy Administration J2ee vulnerabilitiesRanked by how likely they are to be used.

Product20 versions
The short answer

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

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Insurance Policy Administration J2ee vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Insurance Policy Administration J2ee 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. 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
  2. 19%

    In Apache Batik 1.x before 1.10, when deserializing subclass of `AbstractDocument`, the class takes a string from the inputStream as the class name which then use it to call the no-arg constructor of the class.

    CVSS9.8Published24 May 2018
  3. 9.2%

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

    CVSS7.5Published18 Oct 2018
  4. 8.2%

    Improper validation of certificate with host mismatch in Apache Log4j SMTP appender.

    CVSS3.7Published27 Apr 2020
  5. 8.0%

    FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).

    CVSS8.8Published18 Mar 2020
  6. 7.8%

    FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.SharedPoolDataSource.

    CVSS8.1Published17 Dec 2020
  7. 7.3%

    dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks.

    CVSS9.8Published1 May 2020
  8. 6.3%

    FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.dbcp2.datasources.PerUserPoolDataSource.

    CVSS8.1Published17 Dec 2020
  9. 6.3%

    FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).

    CVSS8.8Published31 Mar 2020
Precursor Intelligence

Running Insurance Policy Administration J2ee? 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 18 published vulnerabilities listed under the name Insurance Policy Administration J2ee, across 20 versions.

None of Insurance Policy Administration J2ee's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Insurance Policy Administration J2ee. 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.