Cluster ProjectApplication · Redhat

CVE-2008-6552

MEDIUM · 6.9 CVSS v2.0 Published 2009-03-30

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

74/100

Remediation priority · Elevated

No privileges Zero-click

Official description

NVD · unedited

Red Hat Cluster Project 2.x allows local users to modify or overwrite arbitrary files via symlink attacks on files in /tmp, involving unspecified components in Resource Group Manager (aka rgmanager) before 2.03.09-1, gfs2-utils before 2.03.09-1, and CMAN - The Cluster Manager before 2.03.09-1 on Fedora 9.

Technical summary

dbcve analysis · high confidence

Local privilege escalation vulnerability in Red Hat Cluster Project 2.x components (rgmanager, gfs2-utils, CMAN) allows local users to modify or overwrite arbitrary files via symlink attacks on predictable /tmp files before version 2.03.09-1. The vulnerability stems from insecure temporary file handling in cluster management utilities.

MitigationUpgrade affected components (rgmanager, gfs2-utils, CMAN) to version 2.03.09-1 or later. If these legacy components are still in use on modern systems, consider migration to supported cluster solutions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Cluster ProjectApplication

Affected:= 2.00.00= 2.01.00= 2.02.00= 2.03.00= 2.03.01= 2.03.03= 2.03.04= 2.03.05= 2.03.7= 2.03.08= 2.03.09= 2.03.10

CmanApplication

Affected:= 2.03.03-1= 2.03.04-1= 2.03.05-1= 2.03.07-1= 2.03.08-1

RgmanagerApplication

Affected:= 2.03.03-1= 2.03.04-1= 2.03.05-1= 2.03.07-1= 2.03.08-1

FedoraOperating system

Affected:= 9

Gfs2 UtilsApplication

Affected:= 2.03.03-1= 2.03.04-1= 2.03.05-1= 2.03.07-1= 22.03.08-1

CVSS breakdown

From the vector

Attack vector: Local
Complexity: M
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

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

Am I affected?

dbcve checks

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

Identify installed cluster packages

Run 'rpm -qa | grep -E "(rgmanager|gfs2-utils|cman)"' to list installed Red Hat cluster components

Affected if Any of the packages rgmanager, gfs2-utils, or cman are installed
Check package version

Run 'rpm -q --queryformat "%{VERSION}-%{RELEASE}" <package_name>' for each installed package to get the exact version number

Affected if Version is 2.03.03-1 through 2.03.08-1, or matches 2.00.00 through 2.03.10 in the Redhat Cluster Project list, or is Fedora 9
Verify temporary file usage

Review the binaries in /usr/sbin/ (rgmanager, cman) and /usr/bin/ (gfs2-utils) for any temporary file operations in /tmp during execution using strace or by examining source if available

Affected if The utilities create or manipulate files in /tmp with predictable names
Confirm symlink vulnerability context

Check for any existing symlinks or audit logs indicating symlink attacks on /tmp files used by cluster utilities

Affected if Predictable /tmp file names are used by the installed version without proper safe file handling

If rgmanager, gfs2-utils, or cman are installed at versions 2.03.03-1 through 2.03.08-1 or other affected versions listed, the system is vulnerable to local privilege escalation via symlink attacks on insecure temporary files.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade affected components (rgmanager, gfs2-utils, CMAN) to version 2.03.09-1 or later. If these legacy components are still in use on modern systems, consider migration to supported cluster solutions.

Fix this in Cluster Project Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,040

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-6552 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2008-6552?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 6.9 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Cluster Project

Remediation

Need this fixed?

Fix this in Cluster Project 6 hrs · Moderate

Typical engagement from $1,040

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2008-6552 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References