CVE-2017-10059 json
Vulnerability in the BI Publisher component of Oracle Fusion Middleware (subcomponent: Mobile Service).
published 2017-08-08 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-1706
- cvss
- 7.6
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Vulnerability in the BI Publisher component of Oracle Fusion Middleware (subcomponent: Mobile Service). The supported version that is affected is 11.1.1.7.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise BI Publisher. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in BI Publisher, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all BI Publisher accessible data as well as unauthorized update, insert or delete access to some of BI Publisher accessible data. CVSS 3.0 Base Score 7.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N).
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.6 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N |
| NVD | 2.0 | 4.9 | AV:N/AC:M/Au:S/C:P/I:P/A:N |
Affected products
- Oracle Corporation BI Publisher (formerly XML Publisher)
References
-
oracle.com
/technetwork/security-advisory/cpujul2017-3236622.html
patch, vendor-advisory
-
securityfocus.com
/bid/99743
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038940
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-10059
- NVD CVE-2017-10059
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.