# CVE-2009-0767: Information disclosure in n/a

> Remote attackers can download sensitive credential files from the web root due to insufficient access control in Kipper.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vx9q-r464-6v8x

## What is CVE-2009-0767?

CVE-2009-0767 is a medium-severity vulnerability in n/a, published on 3 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kipper 2.01 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a file containing credentials via a direct request for job/config.data.

Weakness: CWE-264

## Which versions are affected by CVE-2009-0767?

It affects 1 product.


Products: Bookelves Kipper.

## How do I fix CVE-2009-0767?

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

## Is CVE-2009-0767 being exploited?

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

Public exploit code:

- Kipper 2.01 - Cross-Site Scripting / Local File Inclusion / File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0765](https://insights.sbomify.com/CVE-2009-0765/): Path traversal in n/a (high 7.5)
- [CVE-2009-0766](https://insights.sbomify.com/CVE-2009-0766/): Path traversal in n/a (high 7.5)
- [CVE-2009-0763](https://insights.sbomify.com/CVE-2009-0763/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-0764](https://insights.sbomify.com/CVE-2009-0764/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0767 and fix it if it is affected.

What it is: CVE-2009-0767 is a medium-severity vulnerability in n/a, published on 3 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0767 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-2009-0767/ (Markdown: https://insights.sbomify.com/CVE-2009-0767/index.md)
```

## Sources

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

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