CVE-2006-4117
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 · uneditedThe squeue_drain function in Sun Solaris 10, possibly only when run on CMT processors, allows remote attackers to cause a denial of service ("bad trap" and system panic) by opening and closing a large number of TCP connections ("heavy TCP/IP loads"). NOTE: the original report specifies the function name as "drain_squeue," but this is likely incorrect.
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 confidenceSun Solaris 10 contains a vulnerability in the squeue_drain function where rapid opening and closing of TCP connections (heavy TCP/IP loads), particularly on CMT processors, triggers a 'bad trap' causing kernel panic and denial of service. The issue resides in the TCP/IP stack's connection handling subsystem.
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= 10.0CVSS 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
- High
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:H/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the installed Solaris 10 versionRun 'uname -a' or 'cat /etc/release' to identify the exact Solaris version. The vulnerability affects Solaris 10.0 specifically.Affected if The system is running Solaris 10.0 (initial release) rather than a later update version.
-
Determine if the system uses CMT processorsCheck the system hardware configuration using 'psrinfo -v' or 'prtdiag -v' to see if Chip Multi-Threading (CMT) processors are present. CMT processors are a prerequisite for this specific vulnerability.Affected if The system has CMT processors (such as UltraSPARC T1/T2) and is running Solaris 10.0.
-
Check for high TCP connection turnover exposureReview network traffic patterns and connection logs to determine if the system handles rapid opening and closing of TCP connections. Use 'netstat -s' or monitoring tools to observe TCP connection patterns.Affected if The system is exposed to heavy TCP/IP loads with rapid connection open/close cycles.
-
Look for evidence of kernel panicsCheck system crash dump directory (/var/crash) or system logs for 'bad trap' messages or kernel panic events that could be related to this vulnerability.Affected if The system has experienced kernel panics or 'bad trap' errors under high TCP connection load.
A system is affected if it is running the initial Solaris 10.0 release on CMT processor hardware and is exposed to heavy TCP connection activity that has triggered or could trigger kernel panic.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Sun/Oracle security patches for Solaris 10; if patches are unavailable due to EOL status, consider network-level rate limiting or upgrading to a supported OS version. Firewall rules restricting rapid connection rates may provide interim mitigation.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4117 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-4117 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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