CVE-2020-0872

9.6 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to execute arbitrary code on systems running vulnerable versions of Microsoft Application Inspector. Attackers can exploit this by crafting malicious source files that, when analyzed by Application Inspector, inject code into the HTML output. Anyone using Application Inspector v1.0.23 or earlier to analyze untrusted source code is affected.

💻 Affected Systems

Products:
  • Microsoft Application Inspector
Versions: v1.0.23 and earlier
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of affected versions are vulnerable when analyzing source files from untrusted sources.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with attacker gaining full control over the Application Inspector host, potentially leading to lateral movement within the network.

🟠

Likely Case

Remote code execution on the Application Inspector server, allowing attackers to steal data, install malware, or pivot to other systems.

🟢

If Mitigated

Limited impact if Application Inspector is isolated in a sandboxed environment with no network access to sensitive systems.

🌐 Internet-Facing: HIGH if Application Inspector is exposed to the internet, as exploitation requires no authentication.
🏢 Internal Only: HIGH even internally, as any user who can submit source files for analysis could potentially exploit this vulnerability.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability is a classic cross-site scripting (XSS) that leads to remote code execution, making exploitation straightforward for attackers with basic web security knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: v1.0.24 and later

Vendor Advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0872

Restart Required: No

Instructions:

1. Download the latest version of Application Inspector from the official Microsoft repository. 2. Uninstall the vulnerable version. 3. Install the patched version. 4. Verify the installation is complete and functioning.

🔧 Temporary Workarounds

Disable Application Inspector

all

Temporarily disable Application Inspector until patching can be completed.

Stop the Application Inspector service or process

Restrict Source File Analysis

all

Only analyze source files from trusted, verified sources.

🧯 If You Can't Patch

  • Isolate Application Inspector in a network segment with no access to sensitive systems
  • Implement strict input validation and sanitization for all source files before analysis

🔍 How to Verify

Check if Vulnerable:

Check the Application Inspector version. If it's v1.0.23 or earlier, it's vulnerable.

Check Version:

applicationinspector --version

Verify Fix Applied:

Verify the installed version is v1.0.24 or later and test with known safe source files.

📡 Detection & Monitoring

Log Indicators:

  • Unusual process creation from Application Inspector
  • Suspicious network connections originating from Application Inspector host

Network Indicators:

  • Unexpected outbound connections from Application Inspector server
  • Traffic patterns indicating command and control activity

SIEM Query:

source="ApplicationInspector" AND (event_type="process_creation" OR event_type="network_connection")

🔗 References

📤 Share & Export