What is the severity of CVE-2016-8322?

CVE-2016-8322 is classified as an easily exploitable vulnerability that allows a low privileged attacker to compromise the system.

How do I fix CVE-2016-8322?

To fix CVE-2016-8322, it is essential to upgrade to the latest version of Oracle FLEXCUBE Core Banking that is not affected by this vulnerability.

What versions of Oracle FLEXCUBE are affected by CVE-2016-8322?

CVE-2016-8322 affects Oracle FLEXCUBE Core Banking versions 5.1.0, 5.2.0, and 11.5.0.

Who is at risk for CVE-2016-8322?

Organizations using Oracle FLEXCUBE Core Banking versions 5.1.0, 5.2.0, or 11.5.0 are at risk of exploitation through CVE-2016-8322.

What impact does CVE-2016-8322 have on security?

CVE-2016-8322 allows attackers to leverage their low privileges and network access to perform actions that may compromise the security of the system.

Vulnerability/
CVE-2016-8322

medium

4.3

CWE

200

27/1/2017

9/10/2024

CVE-2016-8322: Infoleak

First published: Fri Jan 27 2017(Updated: )

Vulnerability in the Oracle FLEXCUBE Core Banking component of Oracle Financial Services Applications (subcomponent: Core). Supported versions that are affected are 5.1.0, 5.2.0 and 11.5.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Core Banking. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle FLEXCUBE Core Banking accessible data. CVSS v3.0 Base Score 4.3 (Confidentiality impacts).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle FLEXCUBE Core Banking	=5.1.0
Oracle FLEXCUBE Core Banking	=5.2.0
Oracle FLEXCUBE Core Banking	=11.5.0

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-8322?
CVE-2016-8322 is classified as an easily exploitable vulnerability that allows a low privileged attacker to compromise the system.
How do I fix CVE-2016-8322?
To fix CVE-2016-8322, it is essential to upgrade to the latest version of Oracle FLEXCUBE Core Banking that is not affected by this vulnerability.
What versions of Oracle FLEXCUBE are affected by CVE-2016-8322?
CVE-2016-8322 affects Oracle FLEXCUBE Core Banking versions 5.1.0, 5.2.0, and 11.5.0.
Who is at risk for CVE-2016-8322?
Organizations using Oracle FLEXCUBE Core Banking versions 5.1.0, 5.2.0, or 11.5.0 are at risk of exploitation through CVE-2016-8322.
What impact does CVE-2016-8322 have on security?
CVE-2016-8322 allows attackers to leverage their low privileges and network access to perform actions that may compromise the security of the system.

collector/nvd-index
agent/softwarecombine
agent/type
agent/remedy
agent/severity
agent/author
agent/weakness
agent/references
agent/tags
agent/description
agent/first-publish-date
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
vendor/oracle
canonical/oracle flexcube core banking
version/oracle flexcube core banking/5.1.0
version/oracle flexcube core banking/5.2.0
version/oracle flexcube core banking/11.5.0

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.