How severe is CVE-2017-3472?

CVE-2017-3472 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2017-3472 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (77th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-3472?

CVE-2017-3472 primarily affects Oracle Flexcube Private Banking. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-3472?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-3472 published?

CVE-2017-3472 was published on 2017-04-24 and last updated on 2026-06-17.

CVE-2017-3472

CVE-2017-3472 is a high-severity vulnerability in Oracle Flexcube Private Banking with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.1)
CVSS v2: 8.5
EPSS exploit prediction: 2% (77th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Flexcube Private Banking
Published: 2017-04-24
Last modified: 2026-06-17

Description

Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Portfolio Management). Supported versions that are affected are 2.0.0, 2.0.1, 2.2.0.1 and 12.0.1. Easily "exploitable" vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Private Banking. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle FLEXCUBE Private Banking accessible data as well as unauthorized access to critical data or complete access to all Oracle FLEXCUBE Private Banking accessible data. CVSS 3.0 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Frequently asked questions

What is CVE-2017-3472?: Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Portfolio Management). Supported versions that are affected are 2.0.0, 2.0.1, 2.2.0.1 and 12.0.1. Easily "exploitable" vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Private Banking. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle FLEXCUBE Private Banking accessible data as well as unauthorized access to critical data or complete access to all Oracle FLEXCUBE Private Banking accessible data. CVSS 3.0 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
How severe is CVE-2017-3472?: CVE-2017-3472 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2017-3472 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (77th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-3472?: CVE-2017-3472 primarily affects Oracle Flexcube Private Banking. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-3472?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-3472 published?: CVE-2017-3472 was published on 2017-04-24 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:a:oracle:flexcube_private_banking:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:flexcube_private_banking:2.0.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:flexcube_private_banking:2.2.0.1:*:*:*:*:*:*:*
cpe:2.3:a:oracle:flexcube_private_banking:12.0.1:*:*:*:*:*:*:*

More vulnerabilities in Oracle Flexcube Private Banking

CVE-2013-4316 — Critical (CVSS 10.0): Apache Struts 2.0.0 through 2.3.15.1 enables Dynamic Method Invocation by default, which has unknown impact and attack…
CVE-2020-11998 — Critical (CVSS 9.8): A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to…
CVE-2020-5413 — Critical (CVSS 9.8): Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When…
CVE-2020-11973 — Critical (CVSS 9.8): Apache Camel Netty enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to…
CVE-2020-11972 — Critical (CVSS 9.8): Apache Camel RabbitMQ enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to…
CVE-2019-12419 — Critical (CVSS 9.8): Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId…

All CVEs affecting Oracle Flexcube Private Banking →