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

> Attackers can obtain MySQL passwords by inspecting process arguments or sniffing cleartext emails containing command lines in Bacula.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 23 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5626, GHSA-2r7q-8h3w-q3pc

## What is CVE-2007-5626?

CVE-2007-5626 is a medium-severity vulnerability in n/a, published on 23 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

make_catalog_backup in Bacula 2.2.5, and probably earlier, sends a MySQL password as a command line argument, and sometimes transmits cleartext e-mail containing this command line, which allows context-dependent attackers to obtain the password by listing the process and its arguments, or by sniffing the network.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Bacula Bacula.

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

Apply the vendor's patch.

## Is CVE-2007-5626 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5373](https://insights.sbomify.com/CVE-2008-5373/): Path traversal in n/a (medium 6.9)
- [CVE-2012-4430](https://insights.sbomify.com/CVE-2012-4430/): Missing authorization in n/a (medium 4.0)
- [CVE-2005-2995](https://insights.sbomify.com/CVE-2005-2995/): Path traversal in n/a (low 3.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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