Banking Extensibility Workbench vulnerabilitiesRanked by how likely they are to be used.
Banking Extensibility Workbench is made by Oracle. We track 20 published vulnerabilities in it, across 7 versions. None of them is on the list of flaws known to be exploited today. If you run Banking Extensibility Workbench, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Banking Extensibility Workbench vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Banking Extensibility Workbench's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Banking Extensibility Workbench 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.
- 21%CVE-2021-23337High
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
- 13%CVE-2020-35728High
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in...
- 8.8%CVE-2020-36188High
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.JNDIConnectionSource.
- 8.4%CVE-2020-36184High
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp2.datasources.PerUserPoolDataSource.
- 7.6%CVE-2020-8174High
napi_get_value_string_*() allows various kinds of memory corruption in node < 10.21.0, 12.18.0, and < 14.4.0.
- 7.3%CVE-2020-28500Medium
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
- 7.2%CVE-2020-28052High
An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66.
- 6.1%CVE-2020-8172High
TLS session reuse can lead to host certificate verification bypass in node version < 12.18.0 and < 14.4.0.
- 5.2%CVE-2020-8203High
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
Running Banking Extensibility Workbench? 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
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
- Matched to
- Banking Extensibility Workbench 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 20 published vulnerabilities listed under the name Banking Extensibility Workbench, across 7 versions.
None of Banking Extensibility Workbench's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Banking Extensibility Workbench. 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.