Hyperion Data Relationship Management vulnerabilitiesRanked by how likely they are to be used.

Product6 versions
The short answer

Hyperion Data Relationship Management is made by Oracle. We track 10 published vulnerabilities in it, across 6 versions. None of them is on the list of flaws known to be exploited today. If you run Hyperion Data Relationship Management, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Hyperion Data Relationship Management vulnerabilities are being exploited?

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

None of Hyperion Data Relationship Management's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Hyperion Data Relationship 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.

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

    JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.

    CVSS7.5Published14 Dec 2021
  3. 67%

    By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout.

    CVSS9.8Published18 Jan 2022
  4. 64%

    JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker...

    CVSS8.8Published18 Jan 2022
  5. 54%

    CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw.

    CVSS8.8Published18 Jan 2022
  6. 5.3%

    This affects the package codemirror before 5.58.2; the package org.apache.marmotta.webjars:codemirror before 5.58.2.

    CVSS7.5Published30 Oct 2020
  7. 2.0%

    Vulnerability in the Hyperion Data Relationship Management component of Oracle Hyperion (subcomponent: Access and security).

    CVSS5.8Published18 Jul 2018
  8. 2.0%

    Vulnerability in the Hyperion Data Relationship Management component of Oracle Hyperion (subcomponent: Access and Security).

    CVSS7.7Published17 Oct 2018
  9. 1.5%

    Vulnerability in the Hyperion Data Relationship Management component of Oracle Hyperion (subcomponent: Access and security).

    CVSS5.3Published18 Jan 2018
  10. 1.1%

    Vulnerability in the Hyperion Data Relationship Management product of Oracle Hyperion (component: Access and Security).

    CVSS6.4Published16 Oct 2019
Precursor Intelligence

Running Hyperion Data Relationship 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.

  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 10 published vulnerabilities listed under the name Hyperion Data Relationship Management, across 6 versions.

None of Hyperion Data Relationship Management's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Hyperion Data Relationship 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.