Solidfire BIOS vulnerabilitiesRanked by how likely they are to be used.
Solidfire BIOS is made by Netapp. We track 16 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Solidfire BIOS, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Solidfire BIOS vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Solidfire BIOS's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Solidfire 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.
- 0.5%CVE-2020-8698Medium
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- 0.4%CVE-2020-8696Medium
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.
- 0.4%CVE-2020-8739High
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.
- 0.4%CVE-2020-8740Medium
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.
- 0.4%CVE-2020-8764Medium
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.
- 0.4%CVE-2020-24511Medium
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- 0.4%
Observable timing discrepancy in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- 0.3%CVE-2020-12360High
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.
- 0.3%CVE-2020-12357Medium
Improper initialization in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.
- 0.3%CVE-2020-8738Medium
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.
Running Solidfire 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 new flaw affects software Acme tracks
Improper isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
- Matched to
- Solidfire BIOS on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 16 published vulnerabilities listed under the name Solidfire BIOS, across 0 versions.
None of Solidfire BIOS's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Solidfire 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.