Developer Tools vulnerabilitiesRanked by how likely they are to be used.
Developer Tools is made by Red Hat. We track 15 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Developer Tools, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Developer Tools vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Developer Tools's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Developer Tools 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.
- 83%CVE-2019-9514High
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service.
- 9.3%CVE-2017-15041Critical
Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution.
- 5.3%CVE-2019-16276High
Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling.
- 4.7%CVE-2019-17596High
Go before 1.12.11 and 1.3.x before 1.13.2 can panic upon an attempt to process network traffic containing an invalid DSA public key.
- 4.2%CVE-2022-1227High
A privilege escalation flaw was found in Podman.
- 2.7%CVE-2018-16871High
A flaw was found in the Linux kernel's NFS implementation, all versions 3.x and all versions 4.x up to 4.20.
- 2.2%CVE-2019-9741Medium
An issue was discovered in net/http in Go 1.11.5.
- 1.4%CVE-2022-27649High
A flaw was found in Podman, where containers were started incorrectly with non-empty default permissions.
- 1.2%CVE-2022-1011High
A use-after-free flaw was found in the Linux kernel’s FUSE filesystem in the way a user triggers write().
- 0.5%CVE-2021-3744Medium
A memory leak flaw was found in the Linux kernel in the ccp_run_aes_gcm_cmd() function in drivers/crypto/ccp/ccp-ops.c, which allows attackers to cause a denial of service (memory consumption).
Running Developer Tools? 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
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.
- Matched to
- Developer Tools 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 15 published vulnerabilities listed under the name Developer Tools, across 1 version.
None of Developer Tools's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Developer Tools. 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.