What is the severity of CVE-2017-10008?

CVE-2017-10008 has been classified as an easily exploitable vulnerability with a low privileged access requirement.

How do I fix CVE-2017-10008?

To fix CVE-2017-10008, update the Oracle FLEXCUBE Private Banking software to a patched version provided by Oracle.

What versions of Oracle FLEXCUBE Private Banking are affected by CVE-2017-10008?

The affected versions include 2.0.0, 2.0.1, 2.2.0, and 12.0.1 of Oracle FLEXCUBE Private Banking.

Who is at risk from CVE-2017-10008?

Low privileged attackers with network access could exploit CVE-2017-10008, posing a risk to vulnerable systems.

Is there a workaround for CVE-2017-10008?

There are no known workarounds for CVE-2017-10008; upgrading to the latest version is the only recommended solution.

Vulnerability/
CVE-2017-10008

medium

4.3

8/8/2017

4/10/2024

CVE-2017-10008

First published: Tue Aug 08 2017(Updated: )

Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Miscellaneous). Supported versions that are affected are 2.0.0, 2.0.1, 2.2.0 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 read access to a subset of Oracle FLEXCUBE Private Banking accessible data. CVSS 3.0 Base Score 4.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle FLEXCUBE Private Banking	=2.0.0
Oracle FLEXCUBE Private Banking	=2.0.1
Oracle FLEXCUBE Private Banking	=2.2.0
Oracle FLEXCUBE Private Banking	=12.0.1

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-10008?
CVE-2017-10008 has been classified as an easily exploitable vulnerability with a low privileged access requirement.
How do I fix CVE-2017-10008?
To fix CVE-2017-10008, update the Oracle FLEXCUBE Private Banking software to a patched version provided by Oracle.
What versions of Oracle FLEXCUBE Private Banking are affected by CVE-2017-10008?
The affected versions include 2.0.0, 2.0.1, 2.2.0, and 12.0.1 of Oracle FLEXCUBE Private Banking.
Who is at risk from CVE-2017-10008?
Low privileged attackers with network access could exploit CVE-2017-10008, posing a risk to vulnerable systems.
Is there a workaround for CVE-2017-10008?
There are no known workarounds for CVE-2017-10008; upgrading to the latest version is the only recommended solution.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/severity
agent/remedy
agent/author
agent/tags
agent/event
agent/first-publish-date
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
vendor/oracle
canonical/oracle flexcube private banking
version/oracle flexcube private banking/2.0.0
version/oracle flexcube private banking/2.0.1
version/oracle flexcube private banking/2.2.0
version/oracle flexcube private banking/12.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.