dbcve.org
SolarisOperating system · Sun

CVE-2007-3094

HIGH · 9.0 CVSS v2.0 Published 2007-06-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 the authentication mechanism in Solaris Management Console (SMC) on Sun Solaris 8 through 10 before 20070605 allows remote authenticated users to execute arbitrary code via unspecified vectors, related to the WBEM server.

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

A detailed technical summary for this CVE is being prepared.

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.0= 9.0= 10.0
SunosOperating system
Affected:= 5.8= 5.9= 5.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
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.securityfocus.com →
Recommended fix Moderate confidence

Oracle Solaris 11.4 (current stable release) or Oracle Solaris 10 1/13 with latest security patches

  1. 1. Identify the current Solaris version using 'uname -a' and 'cat /etc/release'
  2. 2. Oracle Solaris is now the successor to Sun Solaris; access Oracle's support portal for patches (support.oracle.com)
  3. 3. For legacy Sun Solaris systems, check historical patches on SunSolve (sunsolve.sun.com) for patches released around June 2007 addressing SMC/WBEM vulnerabilities
  4. 4. If the system cannot be patched, consider disabling the Solaris Management Console (SMC) service: svcadm disable smc
  5. 5. If WBEM is not required, disable it: svcadm disable wbem
  6. 6. Restrict network access to the SMC port (898/TCP) via IPF or IPFILTER rules
  7. 7. Apply the most recent Oracle Solaris security patches for your version after upgrading
Caveat Upgrading from Sun Solaris 10 to Oracle Solaris 11 may require application compatibility testing; some legacy SMC features may not be available in newer versions

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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