dbcve.org
SolarisOperating system · Oracle

CVE-2014-0397

HIGH · 10.0 CVSS v2.0 Published 2014-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Multiple unspecified vulnerabilities in libXtsol in Oracle Solaris 10 and 11.1 have unspecified impact and attack vectors related to "Buffer errors."

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

Multiple buffer error vulnerabilities exist in libXtsol, a trusted Solaris library. These are memory corruption issues (likely buffer overflows) in a system-level security component. The CVSS 10 score indicates these are remotely exploitable and can lead to complete system compromise.

MitigationApply Oracle Critical Patch Updates for Solaris 10 and 11.1. If patches are unavailable, consider network isolation of affected systems and monitor for indicators of compromise.

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:= 10= 11.1

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 Solaris version
    Run 'uname -a' or 'cat /etc/release' to determine the exact Oracle Solaris version
    Affected if The system runs Solaris 10 (any update) or Solaris 11.1
  2. Locate libXtsol library
    Search for the library file using 'find /usr -name libXtsol* 2>/dev/null' or check /usr/lib directory
    Affected if The libXtsol library file exists on the system
  3. Check if libXtsol is in use
    Run 'ldd /usr/bin/*' or check running processes that may link this library, or inspect loaded modules with 'modinfo' if applicable
    Affected if Any process or service links against or loads libXtsol
  4. Verify library version
    Use 'pkginfo -l SUNWlibXtsol' on Solaris 10 or 'pkg list libXtsol' on Solaris 11.1 to check package version if available
    Affected if Unable to determine library version or version matches affected Solaris 10 or 11.1 releases

The system is affected if it runs Solaris 10 or 11.1 and has the libXtsol library present and actively used by any component.

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 Critical Patch Updates for Solaris 10 and 11.1. If patches are unavailable, consider network isolation of affected systems and monitor for indicators of compromise.

Fix this in Solaris Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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