CVE-2018-2560 json
Vulnerability in the Solaris component of Oracle Sun Systems Products Suite (subcomponent: Kernel).
published 2018-01-18 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-14415
- cvss
- 5.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Vulnerability in the Solaris component of Oracle Sun Systems Products Suite (subcomponent: Kernel). The supported version that is affected is 11.3. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Solaris executes to compromise Solaris. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Solaris, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Solaris accessible data. CVSS 3.0 Base Score 5.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N).
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.0 | CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N |
| NVD | 2.0 | 1.2 | AV:L/AC:H/Au:N/C:P/I:N/A:N |
Affected products
- Oracle Corporation Solaris Operating System
References
-
oracle.com
/technetwork/security-advisory/cpujan2018-3236628.html
patch, vendor-advisory
-
securitytracker.com
/id/1040215
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/102617
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-2560
- NVD CVE-2018-2560
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.