CVE-2017-3555 json
Vulnerability in the Oracle iReceivables component of Oracle E-Business Suite (subcomponent: Self Registration).
published 2017-04-24 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-12675
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Vulnerability in the Oracle iReceivables component of Oracle E-Business Suite (subcomponent: Self Registration). Supported versions that are affected are 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5 and 12.2.6. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle iReceivables. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle iReceivables. CVSS 3.0 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
2.57% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- Oracle Corporation iReceivables
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
oracle.com
/technetwork/security-advisory/cpuapr2017-3236618.html
vendor-advisory
- erpscan.io /advisories/erpscan-17-024-dos-oracle-e-business-suite-anonymouslogin/
-
securitytracker.com
/id/1038299
vdb-entry
-
securityfocus.com
/bid/97757
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-3555
- NVD CVE-2017-3555
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.