Banking Party Management vulnerabilitiesRanked by how likely they are to be used.
Banking Party Management is made by Oracle. We track 16 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Banking Party Management, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Banking Party Management vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Banking Party Management's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Banking Party Management 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.
- >99%CVE-2021-45105Medium
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.
- 23%CVE-2020-13936High
An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands with the same privileges as the account running the Servlet container.
- 13%CVE-2021-36090High
When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.
- 12%CVE-2021-35516High
When reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.
- 12%CVE-2022-23437Medium
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads.
- 12%CVE-2021-35515High
When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop.
- 11%CVE-2021-35517High
When reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.
- 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...
- 2.9%CVE-2021-43797Medium
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
- 2.3%CVE-2021-26272Medium
It was possible to execute a ReDoS-type attack inside CKEditor 4 before 4.16 by persuading a victim to paste crafted URL-like text into the editor, and then press Enter or Space (in the Autolink plugin).
Running Banking Party Management? 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-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
- Matched to
- Banking Party Management 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 16 published vulnerabilities listed under the name Banking Party Management, across 1 version.
None of Banking Party Management's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Banking Party Management. 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.