CVE-2024-27358VulnerabilityPublished 26 Jul 2024Updated 1 Nov 2024

CVE-2024-27358: n/a

Source CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.3Low

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jul 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-25.

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-27358, organizations should implement strict local user account controls on macOS systems running WithSecure Elements Agent or Client Security. Limit local user privileges to the minimum necessary, preventing non-administrative users from interfering with installation processes. Employ endpoint management solutions to monitor installation attempts and detect abnormal blocking behavior. Administrators should perform installations and updates in controlled environments or during maintenance windows to reduce interference risk. Until an official patch is released, consider isolating critical systems from untrusted local users and auditing local account activities. Engage WithSecure support for any available patches or recommended workarounds. Additionally, maintain comprehensive logging to identify potential exploitation attempts and ensure rapid response capabilities. Regularly review and update security policies to address local privilege misuse scenarios.

Description

An issue was discovered in WithSecure Elements Agent through 23.x for macOS and WithSecure Elements Client Security through 23.x for macOS. Local users can block an admin from completing an installation, aka a Denial-of-Service (DoS).

Impact

The primary impact of CVE-2024-27358 is a denial-of-service condition that disrupts the installation or update of WithSecure security software on macOS endpoints. For organizations relying on these products for endpoint protection, this could delay deployment of critical security updates or new installations, increasing the window of exposure to other vulnerabilities or malware. Although the vulnerability does not allow privilege escalation or data compromise, the inability to complete installations could hinder security posture and operational continuity. In environments with multiple users sharing machines or where local user accounts are common, the risk of exploitation increases. However, the requirement for local access and limited privileges reduces the likelihood of widespread exploitation. The absence of known exploits in the wild further lowers immediate risk but does not eliminate potential future threats. Overall, the impact is moderate operational disruption rather than direct data loss or system compromise.

References

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

Community reviews

Loading reviews…