CVE-2017-3500 json
Vulnerability in the Primavera Gateway component of Oracle Primavera Products Suite (subcomponent: Primavera Desktop Integration).
published 2017-04-24 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-12621
- cvss
- 8.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Vulnerability in the Primavera Gateway component of Oracle Primavera Products Suite (subcomponent: Primavera Desktop Integration). Supported versions that are affected are 1.0, 1.1, 14.2, 15.1, 15.2, 16.1 and 16.2. Easily "exploitable" vulnerability allows high privileged attacker with network access via HTTP to compromise Primavera Gateway. While the vulnerability is in Primavera Gateway, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Primavera Gateway accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Primavera Gateway. CVSS 3.0 Base Score 8.7 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H).
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
2.00% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.7 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H |
| NVD | 2.0 | 4.9 | AV:N/AC:M/Au:S/C:P/I:N/A:P |
Affected products
- Oracle Corporation Primavera Gateway
References
-
oracle.com
/technetwork/security-advisory/cpuapr2017-3236618.html
patch, vendor-advisory
-
securityfocus.com
/bid/97881
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038289
vdb-entry
Sources
- CVE List CVE-2017-3500
- NVD CVE-2017-3500
Fencer Vulns 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.