TrustTunnel has SSRF and private network restriction bypass via numeric address destinations
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| TrustTunnel | TrustTunnel | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Trusttunnel | Trusttunnel | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.267% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Adguard
Adguard trusttunnel |
|
| CPEs | cpe:2.3:a:adguard:trusttunnel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Adguard
Adguard trusttunnel |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Trusttunnel
Trusttunnel trusttunnel |
|
| Vendors & Products |
Trusttunnel
Trusttunnel trusttunnel |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | TrustTunnel is an open-source VPN protocol with a server-side request forgery and and private network restriction bypass in versions prior to 0.9.114. In `tcp_forwarder.rs`, SSRF protection for `allow_private_network_connections = false` was only applied in the `TcpDestination::HostName(peer)` path. The `TcpDestination::Address(peer) => peer` path proceeded to `TcpStream::connect()` without equivalent checks (for example `is_global_ip`, `is_loopback`), allowing loopback/private targets to be reached by supplying a numeric IP. The vulnerability is fixed in version 0.9.114. | |
| Title | TrustTunnel has SSRF and private network restriction bypass via numeric address destinations | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|