# CVE-2008-6552: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks in Red Hat Cluster Project components, potentially compromising system integrity.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mmp4-x7mg-mw3w, RHSA-2009:1337, RHSA-2009:1339, RHSA-2011:0265

## What is CVE-2008-6552?

CVE-2008-6552 is a medium-severity path traversal vulnerability in Fedoraproject Fedora, published on 30 Mar 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2008-6552?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gfs2-utils` | Red Hat:enterprise_linux:5::client | All versions | 0:0.1.62-1.el5 |
| `gfs2-utils-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.1.62-1.el5 |
| `gfs2-utils` | Red Hat:enterprise_linux:5::server | All versions | 0:0.1.62-1.el5 |
| `gfs2-utils-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.1.62-1.el5 |
| `ccs` | Red Hat:rhel_cluster:4 | All versions | 0:1.0.13-2 |
| `ccs-debuginfo` | Red Hat:rhel_cluster:4 | All versions | 0:1.0.13-2 |
| `ccs-devel` | Red Hat:rhel_cluster:4 | All versions | 0:1.0.13-2 |
| `rgmanager` | Red Hat:rhel_cluster:5 | All versions | 0:2.0.52-1.el5 |
| `rgmanager-debuginfo` | Red Hat:rhel_cluster:5 | All versions | 0:2.0.52-1.el5 |

Products: Fedoraproject Fedora, Redhat Cluster Project, Redhat Cman, Redhat Gfs2-Utils, Redhat Rgmanager.

## How do I fix CVE-2008-6552?

Apply the vendor's patch.

## Is CVE-2008-6552 being exploited?

There is no known exploitation of CVE-2008-6552 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6552 and fix it if it is affected.

What it is: CVE-2008-6552 is a medium-severity path traversal vulnerability in Fedoraproject Fedora, published on 30 Mar 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-6552 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-6552/ (Markdown: https://insights.sbomify.com/CVE-2008-6552/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-6552
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-6552
- OSV: https://osv.dev/vulnerability/CVE-2008-6552

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-6552/
Summaries are generated and may contain mistakes; the official description above is the record.