dbcve.org
SolarisOperating system · Oracle

CVE-2022-39417

MEDIUM · 5.5 CVSS v3.1 Published 2022-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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: Filesystem). 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. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris. CVSS 3.1 Base Score 5.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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

Local DoS vulnerability in Oracle Solaris 11 filesystem component. A low-privileged attacker with local system access can exploit this to cause a system hang or crash, resulting in complete denial of service.

MitigationApply Oracle Critical Patch Update or security patch for CVE-2022-39417 when available. Restrict local access to trusted users and follow principle of least privilege.

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 operating system
    Run 'uname -a' or 'cat /etc/release' to confirm the system is Oracle Solaris
    Affected if The system is not Oracle Solaris 11
  2. Verify the exact Solaris 11 version
    Run 'showrev -p' or 'cat /etc/release' to determine the precise version and patch level of Solaris 11
    Affected if The installed version is Oracle Solaris 11 (any patch level, since version =11 is affected)
  3. Confirm local user access exists
    Check for the presence of non-privileged user accounts using 'getent passwd' or review /etc/passwd
    Affected if Low-privileged or untrusted local users have access to the system
  4. Identify exposed filesystem components
    Review running filesystem services and mounts using 'mount' and 'df -h' commands to identify active filesystem resources
    Affected if Filesystem components are exposed and accessible to low-privileged local users

The environment is affected if the system is running Oracle Solaris 11 and low-privileged local users have access to exposed filesystem components that can be triggered to cause a hang or crash.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update or security patch for CVE-2022-39417 when available. Restrict local access to trusted users and follow principle of least privilege.

Recommended fix Moderate confidence

Oracle Solaris 11.4 latest available SRU (Solaris Recommended Update) - contact Oracle Support for specific patch number

  1. Verify current Oracle Solaris 11 version using 'uname -a' and 'cat /etc/release'
  2. Backup critical data and configurations before applying updates
  3. Connect to Oracle support portal (support.oracle.com) and download the latest Solaris 11.4 SRU (Solaris Recommended Update) or patch bundle
  4. Apply the update using 'pkg update' command or Oracle's recommended patch installation procedure
  5. Reboot the system if required by the update
  6. Verify the CVE-2022-39417 is addressed by checking Oracle's patch documentation for the installed version
  7. Confirm the system is running the patched version using 'uname -a'
Caveat Review Oracle Solaris 11.4 release notes for any compatibility considerations before applying updates; ensure applications are tested for compatibility with the newer SRU

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

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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