Quick answers
- Is CVE-2017-3255 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2017-3255 being exploited in the wild.
- How severe is CVE-2017-3255?
- Medium severity, with a CVSS score of 5.8, published 27 January 2017.
- Which products and versions are affected?
- Oracle Jdeveloper 11.1.1.7.0, 11.1.1.9.0, 11.1.2.4.0, 12.1.3.0.0, 12.2.1.0.0, 12.2.1.1.0, 12.2.1.2.0.
- Is there a fix for CVE-2017-3255?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2017-3255 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2017-3255?
- Check whether you run Oracle Jdeveloper 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
This vulnerability (CWE-200) is located in the ADF Faces subcomponent of Oracle JDeveloper. It is classified as an information exposure flaw that can be exploited by an unauthenticated attacker via the HTTP protocol. The attack vector is network-based and requires low complexity with no user interaction. While the vulnerability resides in JDeveloper, the 'Scope' metric is changed (S:C), indicating that an exploit can impact components beyond the immediate security scope of the vulnerable software. Attackers can achieve unauthorized read access to sensitive data. Oracle addressed this in the January 2017 Critical Patch Update.
Affected products
- Oracle JDeveloper 11.1.1.7.0, 11.1.1.9.0, 11.1.2.4.0, 12.1.3.0.0, 12.2.1.0.0, 12.2.1.1.0, 12.2.1.2.0
Timeline
- 2017-01-27: disclosed
- 2017-01-27: advisory: Oracle Critical Patch Update published