SolarisOperating system · Oracle

CVE-2023-21984

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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: Libraries). The supported version that is affected is 11. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/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 · moderate confidence

Vulnerability in Oracle Solaris 11's Libraries component allows a low-privileged attacker with network access via HTTP to cause a complete denial of service, resulting in system hang or repeatable crashes. The attack requires no user interaction and exploits a flaw in library code used by network-accessible services.

MitigationApply Oracle's security patches for CVE-2023-21984 via Oracle Critical Patch Updates for Solaris 11. Restrict network access to Solaris systems and minimize exposed HTTP services until patching is complete.

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

CVSS:3.1/AV:N/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. Confirm Oracle Solaris version
    Run 'uname -a' or 'cat /etc/release' to identify the installed Solaris version
    Affected if The system is running Oracle Solaris 11 (version 11)
  2. Identify running network services
    Run 'svcs -a | grep online' to list all active services, then check for HTTP-listening services using 'netstat -an | grep LISTEN' or 'sockstat'
    Affected if HTTP network-accessible services are running on the system
  3. Check for exposed HTTP daemons
    Inspect configuration files in /etc/httpd/, /etc/apache2/, or service-specific configs to identify HTTP services bound to network interfaces
    Affected if HTTP services are configured to accept network connections (not localhost-only)
  4. Verify library dependencies
    Use 'ldd' on suspected vulnerable service binaries (such as httpd, apache, or Oracle HTTP Server) to identify which libraries from /usr/lib/ they load
    Affected if Network services link against libraries in the affected Oracle Solaris Libraries component
  5. Review network exposure
    Check firewall rules with 'ipf -V' or 'pfctl -sr' and review /etc/hosts.allow and /etc/hosts.deny for TCP wrapper configuration
    Affected if The system accepts network connections from untrusted sources on HTTP ports (typically 80/443)

The environment is affected if running Oracle Solaris 11 with any HTTP-listening network services exposed to untrusted network access, since the vulnerability resides in library code used by such 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.

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

Apply Oracle's security patches for CVE-2023-21984 via Oracle Critical Patch Updates for Solaris 11. Restrict network access to Solaris systems and minimize exposed HTTP services until patching is complete.

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-21984 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