# CVE-2008-6756: Information disclosure in n/a

> Local attackers can read the ZoneMinder configuration file to obtain database credentials due to insecure file permissions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 27 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-6756, GHSA-cwv7-hqww-jxgw

## What is CVE-2008-6756?

CVE-2008-6756 is a low-severity vulnerability in Zoneminder Zoneminder, published on 27 Apr 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ZoneMinder 1.23.3 on Gentoo Linux uses 0644 permissions for /etc/zm.conf, which allows local users to obtain the database username and password by reading this file.

Weakness: CWE-264

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

It affects 1 product.


Products: Zoneminder Zoneminder.

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

Apply the vendor's patch.

## Is CVE-2008-6756 being exploited?

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

## Other vulnerabilities in Zoneminder Zoneminder

- [CVE-2008-3882](https://insights.sbomify.com/CVE-2008-3882/): Command injection in n/a (critical 10.0)
- [CVE-2025-65791](https://insights.sbomify.com/CVE-2025-65791/): Command injection in n/a (critical 9.8)
- [CVE-2024-43360](https://insights.sbomify.com/CVE-2024-43360/): ZoneMinder Time-based SQL Injection (critical 9.8)
- [CVE-2022-29806](https://insights.sbomify.com/CVE-2022-29806/): Path traversal in n/a (critical 9.8)
- [CVE-2019-8423](https://insights.sbomify.com/CVE-2019-8423/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6756 is a low-severity vulnerability in Zoneminder Zoneminder, published on 27 Apr 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-6756 in the wild and no public exploit code.

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

## Sources

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

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