Skip to main content

CVE-2019-3010Oracle Solaris Privilege Escalation Vulnerability

Patch nowHigh8.8Exploited, CISA due date 2022-06-15EPSS 14%, higher than 96% of scored CVEs

CVE-2019-3010 is a vulnerability in Oracle Solaris, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

The record does not classify the weakness yet; the description below says what the reporter found.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. The damage can spread past the vulnerable component into others.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2022-05-25: it is being exploited in the wild. EPSS estimates a 14% chance of exploitation activity in the next 30 days, higher than 96% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-06-15.
  2. Apply the fix for Oracle Solaris: the patch and release notes are linked below.
  3. Limit who can run code or sign in on the hosts that run it.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

Vulnerability in the Oracle Solaris product of Oracle Systems (component: XScreenSaver). The supported version that is affected is 11. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris. While the vulnerability is in Oracle Solaris, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle Solaris. CVSS 3.0 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.

Questions to answer about your own systems

  • Where does Oracle Solaris run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.