CVE-2010-0882
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 · uneditedUnspecified vulnerability in the Solaris component in Oracle Sun Product Suite 10 and OpenSolaris snv_134 allows local users to affect confidentiality, integrity, and availability via unknown vectors related to Trusted Extensions.
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 confidenceLocal privilege or configuration vulnerability in Oracle Solaris 10 and OpenSolaris Trusted Extensions component allowing a local authenticated user to potentially escalate privileges or undermine the multi-level security controls implemented by Trusted Extensions, affecting confidentiality, integrity, and availability.
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.0= snv_134CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Trusted Extensions is enabledRun 'txzonemgr -l' or check the Trusted Extensions status via 'svcs -a | grep tx' or look for TX in the output of 'showrev -p' related to trusted extensions packagesAffected if Trusted Extensions is enabled and the system is Oracle Solaris 10 or OpenSolaris snv_134 or earlier
-
Determine the installed Solaris versionRun 'showrev -a' or 'cat /etc/release' to identify the exact Solaris version installedAffected if The version is Oracle Solaris 10 (any update) or OpenSolaris at or before snv_134
-
Verify the kernel patch levelRun 'showrev -p' and examine the kernel patch numbers, particularly looking at patches related to Trusted Extensions (typically packages containing 'SUNWtsu' or 'SUNWtx')Affected if The system is running an unpatched kernel and Trusted Extensions is active
-
Confirm local authenticated user accessVerify that local user accounts exist on the system (check /etc/passwd or use 'logins' command)Affected if Local authenticated users can access the system, which is required for this privilege escalation vulnerability to be exploitable
The system is affected if it runs Oracle Solaris 10 or OpenSolaris snv_134 or earlier with Trusted Extensions enabled and has not applied the relevant security patches for this CVE.
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 Oracle Solaris security patches for CVE-2010-0882 if available; if no patch exists, evaluate disabling Trusted Extensions or upgrading to a supported Solaris release as the product is EOL.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0882 — 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-2010-0882 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