What is the severity of CVE-2020-0872?

CVE-2020-0872 is classified as a critical vulnerability due to its potential for remote code execution.

How do I fix CVE-2020-0872?

To fix CVE-2020-0872, update Microsoft Application Inspector to version 1.0.24 or later.

What types of attacks can be executed through CVE-2020-0872?

CVE-2020-0872 allows attackers to execute arbitrary code remotely by reflecting malicious code snippets into HTML output.

Which versions of Application Inspector are affected by CVE-2020-0872?

Application Inspector version 1.0.23 and earlier are affected by CVE-2020-0872.

How can I determine if my system is vulnerable to CVE-2020-0872?

Check if you are using Microsoft Application Inspector version 1.0.23 or earlier to determine vulnerability to CVE-2020-0872.

Vulnerability/
CVE-2020-0872

critical

9.6

CWE

12/3/2020

4/8/2024

CVE-2020-0872: XSS

First published: Thu Mar 12 2020(Updated: )

A remote code execution vulnerability exists in Application Inspector version v1.0.23 or earlier when the tool reflects example code snippets from third-party source files into its HTML output, aka 'Remote Code Execution Vulnerability in Application Inspector'.

Credit: secure@microsoft.com

Affected Software	Affected Version	How to fix
Microsoft Application Inspector	<=1.0.23

Remedy

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

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2020-0872?
CVE-2020-0872 is classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2020-0872?
To fix CVE-2020-0872, update Microsoft Application Inspector to version 1.0.24 or later.
What types of attacks can be executed through CVE-2020-0872?
CVE-2020-0872 allows attackers to execute arbitrary code remotely by reflecting malicious code snippets into HTML output.
Which versions of Application Inspector are affected by CVE-2020-0872?
Application Inspector version 1.0.23 and earlier are affected by CVE-2020-0872.
How can I determine if my system is vulnerable to CVE-2020-0872?
Check if you are using Microsoft Application Inspector version 1.0.23 or earlier to determine vulnerability to CVE-2020-0872.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/weakness
agent/references
agent/remedy
agent/last-modified-date
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/microsoft
canonical/microsoft application inspector
version/microsoft application inspector/1.0.23

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-0872?
CVE-2020-0872 is classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2020-0872?
To fix CVE-2020-0872, update Microsoft Application Inspector to version 1.0.24 or later.
What types of attacks can be executed through CVE-2020-0872?
CVE-2020-0872 allows attackers to execute arbitrary code remotely by reflecting malicious code snippets into HTML output.
Which versions of Application Inspector are affected by CVE-2020-0872?
Application Inspector version 1.0.23 and earlier are affected by CVE-2020-0872.
How can I determine if my system is vulnerable to CVE-2020-0872?
Check if you are using Microsoft Application Inspector version 1.0.23 or earlier to determine vulnerability to CVE-2020-0872.