What is the severity of CVE-2020-1455?

CVE-2020-1455 is classified as a denial of service vulnerability in Microsoft SQL Server Management Studio.

How do I fix CVE-2020-1455?

To mitigate CVE-2020-1455, update Microsoft SQL Server Management Studio to version 18.6 or later.

Which versions of SQL Server Management Studio are affected by CVE-2020-1455?

CVE-2020-1455 affects all versions of Microsoft SQL Server Management Studio up to version 18.6.

What are the potential impacts of CVE-2020-1455?

The potential impact of CVE-2020-1455 is a denial of service that can disrupt services within Microsoft SQL Server Management Studio.

Is there a workaround for CVE-2020-1455?

There are no official workarounds for CVE-2020-1455; the best course of action is to upgrade to a fixed version.

Vulnerability/
CVE-2020-1455

medium

5.5

17/8/2020

4/8/2024

CVE-2020-1455: Microsoft SQL Server Management Studio Denial of Service Vulnerability

First published: Mon Aug 17 2020(Updated: )

A denial of service vulnerability exists when Microsoft SQL Server Management Studio (SSMS) improperly handles files, aka 'Microsoft SQL Server Management Studio Denial of Service Vulnerability'.

Credit: secure@microsoft.com secure@microsoft.com

Affected Software	Affected Version	How to fix
	<18.6
Microsoft SQL Server Management Studio	<18.6

Remedy

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

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2020-1455?
CVE-2020-1455 is classified as a denial of service vulnerability in Microsoft SQL Server Management Studio.
How do I fix CVE-2020-1455?
To mitigate CVE-2020-1455, update Microsoft SQL Server Management Studio to version 18.6 or later.
Which versions of SQL Server Management Studio are affected by CVE-2020-1455?
CVE-2020-1455 affects all versions of Microsoft SQL Server Management Studio up to version 18.6.
What are the potential impacts of CVE-2020-1455?
The potential impact of CVE-2020-1455 is a denial of service that can disrupt services within Microsoft SQL Server Management Studio.
Is there a workaround for CVE-2020-1455?
There are no official workarounds for CVE-2020-1455; the best course of action is to upgrade to a fixed version.

collector/nvd-index
agent/type
agent/first-publish-date
agent/author
agent/softwarecombine
agent/remedy
agent/references
agent/title
agent/event
agent/severity
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
vendor/microsoft
canonical/microsoft sql server management studio

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-1455?
CVE-2020-1455 is classified as a denial of service vulnerability in Microsoft SQL Server Management Studio.
How do I fix CVE-2020-1455?
To mitigate CVE-2020-1455, update Microsoft SQL Server Management Studio to version 18.6 or later.
Which versions of SQL Server Management Studio are affected by CVE-2020-1455?
CVE-2020-1455 affects all versions of Microsoft SQL Server Management Studio up to version 18.6.
What are the potential impacts of CVE-2020-1455?
The potential impact of CVE-2020-1455 is a denial of service that can disrupt services within Microsoft SQL Server Management Studio.
Is there a workaround for CVE-2020-1455?
There are no official workarounds for CVE-2020-1455; the best course of action is to upgrade to a fixed version.