# CVE-2007-2766: Information disclosure in n/a

> Local attackers can obtain MySQL passwords by inspecting process arguments in Backup Manager, leading to credential disclosure.

- **Severity:** High 7.2 (`AV:L/AC:L/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:** 18 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2766, GHSA-w99m-9m8w-9wj5

## What is CVE-2007-2766?

CVE-2007-2766 is a high-severity vulnerability in n/a, published on 18 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lib/backup-methods.sh in Backup Manager before 0.7.6 provides the MySQL password as a plaintext command line argument, which allows local users to obtain this password by listing the process and its arguments, related to lib/backup-methods.sh.

Weakness: CWE-255

## Which versions are affected by CVE-2007-2766?

It affects 1 product.


Products: Backup Manager Backup Manager.

## How do I fix CVE-2007-2766?

Upgrade to a fixed version.

## Is CVE-2007-2766 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4656](https://insights.sbomify.com/CVE-2007-4656/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2766 and fix it if it is affected.

What it is: CVE-2007-2766 is a high-severity vulnerability in n/a, published on 18 May 2007. 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-2007-2766 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-2007-2766/ (Markdown: https://insights.sbomify.com/CVE-2007-2766/index.md)
```

## Sources

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

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