cve.bz

CVE-2024-3661 (TunnelVision) Trust Boundary Violation

7.6 highExploit referenceEPSS 4.1%

Known as TunnelVision

High (7.6). EPSS 4.1% estimated probability of exploitation activity in the next 30 days.

On this page
DHCP can add routes to a client’s routing table via the classless static route option (121). VPN-based security solutions that rely on routes to redirect traffic can be forced to leak traffic over the physical interface. An attacker on the same local network can read, disrupt, or possibly modify network traffic that was expected to be protected by the VPN.

Severity

CVSS 3.1

7.6 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
EPSS
4.1% (unchanged from 4.1% a week ago; 4.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-05-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-306 Missing Authentication for Critical Functionality
CWE-501 Trust Boundary Violation
OWASP Top 10
A06:2025 Insecure Design, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-3661 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-3661?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-3661?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-3661 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
fortinet:forticlientfrom 6.4.0 before 7.2.5
fortinet:forticlient7.4.0
citrix:secure_access_clientbefore 24.06.1
citrix:secure_access_clientbefore 24.8.5
f5:big-ip_access_policy_managerfrom 7.2.3 through 7.2.5
f5:big-ip_access_policy_managerfrom 15.1.0 through 15.1.10
f5:big-ip_access_policy_managerfrom 16.1.0 through 16.1.5
f5:big-ip_access_policy_managerfrom 17.1.0 through 17.1.2
zscaler:client_connectorbefore 1.5.1.25
zscaler:client_connectorbefore 4.2.0.282
zscaler:client_connectorfrom 3.7 before 3.7.0.134

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTSpptpdno fix listedUBUNTU-CVE-2024-3661
Ubuntu16.04:LTSn2n, tinc, vpnc and 13 moreno fix listedUBUNTU-CVE-2024-3661
Ubuntu18.04:LTSn2n, tinc, vpnc and 18 moreno fix listedUBUNTU-CVE-2024-3661
Ubuntu20.04:LTSn2n, tinc, vpnc and 20 moreno fix listedUBUNTU-CVE-2024-3661
Ubuntu22.04:LTSn2n, tinc, vpnc and 22 moreno fix listedUBUNTU-CVE-2024-3661
Ubuntu24.04:LTSn2n, tinc, vpnc and 21 moreno fix listedUBUNTU-CVE-2024-3661
UbuntuPro:14.04:LTSopenvpnno fix listedUBUNTU-CVE-2024-3661
UbuntuPro:16.04:LTS, Pro:18.04:LTSconnman, openvpn, openconnectno fix listedUBUNTU-CVE-2024-3661
UbuntuPro:20.04:LTSopenconnectno fix listedUBUNTU-CVE-2024-3661
Red Hatenterprise_linux:8::appstreamNetworkManager-debuginfo, NetworkManager-cloud-setup, NetworkManager-debugsource and 10 more1:1.40.16-18.el8_10RHSA-2025:0288
Red Hatenterprise_linux:8::baseosNetworkManager, NetworkManager-ovs, NetworkManager-ppp and 23 more1:1.40.16-18.el8_10RHSA-2025:0288
Red Hatenterprise_linux:8::crbNetworkManager-debuginfo, NetworkManager-debugsource, NetworkManager-libnm-devel and 10 more1:1.40.16-18.el8_10RHSA-2025:0288
Red Hatenterprise_linux:9::appstreamNetworkManager-ovs, NetworkManager-ppp, NetworkManager-debuginfo and 14 more1:1.48.10-5.el9_5RHSA-2025:0377
Red Hatenterprise_linux:9::baseosNetworkManager, NetworkManager-tui, NetworkManager-adsl and 19 more1:1.48.10-5.el9_5RHSA-2025:0377
Red Hatenterprise_linux:9::crbNetworkManager-debuginfo, NetworkManager-debugsource, NetworkManager-libnm-devel and 10 more1:1.48.10-5.el9_5RHSA-2025:0377
Red Hatrhel_eus:9.4::appstreamNetworkManager-ovs, NetworkManager-ppp, NetworkManager-debuginfo and 14 more1:1.46.0-34.el9_4RHSA-2025:16411
Red Hatrhel_eus:9.4::baseosNetworkManager, NetworkManager-tui, NetworkManager-adsl and 19 more1:1.46.0-34.el9_4RHSA-2025:16411
Red Hatrhel_eus:9.4::crbNetworkManager-debuginfo, NetworkManager-debugsource, NetworkManager-libnm-devel and 10 more1:1.46.0-34.el9_4RHSA-2025:16411
AlmaLinux8NetworkManager, NetworkManager-ovs, NetworkManager-ppp and 13 more1:1.40.16-18.el8_10ALSA-2025:0288
AlmaLinux9NetworkManager, NetworkManager-ovs, NetworkManager-ppp and 13 more1:1.48.10-5.el9_5ALSA-2025:0377
Rocky Linux8NetworkManager1:1.40.16-18.el8_10RLSA-2025:0288
Rocky Linux9NetworkManager1:1.48.10-5.el9_5RLSA-2025:0377

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is also known as TunnelVision and it describes a technique to use DHCP configuration to manipulate hosts to send traffic to an attacker's host instead of through a VPN, as expected. According to MITRE it is reported as a vulnerability against DHCP. However, the DHCP protocol works as intended and as a protocol without cryptographic protection, attackers do not break a security boundary in the DHCP protocol by using the DHCP option 121. To prevent against the attack vector, users or VPN configuration software need to configure the VPN correctly or use other techniques to avoid that a DHCP configuration manipulates routing decisions for packets intended to be contained in the VPN.

This affects only situations where hosts use DHCP in a network and attackers can control a DHCP server. It affects full-tunnel and split-tunnel based VPNs. IPSec policy-based VPNs do not send unencrypted traffic to attackers as they encrypt traffic regardless of the routing decision.

Red Hat's mitigation

The mitigation steps also ensure that the applications using the VPN cannot access local resources outside the VPN in full-tunnel mode. If access to local resources outside the VPN is needed, additional routing configuration is necessary.

The following steps demonstrate how to configure VPN profiles with NetworkManager to prioritize VPN routes over DHCP routes. This uses routing rules with a higher priority than the rule to lookup the main routing table. This means that the VPN routing table is consulted prior to the main routing table. Please note that a higher priority is configured by setting a lower priority value in the routing configuration.

1. There were two bugs in NetworkManager that prevented these steps from working with profiles using VPN plugins, such as libreswan. Therefore first update NetworkManager:

- On RHEL 8.10, use NetworkManager-1.40.16-18.el8_10 or later.

- On RHEL 9.5 and later, use NetworkManager-1.48.10-5.el9_5 or later.

2. In the next steps, you will assign the VPN routes to a dedicated routing table. By default, RHEL does not use the routing tables 1-252, and you can use one of them. If you configured the system to use some of these tables, identify a free routing table number. The following example uses the routing table 75.

3. Optional: Configure a name for the routing table by adding a line, such as the following, to the /etc/iproute2/rt_tables file:

75 vpn

This makes the output of ip commands easier to understand. Note that NetworkManager only supports using a table ID and not the table name.

4. Configure the VPN connection profile to place the VPN routes in a dedicated routing table:

# nmcli connection modify <VPN_connection_profile> ipv4.route-table <routing_table_number>

For example:

# nmcli connection modify "Company VPN" ipv4.route-table 75

5. Set a low priority value for the table you used in the previous command:

# nmcli connection modify <VPN_connection_profile> ipv4.routing-rules "priority <low_priority_value> from all table <routing_table_number>"

The priority value can be any value between 1 and 32766 but, the lower the value, the higher the priority!

For example:

# nmcli connection modify "Company VPN" ipv4.routing-rules "priority 32345 from all table 75"

6. Reconnect the VPN:

# nmcli connection down <VPN_connection_profile>

# nmcli connection up <VPN_connection_profile>

This only prevents the TunnelVision techniques and possibly related issues regarding IPv4. For IPv6 it might be necessary to repeat the steps for IPv6.

If other software than NetworkManager is used to configure a VPN, it might need similar configuration changes to mitigate against TunnelVision.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8NetworkManager-1:1.40.16-18.el8_10Fixed 2025-01-13RHSA-2025:0288
Red Hat Enterprise Linux 9NetworkManager-1:1.48.10-5.el9_5Fixed 2025-01-16RHSA-2025:0377
Red Hat Enterprise Linux 9.4 Extended Update SupportNetworkManager-1:1.46.0-34.el9_4Fixed 2025-09-23RHSA-2025:16411
Red Hat Enterprise Linux 10dhcpcdNot affected
Red Hat Enterprise Linux 10NetworkManagerNot affected
Red Hat Enterprise Linux 6dhcpNot affected
Red Hat Enterprise Linux 6NetworkManagerWill not fix
Red Hat Enterprise Linux 7dhcpNot affected
Red Hat Enterprise Linux 7NetworkManagerWill not fix
Red Hat Enterprise Linux 8dhcpNot affected
Red Hat Enterprise Linux 9dhcpNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-3661.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON