Trident vulnerabilitiesRanked by how likely they are to be used.
Trident is made by Netapp. We track 11 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Trident, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Trident vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Trident's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Trident 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.
- 87%CVE-2018-1002105Critical
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection...
- 83%CVE-2019-9514High
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service.
- 7.0%CVE-2021-34558Medium
The crypto/tls package of Go through 1.16.5 does not properly assert that the type of public key in an X.509 certificate matches the expected type when doing a RSA based key exchange, allowing a malicious TLS server...
- 3.9%CVE-2020-28362High
Go before 1.14.12 and 1.15.x before 1.15.4 allows Denial of Service.
- 2.3%CVE-2020-28366High
Code injection in the go command with cgo before Go 1.14.12 and Go 1.15.5 allows arbitrary code execution at build time via a malicious unquoted symbol name in a linked object file.
- 2.1%CVE-2020-29509Medium
The encoding/xml package in Go (all versions) does not correctly preserve the semantics of attribute namespace prefixes during tokenization round-trips, which allows an attacker to craft inputs that behave in...
- 2.1%CVE-2020-29510Medium
The encoding/xml package in Go versions 1.15 and earlier does not correctly preserve the semantics of directives during tokenization round-trips, which allows an attacker to craft inputs that behave in conflicting...
- 2.1%CVE-2021-25742High
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the custom snippets feature to obtain all secrets in the cluster.
- 2.0%CVE-2020-29511Medium
The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips, which allows an attacker to craft inputs that behave in...
- 1.5%CVE-2019-11243High
In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data).
Running Trident? 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 all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
- Matched to
- Trident 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 11 published vulnerabilities listed under the name Trident, across 0 versions.
None of Trident's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Trident. 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.