dbcve.org
SolarisOperating system · Sun

CVE-2008-2946

HIGH · 7.8 CVSS v2.0 Published 2008-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
The SNMP-DMI mapper subagent daemon (aka snmpXdmid) in Solstice Enterprise Agents in Sun Solaris 8 through 10 allows remote attackers to cause a denial of service (daemon crash) via malformed packets.

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

The SNMP-DMI mapper subagent daemon (snmpXdmid) in Sun Solaris 8 through 10, part of Solstice Enterprise Agents, crashes when receiving malformed SNMP packets, allowing remote unauthenticated attackers to cause denial of service.

MitigationIf the snmpXdmid service is not required, disable it. Otherwise, restrict SNMP access at network perimeter or apply available patches from Oracle for legacy Solaris systems.

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

AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Solaris version
    Run 'uname -r' or 'cat /etc/release' to confirm the installed Solaris version. Look for 5.8 (Solaris 8), 5.9 (Solaris 9), or 5.10 (Solaris 10).
    Affected if The system runs Solaris 8, 9, or 10 (Sunos 5.8, 5.9, or 5.10)
  2. Check if snmpXdmid package is installed
    Run 'pkginfo | grep -i snmp' or 'ls -la /usr/lib/snmpXdmid' to see if the SNMP-DMI mapper package exists on the system.
    Affected if The snmpXdmid package (Solstice Enterprise Agents SNMP-DMI mapper) is installed
  3. Verify if snmpXdmid service is running
    Run 'ps -ef | grep snmpXdmid' or check via SMF: 'svcs -a | grep snmpXdmid' to determine if the daemon is currently active.
    Affected if The snmpXdmid process or service is currently running
  4. Check SNMP network exposure
    Run 'netstat -an | grep 161' or use 'nmap -sU -p 161 target' to see if UDP port 161 (SNMP) is listening and accessible from network.
    Affected if SNMP service (UDP port 161) is listening and accessible to untrusted networks

A system is affected if it runs Solaris 8, 9, or 10 with the snmpXdmid daemon installed, running, and exposed to network access.

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

If the snmpXdmid service is not required, disable it. Otherwise, restrict SNMP access at network perimeter or apply available patches from Oracle for legacy Solaris systems.

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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