CVE-2024-24300VulnerabilityPublished 14 Feb 2024Updated 16 Aug 2024

CVE-2024-24300: n/a

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-24300, organizations should first verify if they are using the affected 4ipnet EAP-767 firmware version 3.42.00. Immediate steps include isolating affected devices from critical network segments and restricting administrative access to trusted IP addresses only. Network segmentation and strict firewall rules can limit exposure. Since no patches are currently available, consider deploying compensating controls such as enforcing strong network access controls, monitoring device logs for suspicious activity, and implementing multi-factor authentication (MFA) on management interfaces if supported. Regularly rotate any credentials associated with the device and invalidate all active sessions where possible. Engage with the vendor for updates or patches and plan for prompt firmware upgrades once available. Additionally, conduct thorough network scans to detect unauthorized access and prepare incident response plans tailored to this vulnerability.

Description

4ipnet EAP-767 v3.42.00 is vulnerable to Incorrect Access Control. The device uses the same set of credentials, regardless of how many times a user logs in, the content of the cookie remains unchanged.

Impact

The impact of CVE-2024-24300 is severe for organizations worldwide that utilize 4ipnet EAP-767 devices. Exploitation can lead to unauthorized access to network infrastructure, allowing attackers to manipulate device settings, intercept sensitive communications, or launch further attacks within the network. The compromise of confidentiality, integrity, and availability can result in data breaches, service disruptions, and loss of trust. Given that the vulnerability requires no privileges or user interaction, attackers can remotely exploit it with minimal effort, increasing the likelihood of widespread exploitation once public exploits emerge. Organizations in sectors such as telecommunications, enterprise IT, education, and government that rely on these devices for wireless connectivity are particularly vulnerable. The inability to rotate or invalidate session credentials also complicates incident response and recovery efforts, potentially prolonging attacker persistence.

Summary

CVE-2024-24300 is a critical security vulnerability identified in the 4ipnet EAP-767 wireless access point firmware version 3.42.00. The vulnerability arises from incorrect access control mechanisms where the device uses a static set of credentials and an unchanging session cookie for user authentication. This means that once an attacker obtains or guesses the credentials or session cookie, they can reuse it indefinitely without the system invalidating or rotating these tokens upon new logins or sessions. The flaw violates proper session management and access control principles (CWE-284), enabling unauthorized users to gain persistent access to the device without requiring privileges or user interaction. The CVSS v3.1 base score of 9.8 reflects the vulnerability’s ease of remote exploitation (network vector), lack of required privileges or user interaction, and its impact on confidentiality, integrity, and availability. Although no public exploits have been reported, the vulnerability presents a significant risk to network security, as attackers could manipulate device configurations, intercept or redirect network traffic, or disrupt network services. The absence of available patches at the time of disclosure necessitates immediate mitigation efforts. This vulnerability primarily affects organizations deploying 4ipnet EAP-767 devices, which are commonly used in enterprise and service provider wireless networks.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/yckuo-sdc/PoC (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:22 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats