6 matches found
CVE-2025-54870
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 thi...
CVE-2025-54870
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 thi...
CVE-2025-54870
VTun-ng (virtual tunnel over TCP/IP) contains a vulnerability in versions 3.0.17 and earlier where failure to initialize encryption modules can cause a fallback to plaintext due to insufficient error handling. The issue was introduced in 3.0.12 and fixed in 3.0.18. Remediation: upgrade to 3.0.18 ...
CVE-2025-54870 VTun-ng's failure to initialize encryption modules may cause reversion to plaintext
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 thi...
CVE-2025-54870 VTun-ng's failure to initialize encryption modules may cause reversion to plaintext
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 thi...
PT-2025-31889 · Vtun-Ng · Vtun-Ng
Name of the Vulnerable Software and Affected Versions: VTun-ng versions 3.0.17 and below Description: VTun-ng, a Virtual Tunnel over TCP/IP network, may revert to plaintext due to insufficient error handling when initializing encryption modules. The issue was introduced in version 3.0.12 and is...