CVE-2008-6786 Multiple directory traversal vulnerabilities in geekigeeki.py in GeekiGeeki before 3.0 allow remote attackers to read arbitrary files via di
Medium 5.0
Published
Updated
Check this codebase for CVE-2008-6786 and fix it if it is affected.
What it is: CVE-2008-6786 is a medium-severity vulnerability in n/a, published on 1 May 2009.
Exploitation: There is no known exploitation of CVE-2008-6786 in the wild and no public exploit code.
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-6786/ (Markdown: https://insights.sbomify.com/CVE-2008-6786/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2008-6786?
CVE-2008-6786 is a medium-severity vulnerability in n/a, published on 1 May 2009.
Official description
Multiple directory traversal vulnerabilities in geekigeeki.py in GeekiGeeki before 3.0 allow remote attackers to read arbitrary files via directory traversal sequences in a pagename argument in the (1) handle_edit and (2) handle_raw functions.
Weakness: CWE-22
Which versions are affected by CVE-2008-6786?
It affects 1 product.
Products include Codewiz Geekigeeki.
How do I fix CVE-2008-6786?
No fix has been published for CVE-2008-6786 yet. Limit exposure of the affected software until one is available.
Is CVE-2008-6786 being exploited?
There is no known exploitation of CVE-2008-6786 in the wild and no public exploit code.
Sources
Also known as GHSA-x4cw-pvcr-8p4m.