Openshift Application Runtimes vulnerabilitiesRanked by how likely they are to be used.
Openshift Application Runtimes is made by Red Hat. We track 33 published vulnerabilities listed under that exact name, across 1 version. None of them is on the list of flaws known to be exploited today. Red Hat lists newer releases under their own names, such as Openshift Application Runtimes Text-Only Advisories, so check those pages too.
We keep watching the known-exploited list.
Is Openshift Application Runtimes listed under other names? Yes.
Red Hat also lists Openshift Application Runtimes under more specific names, such as Openshift Application Runtimes Text-Only Advisories. 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 Openshift Application Runtimes vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Openshift Application Runtimes's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Openshift Application Runtimes 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.
- 3.5%CVE-2019-10184High
undertow before version 2.0.23.Final is vulnerable to an information leak issue.
- 3.1%CVE-2019-10174High
A vulnerability was found in Infinispan such that the invokeAccessibly method from the public class ReflectionUtil allows any application class to invoke private methods in any class with Infinispan's privileges.
- 3.0%CVE-2019-3888Critical
A vulnerability was found in Undertow web server before 2.0.21.
- 2.6%CVE-2020-1714High
A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks.
- 2.4%CVE-2020-25644High
A memory leak flaw was found in WildFly OpenSSL in versions prior to 1.1.3.Final, where it removes an HTTP session.
- 2.2%CVE-2019-10219Medium
A vulnerability was found in Hibernate-Validator.
- 1.9%CVE-2020-10758High
A vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified keycloak server, all with a Content-Length header value that exceeds the...
- 1.9%CVE-2019-10212Critical
A flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security.
- 1.8%CVE-2023-1108High
A flaw was found in undertow. This issue makes achieving a denial of service possible due to an unexpected handshake status updated in SslConduit, where the loop never terminates.
Running Openshift Application Runtimes? 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
- Openshift Application Runtimes 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 33 published vulnerabilities listed under the name Openshift Application Runtimes, across 1 version.
None of Openshift Application Runtimes's vulnerabilities is on the list of flaws known to be exploited today.
Red Hat also lists Openshift Application Runtimes under more specific names, such as Openshift Application Runtimes Text-Only Advisories. 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 Openshift Application Runtimes. 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.