Metrocluster Tiebreaker vulnerabilitiesRanked by how likely they are to be used.
Metrocluster Tiebreaker is made by Netapp. We track 3 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Metrocluster Tiebreaker, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Metrocluster Tiebreaker vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Metrocluster Tiebreaker's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Metrocluster Tiebreaker 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.
- 5.7%CVE-2022-22968Medium
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected...
- 2.2%CVE-2016-6820High
MetroCluster Tiebreaker for clustered Data ONTAP in versions before 1.2 discloses sensitive information in cleartext which may be viewed by an unauthenticated user.
- 1.4%CVE-2021-22096Medium
In Spring Framework versions 5.3.0 - 5.3.10, 5.2.0 - 5.2.17, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries.
Running Metrocluster Tiebreaker? 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
In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.
- Matched to
- Metrocluster Tiebreaker 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 3 published vulnerabilities listed under the name Metrocluster Tiebreaker, across 1 version.
None of Metrocluster Tiebreaker's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Metrocluster Tiebreaker. 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.