Quick answers
- Is CVE-2016-8282 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-8282 being exploited in the wild.
- How severe is CVE-2016-8282?
- Medium severity, with a CVSS score of 6.1, published 27 January 2017.
- Which products and versions are affected?
- Oracle Flexcube Private Banking 2.0.1, 2.2.0, 12.0.1.
- Is there a fix for CVE-2016-8282?
- A patch was published on 2017-01-17: Addressed in Oracle January 2017 Critical Patch Update Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-8282 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2016-8282?
- Check whether you run Oracle Flexcube Private Banking at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the Product / Instrument Search subcomponent of Oracle FLEXCUBE Private Banking (versions 2.0.1, 2.2.0, and 12.0.1). The flaw is classified under improper access control and is exploitable via the network over HTTP without authentication. Successful exploitation requires interaction from a user other than the attacker (User Interaction: Required) and features a 'Changed' Scope, meaning the impact can extend beyond the FLEXCUBE application itself. Attackers can achieve unauthorized read access to a subset of data and unauthorized update, insert, or delete access to some accessible data. Oracle addressed this in the January 2017 Critical Patch Update.
Affected products
- Oracle FLEXCUBE Private Banking 2.0.1, 2.2.0, 12.0.1
Timeline
- 2017-01-27: advisory: Initial NVD publication date
- 2017-01-17: patched: Addressed in Oracle January 2017 Critical Patch Update