Aiven-Open myhoard up to 1.2.x /dev/null transmission of private resources into a new sphere ('resource leak')
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Aiven-Open myhoard up to 1.2.x. It has been declared as critical. Affected by this issue is some unknown functionality of the file /dev/null. Such manipulation leads to transmission of private resources into a new sphere ('resource leak'). This vulnerability is listed as CVE-2025-67745. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Aiven-Open myhoard up to 1.2.x. Affected by this issue is some unknown processing of the file /dev/null. The manipulation with an unknown input leads to a transmission of private resources into a new sphere ('resource leak') vulnerability. Using CWE to declare the problem leads to CWE-402. The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-67745 since 12/11/2025. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available.
Upgrading to version 1.3.0 eliminates this vulnerability. Applying the patch fac89793bfc8c81ae040aadf5292f5d0100b6640 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 7.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Transmission of private resources into a new sphere ('resource leak')CWE: CWE-402
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: myhoard 1.3.0
Patch: fac89793bfc8c81ae040aadf5292f5d0100b6640
Timeline
12/11/2025 CVE reserved12/18/2025 Advisory disclosed
12/18/2025 VulDB entry created
03/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-v42r-6hr9-4hcr
Status: Confirmed
CVE: CVE-2025-67745 (🔒)
GCVE (CVE): GCVE-0-2025-67745
GCVE (VulDB): GCVE-100-337448
Entry
Created: 12/18/2025 22:23Updated: 03/05/2026 21:02
Changes: 12/18/2025 22:23 (66), 03/05/2026 21:02 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.