# CVE-2024-3661: DHCP routing options can manipulate interface-based VPN traffic > Local attackers can manipulate DHCP routes to bypass VPN protections, exposing or modifying protected network traffic. - **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 May 2024 - **Updated:** 28 Aug 2024 - **Also known as:** ALSA-2025:0288, ALSA-2025:0377, CLSA-2025-1764322970, GHSA-jcv7-6v4q-4m7x, RHSA-2025:0288, RHSA-2025:0377, RHSA-2025:16411, RLSA-2025:0288, RLSA-2025:0377, UBUNTU-CVE-2024-3661 ## What is CVE-2024-3661? CVE-2024-3661 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 6 May 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-501 (Trust Boundary Violation), CWE-306 (Missing Authentication for Critical Functionality) ## Which versions are affected by CVE-2024-3661? It affects 9 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `NetworkManager` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-adsl` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-bluetooth` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-cloud-setup` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-config-connectivity-redhat` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-config-server` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-dispatcher-routing-rules` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-initscripts-updown` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-libnm` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-libnm-devel` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-ovs` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-ppp` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-team` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-tui` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-wifi` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-wwan` | AlmaLinux:8 | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-adsl` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-bluetooth` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-cloud-setup` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-config-connectivity-redhat` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-config-server` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-dispatcher-routing-rules` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-initscripts-updown` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-libnm` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-libnm-devel` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-ovs` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-ppp` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-team` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-tui` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-wifi` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-wwan` | AlmaLinux:9 | All versions | 1:1.48.10-5.el9_5 | | `NetworkManager-adsl-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-bluetooth-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-cloud-setup` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-cloud-setup-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-libnm-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | | `NetworkManager-ovs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.40.16-18.el8_10 | Products: Cisco Anyconnect Vpn Client, Cisco Secure Client, Citrix Secure Access Client, F5 Big-Ip Access Policy Manager, Fortinet Forticlient, Paloaltonetworks Globalprotect, Watchguard Ipsec Mobile Vpn Client, Watchguard Mobile Vpn With Ssl, Zscaler Client Connector. ## How do I fix CVE-2024-3661? Apply the vendor's patch. ## Is CVE-2024-3661 being exploited? There is no known exploitation of CVE-2024-3661 in the wild and no public exploit code. Public exploit code: - CVE-2024-3661 TunnelVision (github_poc): https://github.com/Wh1t3Fox/CVE-2024-3661 - https://github.com/Roundthe-clock/CVE-2024-3661VPN (github_poc): https://github.com/Roundthe-clock/CVE-2024-3661VPN - Demo TunnelVision vulnerability for VPN using DHCP option 121 (github_poc): https://github.com/YardenFadida/CVE-2024-3661_Demo ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3661 and fix it if it is affected. What it is: CVE-2024-3661 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 6 May 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-3661 in the wild and no public exploit code. Affected product: F5 Big-Ip Access Policy Manager. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-3661/ (Markdown: https://insights.sbomify.com/CVE-2024-3661/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3661 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3661 - OSV: https://osv.dev/vulnerability/CVE-2024-3661 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3661/ Summaries are generated and may contain mistakes; the official description above is the record.