dbcve.org
SolarisOperating system · Oracle

CVE-2017-3564

HIGH · 8.2 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High

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: RBAC). The supported version that is affected is 11.3. Easily "exploitable" vulnerability allows low 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 takeover of Solaris. CVSS 3.0 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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

This is a local privilege escalation vulnerability in Oracle Solaris 11.3's Role-Based Access Control (RBAC) subsystem. A low-privileged attacker with valid logon access can exploit this to gain elevated privileges and achieve complete takeover of the Solaris system. The vulnerability requires human interaction from another person, and while initially affecting Solaris RBAC, attacks can impact additional products in the environment.

MitigationApply the Oracle critical patch update for CVE-2017-3564 to Solaris 11.3, and review RBAC role configurations to ensure no unauthorized privilege escalation paths exist.

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.3

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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 'pkg list entire' or 'cat /etc/release' to confirm the exact Solaris version installed
    Affected if The system is running Oracle Solaris 11.3 exactly (version 11.3)
  2. Verify RBAC subsystem is in use
    Check if RBAC is enabled by examining /etc/user_attr or running 'roles' command for user accounts
    Affected if RBAC is configured and in use on the system, as the vulnerability exploits the RBAC subsystem
  3. Review existing RBAC role definitions
    Examine RBAC role configurations using 'rolemod -l <rolename>' or by inspecting /etc/security/auth_attr for defined roles
    Affected if Any RBAC roles exist on the system, particularly those with elevated privileges that could be exploited
  4. Audit user role assignments
    Check which users are assigned RBAC roles using 'profiles -l <username>' or by reviewing /etc/user_attr for user-role mappings
    Affected if Any users are assigned to RBAC roles, creating potential escalation paths
  5. Check for role authentication requirements
    Review RBAC role configuration to determine if roles require password authentication using 'rolemod -p <password> <rolename>' or examining /etc/security policy
    Affected if Roles permit authentication with user-provided credentials without proper verification controls

A system is affected if it runs Oracle Solaris 11.3 with RBAC enabled and has any RBAC roles configured that could be exploited through the authentication bypass for privilege escalation

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle critical patch update for CVE-2017-3564 to Solaris 11.3, and review RBAC role configurations to ensure no unauthorized privilege escalation paths exist.

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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