dbcve.org
SolarisOperating system · Oracle

CVE-2017-3565

HIGH · 7.9 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 →
79/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 unauthorized creation, deletion or modification access to critical data or all Solaris accessible data as well as unauthorized access to critical data or complete access to all Solaris accessible data. CVSS 3.0 Base Score 7.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N).

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

Vulnerability in Solaris 11.3's Role-Based Access Control (RBAC) subcomponent allowing a low-privileged local attacker to modify RBAC configurations, potentially gaining unauthorized access to critical data or complete access to all Solaris accessible data. The attack requires local access and human interaction, and while confined to Solaris, may significantly impact additional products that depend on RBAC for access control.

MitigationApply the Oracle critical patch update for CVE-2017-3565 to Solaris 11.3, or review and harden RBAC policies to restrict low-privileged users from modifying critical RBAC authorizations.

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
None

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

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. Confirm Solaris 11.3 is installed
    Run 'cat /etc/release' or 'uname -a' to display the OS version. Look for 'Oracle Solaris 11.3' in the output.
    Affected if The system is running Oracle Solaris version 11.3 exactly.
  2. Verify RBAC is enabled
    Check if RBAC is active by viewing the /etc/user_attr file. Run 'cat /etc/user_attr' to see if any users have defined roles, profiles, or authorizations.
    Affected if RBAC is enabled and configured with user attributes in /etc/user_attr.
  3. Identify profiles with RBAC modification rights
    Examine the /etc/security/exec_attr file for profiles containing 'solaris.*' or 'RBAC' related entries. Run 'grep -i rbac /etc/security/exec_attr' or review profile entries that grant user administration capabilities.
    Affected if Profiles exist that grant RBAC modification capabilities to non-privileged users.
  4. Check for low-privileged users with elevated authorizations
    Review /etc/user_attr for users assigned 'solaris.*' authorizations or profiles without root privileges. Look for entries where type='normal' users have role or profile assignments.
    Affected if Non-root users have been granted RBAC roles, profiles, or authorizations.
  5. Audit recent RBAC configuration changes
    Run 'logins -l' or review audit logs in /var/adm for changes to RBAC files (/etc/user_attr, /etc/security/*_attr, /etc/security/prof_attr) within recent activity.
    Affected if RBAC configuration files have been modified or there are unexpected changes to user authorizations.

A system is affected if it runs Oracle Solaris 11.3, has RBAC enabled, and contains low-privileged accounts with RBAC modification capabilities or unexpected authorization changes.

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-3565 to Solaris 11.3, or review and harden RBAC policies to restrict low-privileged users from modifying critical RBAC authorizations.

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-3565 — 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-3565 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