CVE-2017-20190
Microsoft Windows Unicode Combining Characters Processing Vulnerability
Description
Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side performance degradation during processing of multiple Unicode combining characters, aka a "Zalgo text" attack. NOTE: third parties dispute whether the computational cost of interpreting Unicode data should be considered a vulnerability.
INFO
Published Date :
March 27, 2024, 12:15 a.m.
Last Modified :
Nov. 21, 2024, 3:22 a.m.
Source :
[email protected]
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2017-20190.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2017-20190 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2017-20190 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://aka.ms/windowsbugbar Added Reference https://en.wikipedia.org/wiki/Zalgo_text Added Reference https://talk.dynalist.io/t/dynalist-is-vulnerable-to-zalgo/1234 -
CVE Modified by [email protected]
Aug. 12, 2024
Action Type Old Value New Value -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 08, 2024
Action Type Old Value New Value Added CWE CISA-ADP CWE-176 -
CVE Modified by [email protected]
Aug. 05, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
May. 17, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Apr. 11, 2024
Action Type Old Value New Value -
CVE Received by [email protected]
Mar. 27, 2024
Action Type Old Value New Value Added Description Some Microsoft technologies as used in Windows 8 through 11 allow a temporary client-side performance degradation during processing of multiple Unicode combining characters, aka a "Zalgo text" attack. NOTE: third parties dispute whether the computational cost of interpreting Unicode data should be considered a vulnerability. Added Reference MITRE https://talk.dynalist.io/t/dynalist-is-vulnerable-to-zalgo/1234 [No types assigned] Added Reference MITRE https://en.wikipedia.org/wiki/Zalgo_text [No types assigned] Added Reference MITRE https://aka.ms/windowsbugbar [No types assigned] Added Tag MITRE disputed
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2017-20190 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2017-20190
weaknesses.