Health Sciences Data Management Workbench vulnerabilitiesRanked by how likely they are to be used.
Health Sciences Data Management Workbench is made by Oracle. We track 8 published vulnerabilities in it, across 9 versions. None of them is on the list of flaws known to be exploited today. If you run Health Sciences Data Management Workbench, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Health Sciences Data Management Workbench vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Health Sciences Data Management Workbench's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Health Sciences Data Management 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.
- 98%CVE-2021-44832Medium
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP...
- 21%CVE-2021-23337High
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
- 14%CVE-2019-2904Critical
Vulnerability in the Oracle JDeveloper and ADF product of Oracle Fusion Middleware (component: ADF Faces).
- 11%CVE-2021-29425Medium
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to...
- 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.
- 0.8%CVE-2022-21518Medium
Vulnerability in the Oracle Health Sciences Data Management Workbench product of Oracle Health Sciences Applications (component: User Interface).
- 0.8%CVE-2019-2629Medium
Vulnerability in the Oracle Health Sciences Data Management Workbench component of Oracle Health Sciences Applications (subcomponent: User Interface).
- 0.3%CVE-2025-62288Medium
Vulnerability in the Oracle Health Sciences Data Management Workbench product of Oracle Health Sciences Applications (component: Logger).
Running Health Sciences Data Management 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
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
- Matched to
- Health Sciences Data Management 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 8 published vulnerabilities listed under the name Health Sciences Data Management Workbench, across 9 versions.
None of Health Sciences Data Management Workbench's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Health Sciences Data Management 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.