CVE-2024-45944VulnerabilityPublished 18 Oct 2024Updated 21 Oct 2024

CVE-2024-45944: J2EEFAST · n/a

Affects J2EEFASTSource 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.8% chance of exploitation in 30 days – higher than 58% 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 18 Oct 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

Affected software

Product	Affected	Fixed in
GitHubdromara/J2EEFAST`pkg:github/dromara/J2EEFAST`Other threats	Affected <=2.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately identify and inventory all systems running J2eeFAST version 2.7 or earlier. Until official patches are released, apply the following mitigations: 1) Restrict network access to backend functions by implementing firewall rules and network segmentation to limit exposure to trusted hosts only. 2) Implement strict input validation and sanitization on all inputs processed by the backend functions to prevent injection of malicious payloads. 3) Monitor logs and backend function calls for unusual or unauthorized activity indicative of exploitation attempts. 4) Employ application-layer firewalls or runtime application self-protection (RASP) solutions to detect and block suspicious behavior. 5) Prepare for rapid patch deployment once vendor updates become available. 6) Conduct security awareness and incident response readiness exercises focused on this vulnerability. 7) Consider temporary disabling or isolating vulnerable backend functions if feasible without disrupting critical operations. These targeted steps go beyond generic advice by focusing on access control, input validation, and proactive monitoring specific to the vulnerability's exploitation vector.

Description

In J2eeFAST <=2.7, the backend function has unsafe filtering, which allows an attacker to trigger certain sensitive functions resulting in arbitrary code execution.

Impact

The impact of CVE-2024-45944 is severe for organizations worldwide using J2eeFAST in their enterprise Java applications. Successful exploitation results in arbitrary code execution, allowing attackers to fully compromise affected systems. This can lead to data breaches, system manipulation, service disruption, and potential lateral movement within networks. The vulnerability affects confidentiality by exposing sensitive data, integrity by allowing unauthorized code execution and modification, and availability by enabling denial-of-service or destruction of resources. Given the remote, unauthenticated nature of the exploit, attackers can target vulnerable systems at scale, increasing the risk of widespread attacks. Enterprises relying on J2eeFAST for critical business functions face operational and reputational damage if exploited. The absence of known exploits currently provides a window for proactive defense, but the critical severity demands immediate attention to prevent future attacks.

References

Community reviews

Loading reviews…