CVE-2007-2267
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 Sun Cluster 3.1 and Solaris Cluster 3.2 before 20070424 allows remote authenticated users, operating from a different cluster node, to cause a denial of service (data corruption or send_mondo panic) via unspecified vectors, as demonstrated by EMC Symcli backup software 6.2.1.
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 confidenceUnspecified vulnerability in Sun Cluster 3.1 and Solaris Cluster 3.2 (pre-20070424) allows remote authenticated users operating from one cluster node to cause denial of service (data corruption or send_mondo panic) on another cluster node via unspecified vectors, as demonstrated by EMC Symcli backup software.
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= 3.1= 3.2CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/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.
-
Identify installed Sun Cluster or Solaris Cluster versionRun 'scinstall -p' or check /usr/cluster/lib/rgm/cluster/version file; alternatively use 'cluster show - verbose' to display cluster version informationAffected if The version shown is 3.1 or 3.2 and was released before April 24, 2007 (20070424)
-
Determine the exact release date of the installed versionCross-reference the installed version number with Sun's patch release notes or Solaris Cluster documentation to confirm the release dateAffected if The release date predates 20070424
-
Confirm the system is configured as an active clusterRun 'cluster status' or check for multiple nodes communicating via cluster interconnect using 'clinterconnect status'Affected if Multiple cluster nodes are active and communicating over the cluster interconnect
-
Check for authenticated user access between cluster nodesReview /etc/hosts.equiv, rsh/rcp configuration, SSH key-based authentication, or user equivalence settings that allow commands from one node to execute on anotherAffected if User authentication is configured allowing remote operations from one cluster node to another without interactive password entry
-
Inspect for EMC Symcli or similar backup software configurationCheck for presence of EMC Symcli binaries (typically in /usr/symcli) or backup scripts using this software in /etc/crontab, /usr/local/crontab, or cluster resource groupsAffected if EMC Symcli backup software is installed and configured to run cluster-aware backup operations
A system is affected if it runs Sun Cluster 3.1 or Solaris Cluster 3.2 with a release date before 20070424 and has authenticated inter-node access configured, particularly when EMC Symcli or similar backup software is in use.
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 dataUpgrade to Solaris Cluster 3.1 or 3.2 post-20070424, or migrate to a supported Solaris Cluster version. If upgrade is not immediately feasible, restrict cluster interconnect access to trusted nodes and monitor for anomalous backup operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2267 — 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-2007-2267 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