| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in leakingmemory vtun-ng up to 3.0.17. This issue affects some unknown processing. This manipulation causes failing open. This vulnerability is handled as CVE-2025-54870. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in leakingmemory vtun-ng up to 3.0.17. It has been declared as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a failing open vulnerability. The CWE definition for the vulnerability is CWE-636. When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. As an impact it is known to affect confidentiality. The summary by CVE is:
VTun-ng is a Virtual Tunnel over TCP/IP network. In versions 3.0.17 and below, failure to initialize encryption modules might cause reversion to plaintext due to insufficient error handling. The bug was first introduced in VTun-ng version 3.0.12. This is fixed in version 3.0.18. To workaround this issue, avoid blowfish-256.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-54870 since 07/31/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.0.18 eliminates this vulnerability. Applying the patch 8c63982b6c487c52db1d56ab94c266f0bc857140 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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-23579). Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Failing openCWE: CWE-636
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: vtun-ng 3.0.18
Patch: 8c63982b6c487c52db1d56ab94c266f0bc857140
Timeline
07/31/2025 CVE reserved08/05/2025 Advisory disclosed
08/05/2025 VulDB entry created
08/05/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-m3jc-27c6-2wrf
Status: Confirmed
CVE: CVE-2025-54870 (🔒)
GCVE (CVE): GCVE-0-2025-54870
GCVE (VulDB): GCVE-100-318751
EUVD: 🔒
Entry
Created: 08/05/2025 09:13Updated: 08/05/2025 18:47
Changes: 08/05/2025 09:13 (68), 08/05/2025 13:29 (1), 08/05/2025 18:47 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.