dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022.
SolarisOperating system · Oracle

CVE-2019-3010

HIGH · 8.8 CVSS v3.1 Published 2019-10-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
In the wild Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A privilege escalation vulnerability exists in XScreenSaver of Oracle Solaris 11, allowing a low-privileged user with local system access to gain complete control of the operating system. The vulnerability has a CVSS base score of 8.8 and can lead to full takeover of the affected system.

MitigationApply the Oracle Solaris patch for CVE-2019-3010. Until patched, restrict physical and console access to systems running Solaris 11 and ensure only trusted users have local accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolarisOperating system
Affected:= 11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Oracle Solaris version
    Run 'uname -a' or check '/etc/release' to confirm the system is running Oracle Solaris 11
    Affected if The system is not Oracle Solaris 11 (the vulnerability only affects Solaris 11)
  2. Determine if XScreenSaver is installed
    Use the Solaris package manager (pkg list or pkginfo) to list installed packages containing 'xscreensaver'
    Affected if XScreenSaver is not installed on the system
  3. Check if XScreenSaver daemon is running
    Run 'ps -ef | grep xscreensaver' to see if the XScreenSaver daemon process is active
    Affected if XScreenSaver process is not currently running on the system
  4. Verify XScreenSaver is accessible to local users
    Check that the XScreenSaver binary is executable by non-privileged users (ls -la on the xscreensaver binary)
    Affected if Standard users cannot execute the XScreenSaver binary

The system is affected if it runs Oracle Solaris 11 with XScreenSaver installed and executable by local users, allowing a low-privileged attacker to potentially escalate privileges through the XScreenSaver component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the Oracle Solaris patch for CVE-2019-3010. Until patched, restrict physical and console access to systems running Solaris 11 and ensure only trusted users have local accounts.

Recommended fix Moderate confidence

Solaris 11.4 latest SRU (e.g., 11.4.30 or later) or apply Oracle Critical Patch Update patch for CVE-2019-3010

  1. 1. Identify the current Oracle Solaris 11 version installed: `uname -a` and `cat /etc/release`
  2. 2. Check Oracle's official Critical Patch Update advisories for CVE-2019-3010 to obtain the specific patch number for Solaris 11
  3. 3. Obtain the patch from Oracle Support (My Oracle Security) or apply the latest Solaris 11.4 SRU (Solaris Release Update) that includes the fix
  4. 4. Apply the patch using `patchadd` or upgrade via `pkg update` for SRU-based systems
  5. 5. Verify the installation: `showrev -p | grep <patch_id>` or confirm XScreenSaver package version
  6. 6. Restart the system or at minimum restart XScreenSaver to ensure the fix takes effect
Caveat Standard upgrade risks apply - review Oracle upgrade documentation and test in non-production environment first; ensure backups exist before applying patches to production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solaris Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data