CmanApplication · Redhat
CVE-2008-6560
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 · uneditedBuffer overflow in CMAN - The Cluster Manager before 2.03.09-1 on Fedora 9 and Red Hat Enterprise Linux (RHEL) 5 allows attackers to cause a denial of service (CPU consumption and memory corruption) via a cluster.conf file with many lines. NOTE: it is not clear whether this issue crosses privilege boundaries in realistic uses of the product.
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 confidenceBuffer overflow vulnerability in CMAN (Cluster Manager) allows denial of service through specially crafted cluster.conf files containing excessive lines, causing CPU consumption and memory corruption.
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
CmanApplication
<= 2.03.08-1= 2.03.03-1= 2.03.04-1= 2.03.05-1= 2.03.07-1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if CMAN is installedQuery the package manager for CMAN (Cluster Manager) package, or check running processes for cman daemonAffected if CMAN package is present and running on the system
-
Determine installed CMAN versionUse package manager query (rpm -q cman, dpkg -l, or similar) to retrieve the exact version number of the CMAN packageAffected if Version matches <= 2.03.08-1, or equals exactly 2.03.03-1, 2.03.04-1, 2.03.05-1, or 2.03.07-1
-
Locate cluster.conf fileFind the cluster.conf file typically located in /etc/cluster/ or /etc/ directory - this is the cluster configuration file parsed by CMANAffected if cluster.conf file exists and is being used by CMAN
-
Inspect cluster.conf file size and contentsCheck the file size and line count of cluster.conf - look for unusually large files or files with excessive entries that could trigger the buffer overflowAffected if cluster.conf contains an abnormally large number of lines or entries relative to expected cluster configuration size
If CMAN is installed with a version matching the affected ranges (2.03.03-1 through 2.03.08-1 inclusive) and is actively parsing a cluster.conf file, the environment is vulnerable to the buffer overflow via specially crafted configuration files.
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 CMAN to version 2.03.09-1 or later, or apply vendor patches; validate and limit cluster.conf file size to prevent exploitation.
Fix this in Cman
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-6560 — 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-2008-6560 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