Jboss Brms vulnerabilitiesRanked by how likely they are to be used.
Jboss Brms is made by Red Hat. We track 8 published vulnerabilities in it, across 7 versions. None of them is on the list of flaws known to be exploited today. If you run Jboss Brms, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Jboss Brms vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Jboss Brms's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Jboss Brms 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.
- 11%CVE-2018-19362Critical
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the jboss-common-core class from polymorphic deserialization.
- 11%CVE-2018-19360Critical
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization.
- 11%CVE-2018-19361Critical
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the openjpa class from polymorphic deserialization.
- 8.9%CVE-2018-12023High
An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6.
- 7.3%CVE-2018-12022High
An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6.
- 4.0%CVE-2016-7041Medium
Drools Workbench contains a path traversal vulnerability.
- 2.2%CVE-2020-14340Medium
A vulnerability was discovered in XNIO where file descriptor leak caused by growing amounts of NIO Selector file handles between garbage collection cycles.
- 0.9%CVE-2012-5626High
EJB method in Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 5; Red Hat JBoss Operations Network 3.1; Red Hat JBoss Portal 4 and 5; Red Hat JBoss SOA Platform 4.2, 4.3, and 5; in Red Hat JBoss...
Running Jboss Brms? 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
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the jboss-common-core class from polymorphic deserialization.
- Matched to
- Jboss Brms 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 8 published vulnerabilities listed under the name Jboss Brms, across 7 versions.
None of Jboss Brms's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Jboss Brms. 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.