Hci Storage Node BIOS vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Hci Storage Node BIOS is made by Netapp. We track 14 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Hci Storage Node BIOS, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Hci Storage Node BIOS vulnerabilities are being exploited?

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

None of Hci Storage Node BIOS's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Hci Storage Node BIOS 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. 0.5%

    Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.

    CVSS5.5Published12 Nov 2020
  2. 0.4%

    Improper removal of sensitive information before storage or transfer in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.

    CVSS5.5Published12 Nov 2020
  3. 0.4%

    Use of potentially dangerous function in Intel BIOS platform sample code for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.

    CVSS7.8Published12 Nov 2020
  4. 0.4%

    Improper access control in BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

    CVSS6.7Published12 Nov 2020
  5. 0.4%

    Out of bounds write in Intel BIOS platform sample code for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

    CVSS6.7Published12 Nov 2020
  6. 0.3%

    Out of bounds read in the firmware for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.

    CVSS7.8Published9 Jun 2021
  7. 0.3%

    Improper initialization in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

    CVSS6.7Published9 Jun 2021
  8. 0.3%

    Improper conditions check in Intel BIOS platform sample code for some Intel(R) Processors before may allow a privileged user to potentially enable escalation of privilege via local access.

    CVSS6.7Published12 Nov 2020
  9. 0.3%

    Insufficient control flow management in the firmware for some Intel(R) Processors may allow an unauthenticated user to potentially enable escalation of privilege via physical access.

    CVSS6.8Published9 Jun 2021
Precursor Intelligence

Running Hci Storage Node BIOS? 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 Hci Storage Node BIOS, across 0 versions.

None of Hci Storage Node BIOS's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Hci Storage Node BIOS. 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.