dbcve.org
SolarisOperating system · Oracle

CVE-2010-3507

MEDIUM · 6.6 CVSS v2.0 Published 2010-10-14
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
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
Unspecified vulnerability in Oracle Solaris 8, 9, and 10 allows local users to affect confidentiality, integrity, and availability via unknown vectors related to Live Upgrade.

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 · low confidence

CVE-2010-3507 is an unspecified vulnerability in Oracle Solaris 8, 9, and 10 affecting the Live Upgrade feature. The vulnerability allows local users to impact confidentiality, integrity, and availability through unknown vectors, with a CVSS score of 6.6 indicating medium severity.

MitigationApply Oracle security patches for this vulnerability; if patches are unavailable for these end-of-life Solaris versions, consider upgrading or replacing the affected systems, and restrict local user access to sensitive areas.

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:= 8= 9= 10

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

AV:L/AC:M/Au:N/C:P/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 the Oracle Solaris version
    Run `uname -a` or `cat /etc/release` to determine the installed Solaris version
    Affected if The version displayed is 8, 9, or 10 (any update/_patch level within these major versions)
  2. Verify if Live Upgrade packages are installed
    Run `pkginfo | grep -i 'SUNWlu'` to list installed Live Upgrade packages (typically SUNWluu for Live Upgrade software and SUNWlur for runtime)
    Affected if Any Live Upgrade packages (SUNWluu or SUNWlur) are present on the system
  3. Check Live Upgrade kernel module availability
    Run `modinfo | grep lu` to see if Live Upgrade kernel modules are loaded
    Affected if Live Upgrade modules are loaded in memory
  4. Verify Live Upgrade command availability
    Check for the presence of Live Upgrade binaries by running `which luupgradel` or `ls /usr/lib/liveupgrade`
    Affected if Live Upgrade executables exist on the system

The system is affected if it runs Solaris 8, 9, or 10 AND has the Live Upgrade feature (packages or binaries) installed, regardless of whether it is actively in use.

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 security patches for this vulnerability; if patches are unavailable for these end-of-life Solaris versions, consider upgrading or replacing the affected systems, and restrict local user access to sensitive areas.

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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 locally
dbcve dependency scanner

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