CVE-2016-5623: Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Product / Instrument Search)

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Product / Instrument Search). Supported versions that are affected are 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 update, insert or delete access to some of Oracle FLEXCUBE Private Banking accessible data as well as unauthorized read access to a subset of Oracle FLEXCUBE Private Banking accessible data. CVSS v3.0 Base Score 5.4 (Confidentiality and Integrity impacts).

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-254 ↗
CWE-254. Open the MITRE definition for the exact weakness description.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkCWE-254

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2016-6567Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

Canadian Centre for Cyber Security · English · AV17-007Oracle Critical Patch update Advisory – January 2017

Monitor, version(s) 3.1.3.7856 and prior, 3.1.4.7895 and prior, 3.1.5.7958 and prior, 3.2.1.1049 and prior, 3.2.4.1102 and prior, 3.3.0.1098 and prior MySQL Server, version(s) 5.5.53 and prior, 5.6.34 and prior, 5.7.16 and prior CVE References: CVE-2015-0250, CVE-2015-1791, CVE-2015-3237, CVE-2015-3253, CVE-2015-5505, CVE-2015-7501, CVE-2015-7940, CVE-2016-6304, CVE-2016-0635, CVE-2016-0714, CVE-2016-0734, CVE-2016-1182, CVE-2016-1903, CVE-2016-2183, CVE-2016-5000, CVE-2016-5019, CVE-2016-5509, CVE-2016-5528, CVE-2016-5541, CVE-2016-5545, CVE-2016-5546, CVE-2016-5547, CVE-2016-5548, CVE-2016-5549, CVE-2016-5552, CVE-2016-5590, CVE-2016-5614, CVE-2016-5623, CVE-2016-6303, CVE-2016-6304, CVE-2016-7052, CVE-2016-8282, CVE-2016-8297, CVE-2016-8298, CVE-2016-8299, CVE-2016-8300, CVE-2016-8301, CVE-2016-8302, CVE-2016-8303, CVE-2016-8304, CVE-2016-8305, CVE-2016-8306, CVE-2016-8307, CVE-2016-8308, CVE-2016-8309, CVE-2016-8310, CVE-2016-8311, CVE-2016-8312, CVE-2016-8313, CVE-2016-8314, CVE-2016-8315, CVE-2016-8316, CVE-2016-8317, CVE-2016-8318, CVE-2016-8319, CVE-2016-8320, CVE-2016-8322, CVE-2016-8323, CVE-2016-8324, CVE-2016-8325, CVE-2016-8327, CVE-2016-8328, CVE-2016-8329, CVE-2016-8330, CVE-2017-3231, CVE-2017-3235, CVE-2017-3236, CVE-2017-3238, CVE-2017-3239, CVE-2017-3240, CVE-2017-3241, CVE

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2017-001323Oracle Financial Services Applications の Oracle FLEXCUBE Private Banking における Product / Instrument Search に関する脆弱性

Oracle Financial Services Applications の Oracle FLEXCUBE Private Banking には、Product / Instrument Search に関する処理に不備があるため、機密性、および完全性に影響のある脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: FLEXCUBE Private Banking: 2.0.1, 2.2.0, 12.0.1
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 27 Jan 2017 · Last source change 9 Oct 2024, 20:03 UTC · CWE-254

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2016-6567

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

1 Sep 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2016-6567 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2016-6567"}
ENISA EUVD ↗
9 Oct 2024, 20:03 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: oracle.com/cpujan2017-2881727.html; added remediation: oracle.com/cpujan2017-2881727.html.
Before
no authoritative guidance recorded
After
patch: oracle.com/cpujan2017-2881727.html · remediation: oracle.com/cpujan2017-2881727.html
oracle.com ↗
9 Oct 2024, 20:03 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
2.0.1; 2.2.0; 12.0.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
2.0.1; 2.2.0; 12.0.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
9 Oct 2024, 20:03 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
oracle.com ↗
9 Oct 2024, 20:03 UTC
SeveritySeverity changed from Unknown to Medium.
Before
Unknown
After
Medium
NIST NVD ↗
9 Oct 2024, 20:03 UTC
CVSS scoreCVSS score changed from not recorded to 5.4 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N).
Before
not recorded
After
5.4 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N)
NIST NVD ↗
9 Oct 2024, 20:03 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2017-01-27CVE published

2024-10-09Fixed release or patch reference recorded

ENISA EUVD · EUVD-2016-6567↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Vulnerability in the Oracle FLEXCUBE Private Banking component of Oracle Financial Services Applications (subcomponent: Product / Instrument Search)

Published severity in operational context

Evidence used

Compensating controls

Verification

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2016-6567