External risk intelligence

MicroWorld eScan AV Insecure Update Mechanism Allows Malicious Payload Substitution

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2024-13990

The vulnerability affects an endpoint antivirus client's update mechanism. While it relies on network communication to fetch updates, this process is typically an internal client-initiated action rather than a public-facing service. Man-in-the-middle attacks require a specific, often localized network position to intercept traffic, making general public internet exposure uncommon for this type of component.

Remote Code Execution

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns an issue with the update process for MicroWorld eScan antivirus software. A vulnerability existed where update packages were not properly verified, allowing an attacker on the network to substitute malicious updates for legitimate ones. This could lead to remote code execution on affected systems.

  • Antivirus updates were not securely verified.
  • Critical to confirm if our systems use this antivirus.
  • Leadership must ensure core software integrity.

Attack Path

How an attacker could exploit the issue

An attacker positioned to intercept network traffic can exploit this vulnerability by substituting malicious files for legitimate software updates. This attack targets the eScan AV client's update process, which does not adequately verify the authenticity of incoming data. If successful, the attacker can execute arbitrary code on the user's system.

  • Requires network interception.
  • Malicious update packages are accepted.
  • Allows remote code execution.

Live Threat

Current exploitation, exposure, and threat context

An on-path attacker could substitute malicious files for legitimate updates to the antivirus software. This could lead to remote code execution when the antivirus client accepts and processes these altered files, potentially including sideloaded components.

  • Antivirus client software components.
  • Man-in-the-middle attack on update delivery.
  • Remote code execution on affected systems.

Operational Fix

Recommended remediation, mitigation, and detection steps

The security teams or IT infrastructure owners managing MicroWorld eScan AV deployments are responsible for addressing this vulnerability. The initial step involves inventorying all eScan installations, determining their network reachability and criticality, and identifying the accountable system owners. Planning for remediation should then be based on a risk assessment, considering the vendor's statement about past remediation.

  • Identify eScan AV installations and owners.
  • Verify update process reachability and risk.
  • Plan remediation based on risk assessment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is MicroWorld eScan AV?

MicroWorld eScan AV is an endpoint security suite designed to protect computers and servers from malicious threats. It functions by monitoring system activity and regularly downloading software updates from the vendor's servers to maintain current protection against new threats. These updates are intended to refresh the client’s internal detection engines and core components.

How does CVE-2024-13990 affect software updates?

This vulnerability involves a failure in cryptographic verification during the update process, categorized as Improper Certificate Validation (CWE-295) and Improper Verification of Cryptographic Signature (CWE-347). Because the software did not properly check the identity or integrity of incoming packages, it could inadvertently accept and execute malicious files masquerading as legitimate software updates.

What must happen for this vulnerability to be triggered?

An attacker must be positioned as a 'man-in-the-middle' on the local network path between the client and the update server to intercept and replace traffic. Simply visiting a malicious website or opening a file does not trigger the bug; the attacker needs to actively manipulate the specific network stream used by the eScan update mechanism to inject their payload during an update cycle.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal labels this as unlikely for general public-facing exposure. Because this vulnerability targets an internal, client-initiated update process, it requires an attacker to have a specific, localized network position to intercept traffic. It is generally not considered a public-facing service directly accessible to anonymous internet users.

What are the first steps to address this issue?

Begin by auditing your environment to identify all systems where MicroWorld eScan AV is installed. Once you have an inventory of these devices, verify that your software is running the latest versions provided by the vendor. Consult the vendor's guidance regarding updates implemented in previous years to ensure your current deployment has moved beyond the vulnerable configuration.

References