Endpoint Security

Security Firm Discloses CrowdStrike Issue After ‘Ridiculous Disclosure Process’

A security firm has disclosed the details of an issue affecting a CrowdStrike product after what it described as a ‘ridiculous vulnerability disclosure process’. CrowdStrike has provided some clarifications following the disclosure.

<p><strong><span><span>A security firm has disclosed the details of an issue affecting a CrowdStrike product after what it described as a ‘ridiculous vulnerability disclosure process’. CrowdStrike has provided some clarifications following the disclosure.</span></span></strong></p>

A security firm has disclosed the details of an issue affecting a CrowdStrike product after what it described as a ‘ridiculous vulnerability disclosure process’. CrowdStrike has provided some clarifications following the disclosure.

Researchers at Swiss security firm Modzero discovered an issue related to CrowdStrike’s Falcon endpoint detection and response product. Specifically, the problem is related to the Falcon Sensor, a lightweight agent deployed on each end device. The sensor can be configured with uninstall protection, which prevents its removal without a special token.

Modzero discovered that an attacker with admin privileges can bypass the token check on Windows devices and uninstall the sensor in an effort to remove the protection provided by CrowdStrike’s product.

The firm admitted that ‘the overall risk of the vulnerability is very limited’ due to the fact that elevated privileges are required for exploitation, but it wanted to publish a blog post — in addition to a technical advisory describing the issue — to complain about the disclosure process.

Modzero did not want to report its findings through CrowdStrike’s HackerOne-based bug bounty program and the disclosure process did not go smoothly.

In early June, Modzero started asking CrowdStrike about an alternative way to report its findings, one that did not involve HackerOne or signing a non-disclosure agreement.

Modzero ultimately sent its findings via email in late June, but CrowdStrike initially could not reproduce the issue and later said it did not appear to be a valid vulnerability.

Modzero later tested its findings on a more recent version of CrowdStrike Falcon and noticed that the vendor had actually taken some steps to prevent exploitation, including by flagging Modzero’s proof-of-concept (PoC) exploit as malicious.

Advertisement. Scroll to continue reading.

Modzero said it managed to bypass CrowdStrike’s countermeasures and decided to make its findings public.

In a response posted on Reddit after Modzero’s blog post and technical advisory were published on Monday, CrowdStrike provided clarifications about the vulnerability, but did not address the issues related to the disclosure process itself, although it did thank Modzero for its ‘hard work and disclosure of this incident’.

CrowdStrike said it informed customers about the bug through a Tech Alert issued on July 8, which it updated on August 22 with additional details. The Tech Alert credits Modzero for its findings.

According to the endpoint security firm, exploitation requires “specialized software, local administrator access, privilege elevation, and a reboot of the endpoint”.

CrowdStrike said the issue is related to the Microsoft installer and it sent a bug report to the tech giant on August 12. CrowdStrike has shared a description of the flaw from its own perspective:

“Falcon is installed and uninstalled on Windows systems using the Microsoft Installer (MSI) harness. To perform secondary actions during an installation or uninstallation — such as performing system checks or, in this instance, verifying an uninstall token — Microsoft recommends using Custom Actions (CA) via msiexec.exe.

 

During an uninstallation of Falcon, several instances of msiexec.exe run in parallel performing various tasks. One of these tasks uses a custom action (CA) to verify the presence of a valid uninstall token for Falcon. Under normal conditions, if that verification fails or can’t be completed, the MSI logic stops the uninstallation process and notifies the user that a valid uninstall token is required.

 

As disclosed by modzero, a local administrator can circumvent this within Microsoft’s MSI implementation, wherein msiexec.exe will continue an uninstall process if a CA terminates without returning (such as when that process crashes or is intentionally killed). In essence, the MSI is failing open (unexpected) as opposed to failing closed (expected).”

The vulnerability has been assigned the CVE identifier CVE-2022-2841, but CrowdStrike said the CVE is still under analysis.

Related: High-Severity Vulnerabilities Patched in McAfee Enterprise Product

Related: Trend Micro Patches Vulnerabilities in Hybrid Cloud Security Products

Related Content

Copyright © 2024 SecurityWeek ®, a Wired Business Media Publication. All Rights Reserved.

Exit mobile version