Cloud Insights Telegraf vulnerabilitiesRanked by how likely they are to be used.
Cloud Insights Telegraf is made by Netapp. We track 5 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Netapp lists newer releases under their own names, such as Cloud Insights Telegraf Agent, so check those pages too.
We keep watching the known-exploited list.
Is Cloud Insights Telegraf listed under other names? Yes.
Netapp also lists Cloud Insights Telegraf under more specific names, such as Cloud Insights Telegraf Agent. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Cloud Insights Telegraf vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cloud Insights Telegraf's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cloud Insights Telegraf 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.
- 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...
- 6.9%CVE-2021-39293High
In archive/zip in Go before 1.16.8 and 1.17.x before 1.17.1, a crafted archive header (falsely designating that many files are present) can cause a NewReader or OpenReader panic.
- 4.0%CVE-2021-44716High
net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests.
- 2.6%CVE-2020-7919High
Go before 1.12.16 and 1.13.x before 1.13.7 (and the crypto/cryptobyte package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients (resulting in a panic) via a malformed X.509 certificate.
- 2.4%CVE-2022-28131High
Uncontrolled recursion in Decoder.Skip in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a deeply nested XML document.
Running Cloud Insights Telegraf? 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
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 to cause a TLS client to panic.
- Matched to
- Cloud Insights Telegraf 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 5 published vulnerabilities listed under the name Cloud Insights Telegraf, across 0 versions.
None of Cloud Insights Telegraf's vulnerabilities is on the list of flaws known to be exploited today.
Netapp also lists Cloud Insights Telegraf under more specific names, such as Cloud Insights Telegraf Agent. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Cloud Insights Telegraf. 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.