CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighResearch in progress

CVE-2020-0878 remediation guide

Microsoft Edge and Internet Explorer

<p>A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory. The vulnerability could corrupt memory in a way that could allow an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, the attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.</...

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductMicrosoft Edge and Internet Explorer
Affected versions1.0..0, 1.0.0, 11, 9
Fixed versionsNo verified fixed-version field is available yet
Priority basisImmediate · CVSS 7.5 · EPSS 2.70%
01

Identify the affected asset

Confirm whether Microsoft Edge and Internet Explorer is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 1.0..0, 1.0.0, 11, 9. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2020-0878 Remediation Guide | SECUFOCUS NOW