Healthcare Data Repository vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited5 versions
The short answer

Healthcare Data Repository is made by Oracle. We track 14 published vulnerabilities in it, across 5 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 November 2021. If you run Healthcare Data Repository, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Healthcare Data Repository flaw added to the known-exploited list is CVE-2020-2555, on 3 November 2021. We keep watching the known-exploited list.

Versions

Which versions of Healthcare Data Repository do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2020-2555Exploited list, 3 Nov 2021

    Oracle Multiple Products Remote Code Execution Vulnerability

    7.0.1
Known exploited

Which Healthcare Data Repository vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.8
    CVE-2020-2555CriticalKnown exploited
    Oracle Multiple Products Remote Code Execution Vulnerability

    Multiple Oracle products contain a remote code execution vulnerability that allows an unauthenticated attacker with network access via T3 or HTTP to takeover the affected system.

    Chance of use97%Known exploited since3 Nov 2021
Exploit likelihood

Which Healthcare Data Repository 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. 97%
    CVE-2020-2555CriticalKnown exploited

    Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Caching,CacheStore,Invocation).

    CVSS9.8Published15 Jan 2020
  3. 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
  4. 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
  5. 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
  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%

    Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in an application crash (potential information disclosure) or a potential authentication bypass.

    CVSS9.8Published15 Oct 2019
  8. 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
  9. 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
  10. 2.5%

    faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and Mojarra JavaServer Faces before 2.2.20, allows Reflected XSS because a client window field is...

    CVSS6.1Published2 Oct 2019
Precursor Intelligence

Running Healthcare Data Repository? 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 14 published vulnerabilities listed under the name Healthcare Data Repository, across 5 versions. The most recent Healthcare Data Repository flaw added to the known-exploited list is CVE-2020-2555, on 3 November 2021.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2020-2555.

Each flaw names its own versions, usually as ranges. The newest, CVE-2020-2555, affects 7.0.1. The versions for every exploited flaw are listed on this page.

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