# CVE-2008-0905: Directory traversal vulnerability in globsy_edit.php in Globsy 1.0 allows remote attackers to read arbitrary files via a ..


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cp6v-vwwq-5gw4

## What is CVE-2008-0905?

CVE-2008-0905 is a medium-severity vulnerability in n/a, published on 22 Feb 2008. 

### Official description

Directory traversal vulnerability in globsy_edit.php in Globsy 1.0 allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Meo Globsy.

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

No fix has been published for CVE-2008-0905 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-0905 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0905 exists.

Public exploit code:

- Globsy 1.0 - 'file' Remote File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0905 is a medium-severity vulnerability in n/a, published on 22 Feb 2008. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0905 exists.

Affected product: n/a. 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-0905/ (Markdown: https://insights.sbomify.com/CVE-2008-0905/index.md)
```

## Sources

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

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