CVE-2007-5626
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedmake_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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe make_catalog_backup script in Bacula 2.2.5 passes MySQL passwords as command-line arguments, which are exposed through process listings and can be transmitted in cleartext emails. Attackers with local access can retrieve credentials via process enumeration, while network attackers can sniff the cleartext communication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.2.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bacula versionRun 'bacula-fd --version' or 'bacula-sd --version' or check package manager (rpm -q bacula, dpkg -l bacula)Affected if Version is 2.2.5 or lower
-
Locate the make_catalog_backup scriptFind the script using 'find / -name make_catalog_backup 2>/dev/null' or check common paths like /usr/lib/bacula, /opt/bacula, or the scripts directory in Bacula installationAffected if Script exists and is from Bacula <= 2.2.5
-
Inspect script for password handlingOpen the make_catalog_backup script and search for lines where MySQL_PASSWORD or database passwords are passed as command-line arguments (look for $MYSQL_PASSWORD in command strings)Affected if The script passes passwords as command-line arguments to mysql or mysqldump commands
-
Check process listings for exposed credentialsRun 'ps aux | grep -i mysql' or 'ps aux | grep catalog' while a backup job or catalog backup is runningAffected if Passwords are visible in plain text in process command lines
-
Verify backup communication encryption statusCheck Bacula director configuration (bacula-dir.conf) for TLS (encryption) settings in the FileDaemon, StorageDaemon, and Director resourcesAffected if TLS/encryption is not enabled for backup communications
A user is affected if running Bacula version 2.2.5 or lower where the make_catalog_backup script passes MySQL passwords as command-line arguments, exposing them via process listings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a Bacula version that uses secure credential handling (environment variables or config files with restricted permissions) instead of command-line arguments, and ensure sensitive backup communications are encrypted.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-5626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data