VulnerabilityPublished 25 Feb 2024Updated 5 Aug 2024

CVE-2024-27359: Infinite Loop

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% 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:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within 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 25 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Organizations should monitor WithSecure’s official channels for patches addressing CVE-2024-27359 and apply them promptly once available. Until patches are released, consider implementing the following mitigations: 1) Restrict or monitor the types of archive files submitted for scanning, especially from untrusted sources, to reduce exposure to malicious archives. 2) Deploy network-level protections such as intrusion detection/prevention systems (IDS/IPS) to detect and block suspicious archive file transfers. 3) Isolate or sandbox scanning processes where possible to limit the impact of potential infinite loops on critical systems. 4) Implement resource usage monitoring and automated process restarts to quickly recover from potential hangs caused by the vulnerability. 5) Review and tighten access controls to WithSecure management interfaces to prevent unauthorized triggering of scans. 6) Conduct internal testing with crafted archive files to understand the vulnerability’s behavior and validate mitigation effectiveness. These targeted steps go beyond generic advice by focusing on limiting exposure to malicious archives and minimizing operational impact until official fixes are deployed.

Description

Certain WithSecure products allow a Denial of Service because the engine scanner can go into an infinite loop when processing an archive file. This affects WithSecure Client Security 15, WithSecure Server Security 15, WithSecure Email and Server Security 15, WithSecure Elements Endpoint Protection 17 and later, WithSecure Client Security for Mac 15, WithSecure Elements Endpoint Protection for Mac 17 and later, WithSecure Linux Security 64 12.0, WithSecure Linux Protection 12.0, and WithSecure Atlant 1.0.35-1.

Impact

The primary impact of CVE-2024-27359 is denial of service, which can disrupt the availability of critical security products protecting endpoints, servers, email systems, and Linux environments. This disruption can leave organizations temporarily unprotected against other threats, increasing their risk exposure. Since the vulnerability can be triggered remotely without authentication or user interaction, attackers can easily exploit it to degrade or disable security defenses at scale. This could be leveraged as part of a larger attack campaign to create windows of opportunity for further compromise. Organizations with high reliance on WithSecure products, especially in sectors like finance, healthcare, government, and critical infrastructure, may face operational interruptions and potential regulatory compliance issues if security controls are disabled. The broad range of affected platforms and product lines increases the likelihood of widespread impact across diverse IT environments globally.

References

withsecure.com/en/support/security-advisories/cve-2034-n1 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 11:01 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats