dbcve.org
SolarisOperating system · Oracle

CVE-2017-3623

CRITICAL · 10.0 CVSS v3.0 Published 2017-04-24
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 Solaris component of Oracle Sun Systems Products Suite (subcomponent: Kernel RPC). For supported versions that are affected see note. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Solaris. While the vulnerability is in Solaris, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Solaris. Note: CVE-2017-3623 is assigned for "Ebbisland". Solaris 10 systems which have had any Kernel patch installed after, or updated via patching tools since 2012-01-26 are not impacted. Also, any Solaris 10 system installed with Solaris 10 1/13 (Solaris 10 Update 11) are not vulnerable. Solaris 11 is not impacted by this issue. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/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

Unauthenticated remote code execution vulnerability in the Solaris Kernel RPC subsystem (Ebbisland) allowing complete system takeover via network protocols without any authentication. Affects Solaris 10 systems that have not received kernel patches since 2012-01-26 or are not on Solaris 10 1/13 (Update 11) or later. Solaris 11 is not affected.

MitigationApply Oracle kernel patch for CVE-2017-3623 or upgrade to Solaris 10 1/13 (Update 11) or later; for already-patched systems (post-2012-01-26), no action required.

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:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 Solaris version
    Run 'uname -a' and 'cat /etc/release' to determine if the system is Solaris 10 or Solaris 11
    Affected if System is Solaris 10; Solaris 11 is not affected by this CVE
  2. Check Solaris 10 update level
    Examine the output from 'cat /etc/release' for the version string. Look for 'Solaris 10 1/13' or later (Update 11)
    Affected if System is Solaris 10 and the version is earlier than 1/13 (Update 11)
  3. Verify kernel patch currency
    Run 'showrev -p | grep -i patch' to list installed kernel patches. Compare against patches released after January 26, 2012
    Affected if No kernel patches have been applied since 2012-01-26
  4. Check if RPC services are exposed
    Run 'rpcinfo -p' to enumerate active RPC services. Also check if the system has network-accessible RPC listeners via 'rpcinfo -p hostname' from a remote system
    Affected if The RPC subsystem is network-accessible and the system meets the version/patch criteria above

System is affected if it runs Solaris 10 earlier than Update 11 or lacks post-2012-01-26 kernel patches, and has network-accessible RPC services

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 Oracle kernel patch for CVE-2017-3623 or upgrade to Solaris 10 1/13 (Update 11) or later; for already-patched systems (post-2012-01-26), no action required.

Recommended fix High confidence

Solaris 10 1/13 (Update 11) or later, or Solaris 11.x

  1. Apply the Oracle Critical Patch Update (CPU) April 2017 kernel patch for Solaris 10. Refer to Oracle CPU April 2017 for the specific patch ID.
  2. Alternatively, upgrade to Solaris 10 1/13 (Solaris 10 Update 11) or later which includes the fix.
  3. Alternatively, upgrade to Solaris 11 which is not impacted by this vulnerability.
  4. After patching or upgrading, verify the fix by confirming the kernel patch level is beyond the 2012-01-26 baseline or running the latest Solaris 10 Update 11+ kernel.
Caveat Upgrading Solaris releases may require testing of applications and services for compatibility with the newer OS version

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

Fix this in Solaris Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3623 — 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-2017-3623 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