Codeready Studio vulnerabilitiesRanked by how likely they are to be used.
Codeready Studio is made by Red Hat. We track 4 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Codeready Studio, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Codeready Studio vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Codeready Studio's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Codeready Studio 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.
- 81%CVE-2021-4104High
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.
- 1.5%CVE-2020-10714High
A flaw was found in WildFly Elytron version 1.11.3.Final and before.
- 1.3%CVE-2021-20218High
A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after.
- 0.8%CVE-2021-3642Medium
A flaw was found in Wildfly Elytron in versions prior to 1.10.14.Final, prior to 1.15.5.Final and prior to 1.16.1.Final where ScramServer may be susceptible to Timing Attack if enabled.
Running Codeready Studio? 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
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
- Matched to
- Codeready Studio 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 4 published vulnerabilities listed under the name Codeready Studio, across 1 version.
None of Codeready Studio's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Codeready Studio. 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.