Saturday, November 7, 2026
HomeCyber SecuritySpeedy window title modifications trigger ‘white display of dying’

Speedy window title modifications trigger ‘white display of dying’

[ad_1]

ice

Experimentation with ANSI escape characters on terminal emulators has led to the invention of a number of high-severity DoS (denial of service) vulnerabilities on Home windows terminals and Chrome-based net browsers.

Eviatar Gerzi, a safety researcher at CyberArk, has tried out varied potential abuse pathways primarily based on an previous 2003 advisory on code execution through window title modifications and found a option to induce speedy window title modifications on PuTTY.

This atypical assault triggered the check machine to enter a state often called the “White Display of Demise”, the place every little thing freezes apart from the mouse cursor.

Upon testing the same assault on an area utility, the system entered WSOD instantly attributable to overburdening the OS kernel with calls.

Calls overwhelming the system kernel
Calls overwhelming the system kernel
Supply: CyberArk

The abused perform is ‘SetWindowText,’ which permits altering the textual content of the desired window’s title bar.

The one approach out of the WSOD state is to restart the pc, so this easy trick can result in a DoS state on a variety of purposes.

SetWindowText function in PuTTY
SetWindowText perform in PuTTY
Supply: CyberArk

As the researcher factors out, ‘SetWindowText’ isn’t the one attainable leverage for hung ups, as found within the case of MobaXterm.

In one of many circumstances, I examined the MobaXterm terminal, and I used to be shocked that it didn’t use SetWindowText perform to alter the window title however, moderately, a perform named GdipDrawString.

The attention-grabbing factor on this case is that it didn’t have an effect on the entire pc like SetWindowText. It affected solely the applying, which finally crashed.

Gerzi confirmed the next Home windows terminals are affected by DoS problem:

  • PuTTY – CVE-2021-33500 (freezes entire pc), mounted in model 0.75
  • MobaXterm – CVE-2021-28847 (freezes solely app), mounted in model 21.0 preview 3
  • MinTTY (and Cygwin) – CVE-2021-28848 (freezes entire pc), mounted in model 3.4.6
  • Git – makes use of MinTTY, mounted in model 2.30.1
  • ZOC – CVE-2021-32198 (freezes solely app), no repair
  • XSHELL – CVE-2021-42095 (freezes entire pc), mounted in model 7.0.0.76

Attempting it out on net browsers

Realizing that the majority GUI purposes use the SetWindowText perform, the researcher tried out the assault towards fashionable net browsers comparable to Chrome.

He created an HTML file that might trigger the title to alter quickly in an infinite loop, forcing the browser to freeze.

The identical habits was seen in Edge, Torch, Maxthon, Opera, and Vivaldi, all Chromium-based browsers. Although Firefox and Web Explorer are proof against it, they nonetheless take a efficiency hit.

Monitoring function calls on Edge
Monitoring perform calls on Edge
Supply: CyberArk

In all circumstances although, the underlying OS stays unaffected as a result of trendy browsers are primarily based on sandboxes.

Nonetheless, when attempting the browser assault inside a digital machine, a useful resource depletion problem occurred inflicting the virtualized system to show a ‘Blue Display of Demise.’

BSOD when testing DoS on a virtual machine
BSOD when testing DoS on a digital machine
Supply: CyberArk

Response from distributors

The researcher notes that the purposes affected by this assault may very well be something utilizing both SetWindowText or GdipDrawString, so the above apps are solely a pattern of the affected software program.

Some purposes like Slack, for instance, characteristic a charge limiter on the calls of the features, in order that they’re resilient to this sort of DoS assaults.

Slack's limiter stopping the attack after just three calls
Slack’s limiter stopping the assault after simply three calls
Supply: CyberArk

Gerzi contacted the affected distributors and acquired the next responses:

Google: DoS points are handled as abuse or stability points moderately than safety vulnerabilities. Word: Difficulty shouldn’t be noticed on Mac however is noticed on Linux. We’ve reviewed the difficulty once more. We weren’t capable of reproduce the crash within the newest variations of WS 16.1.2 build-17966106 and Chrome 92.0.4515.131. We view that the habits you noticed may be relied on chrome model used as we didn’t see any BSOD points on our finish. Therefore, we take into account this as not a bug.

Vivaldi: It is a design limitation of Home windows 10; it doesn’t restrict utility reminiscence utilization, and easily makes use of pagefile (digital reminiscence) when it runs out of RAM. That is slower to reply as a result of it should be learn from disk.

Microsoft: Our crew was capable of reproduce this problem, however it doesn’t meet our bar for servicing with a right away safety replace. Whereas this leads to a denial of service situation, this will solely be triggered domestically and is the results of useful resource exhaustion. An attacker wouldn’t be capable of set off any extra weak situations or retrieve data that might be useful in different assaults on the system. We can be closing this case, however we have now opened a bug with our improvement crew, they usually might take into account addressing this in a future launch of Home windows.

In response to the above, the researcher factors out that it’s attainable to set off the assault remotely by making a malicious file on a distant server and opening it from a weak terminal.

[ad_2]

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments