Vulnerabilities > Oracle > Banking Payments > 14.3.0
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2020-01-15 | CVE-2020-2714 | Unspecified vulnerability in Oracle Banking Payments 14.1.0/14.3.0 Vulnerability in the Oracle Banking Payments product of Oracle Financial Services Applications (component: Core). | 4.3 |
2020-01-15 | CVE-2020-2713 | Unspecified vulnerability in Oracle Banking Payments 14.1.0/14.3.0 Vulnerability in the Oracle Banking Payments product of Oracle Financial Services Applications (component: Core). | 7.1 |
2020-01-15 | CVE-2020-2712 | Unspecified vulnerability in Oracle Banking Payments 14.1.0/14.3.0 Vulnerability in the Oracle Banking Payments product of Oracle Financial Services Applications (component: Core). | 5.4 |
2020-01-15 | CVE-2020-2711 | Unspecified vulnerability in Oracle Banking Payments 14.1.0/14.3.0 Vulnerability in the Oracle Banking Payments product of Oracle Financial Services Applications (component: Core). | 6.5 |
2020-01-15 | CVE-2020-2710 | Unspecified vulnerability in Oracle Banking Payments 14.1.0/14.3.0 Vulnerability in the Oracle Banking Payments product of Oracle Financial Services Applications (component: Core). | 5.4 |
2019-08-30 | CVE-2019-12402 | Infinite Loop vulnerability in multiple products The file name encoding algorithm used internally in Apache Commons Compress 1.15 to 1.18 can get into an infinite loop when faced with specially crafted inputs. | 7.5 |
2019-07-26 | CVE-2019-13990 | XXE vulnerability in multiple products initDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description. | 9.8 |
2018-04-26 | CVE-2018-10237 | Allocation of Resources Without Limits or Throttling vulnerability in multiple products Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable. | 5.9 |