NVD / CVE Program· CNA cisa-cg

CVE-2024-3661: DHCP routing options can manipulate interface-based VPN traffic

Noroxi assessment

Priority: Monitor (action score 31/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 4% (FIRST EPSS); higher than 90.7% of all records.
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: NetworkManager (AlmaLinux:8) 1:1.40.16-18.el8_10; NetworkManager-adsl (AlmaLinux:8) 1:1.40.16-18.el8_10; NetworkManager-bluetooth (AlmaLinux:8) 1:1.40.16-18.el8_10.

Low priority for now. Upgrade to NetworkManager (AlmaLinux:8) 1:1.40.16-18.el8_10; NetworkManager-adsl (AlmaLinux:8) 1:1.40.16-18.el8_10; NetworkManager-bluetooth (AlmaLinux:8) 1:1.40.16-18.el8_10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.6 · v3.1—Proof of concept Fix available

Published: May 6, 2024
Updated: Jun 17, 2026
EPSS: 4.0% · 90th percentile
CWE: CWE-306

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 4.0%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.6
CNA · cisa-cg: 7.6; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
fortinet	forticlient	cpe:2.3:a:fortinet:forticlient
cisco	anyconnect vpn client	cpe:2.3:a:cisco:anyconnect_vpn_client
cisco	secure client	cpe:2.3:a:cisco:secure_client
paloaltonetworks	globalprotect	cpe:2.3:a:paloaltonetworks:globalprotect
citrix	secure access client	cpe:2.3:a:citrix:secure_access_client
apple	iphone os	cpe:2.3:o:apple:iphone_os
apple	macos	cpe:2.3:o:apple:macos
linux	linux kernel	cpe:2.3:o:linux:linux_kernel
f5	big-ip access policy manager	cpe:2.3:a:f5:big-ip_access_policy_manager
watchguard	ipsec mobile vpn client	cpe:2.3:a:watchguard:ipsec_mobile_vpn_client
watchguard	mobile vpn with ssl	cpe:2.3:a:watchguard:mobile_vpn_with_ssl
zscaler	client connector	cpe:2.3:a:zscaler:client_connector

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

cisco secure clientall versions
paloaltonetworks globalprotectall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (cisa-cg). Independent of NVD's CPE analysis and usually ahead of it.

IETF DHCP
- 0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	NetworkManager	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-adsl	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-bluetooth	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-cloud-setup	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-config-connectivity-redhat	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-config-server	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-dispatcher-routing-rules	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-initscripts-updown	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-libnm	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-libnm-devel	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-ovs	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-ppp	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-team	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-tui	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-wifi	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:8	NetworkManager-wwan	before 1:1.40.16-18.el8_10	1:1.40.16-18.el8_10
AlmaLinux:9	NetworkManager	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-adsl	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-bluetooth	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-cloud-setup	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-config-connectivity-redhat	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-config-server	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-dispatcher-routing-rules	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5
AlmaLinux:9	NetworkManager-initscripts-updown	before 1:1.48.10-5.el9_5	1:1.48.10-5.el9_5

+94

Same product

fortinet: all records

Other highest-scoring records for the same primary product.

CVE-2019-17658An unquoted service path vulnerability in the FortiClient FortiTray component of FortiClientWindows v6.2.2 and prior allow an attacker to ga
40Plan
CVE-2017-14184An Information Disclosure vulnerability in Fortinet FortiClient for Windows 5.6.0 and below versions, FortiClient for Mac OSX 5.6.0 and belo
36Monitor
CVE-2016-8493In FortiClientWindows 5.4.1 and 5.4.2, an attacker may escalate privilege via a FortiClientNamedPipe vulnerability.
36Monitor

Published before and after this one in the same product

← EarlierCVE-2023-45590Apr 9, 2024 · An improper control of generation of code ('code injection') in Fortinet FortiClientLinux version 7.2.0, 7.0.6 through 7.0.10 and 7.0.3 thro
35Monitor
← EarlierCVE-2024-31492Apr 10, 2024 · An external control of file name or path vulnerability [CWE-73] in FortiClientMac version 7.2.3 and below, version 7.0.10 and below install
31Monitor
Later →CVE-2022-45856Sep 10, 2024 · An improper certificate validation vulnerability [CWE-295] in FortiClientWindows 6.4 all versions, 7.0.0 through 7.0.7, FortiClientMac 6.4 a
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
almalinux:NetworkManager	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-adsl	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-bluetooth	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-cloud-setup	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-config-connectivity-redhat	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-config-server	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-dispatcher-routing-rules	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-initscripts-updown	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-libnm	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-libnm-devel	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-ovs	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
almalinux:NetworkManager-ppp	1:1.40.16-18.el8_10 · AlmaLinux:8	Package registry (OSV)
red hat:NetworkManager-adsl-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-bluetooth-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-cloud-setup	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-cloud-setup-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-debugsource	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-libnm-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-ovs-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-ppp-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-team-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-tui-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:NetworkManager-wifi-debuginfo	1:1.40.16-18.el8_10 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
rocky linux:NetworkManager	1:1.40.16-18.el8_10 · Rocky Linux:8	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2025-05-16
Proof-of-concept repository on GitHub	stars:0	2025-05-23
Proof-of-concept repository on GitHub	stars:0	2025-11-27

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMay 6, 2024
First PoCMay 16, 2025+374 d
TodayNov 7, 2026+915 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2024-3149226 days apartAn external control of file name or path vulnerability [CWE-73] in FortiClientMac version 7.2.3 and below, version 7.0.10 and below install
31Monitor

Bug bounty scope

Cloud Software GroupHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: low · data or configuration can be modified
Availability: low · the service can be disrupted

Attack vector: Adjacent
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: Low
Availability impact: Low

Weakness class (CWE)

CWE-306 · Missing Authentication for Critical Function

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

nvd-primary

Root cause

A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”

The bug in code

The whole CWE-306 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1// Added for the support team
2app.post("/maintenance/reset", resetDevice);

Fixed

1if (config.maintenanceEnabled) {
2  app.post(
3    "/maintenance/reset",
4    requireSession, requireRole("admin"), resetDevice
5  );
6}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

bst.cisco.com/quickview/bug/CSCwk05814

Show all references (14 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records