CVE-2025-67745: Myhoard logs backup encryption key in plain text
MyHoard is a daemon for creating, managing and restoring MySQL backups. Starting in version 1.0.1 and prior to version 1.3.0, in some cases, myhoard logs the whole backup info, including the encryption key. Version 1.3.0 fixes the issue. As a workaround, direct logs into /dev/null.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-67745?
CVE-2025-67745 is classified as a medium-severity vulnerability due to the potential exposure of sensitive encryption keys in logs.
How do I fix CVE-2025-67745?
To fix CVE-2025-67745, upgrade to MyHoard version 1.3.0 or later, or redirect logs to /dev/null as a temporary workaround.
What versions of MyHoard are affected by CVE-2025-67745?
CVE-2025-67745 affects MyHoard versions from 1.0.1 up to, but not including, version 1.3.0.
What information is logged that is related to CVE-2025-67745?
CVE-2025-67745 can lead to logs containing sensitive backup information, including encryption keys.
Is there a workaround for CVE-2025-67745?
Yes, as a workaround for CVE-2025-67745, you can redirect the logs to /dev/null.