Quick answers
- Is CVE-2017-3271 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-3271 being exploited in the wild.
- How severe is CVE-2017-3271?
- High severity, with a CVSS score of 8.6, published 27 January 2017.
- Which products and versions are affected?
- Oracle Outside In Technology 8.5.2, 8.5.3.
- Is there a fix for CVE-2017-3271?
- 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-2017-3271 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-3271?
- Check whether you run Oracle Outside In Technology 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 Outside In Filters subcomponent of Oracle Outside In Technology (versions 8.5.2 and 8.5.3). The flaw allows an unauthenticated attacker with network access via HTTP to compromise the component, provided the hosting application passes network-received data directly to the Outside In SDK. Successful exploitation can result in unauthorized read access to all accessible data, unauthorized modification (update, insert, or delete) of some data, and a partial denial of service. The vulnerability is classified as easily exploitable with a low attack complexity. Oracle addressed this issue in the January 2017 Critical Patch Update.
Affected products
- Oracle Outside In Technology 8.5.2, 8.5.3
Timeline
- 2017-01-27: advisory: NVD publication date
- 2017-01-17: patched: Addressed in Oracle January 2017 Critical Patch Update