Overrun of a stack-based buffer

Report · Jul 04, 2021

I got the system error (Creative Cloud) saying "System detected an overrun of
a stack-based buffer in this application. This overrun could potentially

allow a malicious user to gain control of this application".

Question:

Is the overrun caused only by a third-party attack? Is the issue sometimes
caused by system error that is not related to attack, such as freezing I
mention below? Is there no potential risk if the application is uninstalled?

Details:

The PC (Windows10) kept overheating and freezing for minutes
while surfing Internet.
Pressing Ctrl+Alt+Delete but Task Manager did not open because of
the freezing. Closing the lid to make the PC sleep once, I opened it and
got the error of the above-mentioned overrun. The PC kept freezing and
I turned it off by the power button.

System File Checker did not find any integrity violations.
I don't find any trace suspicious processes on TCP view.

Scanning with an antivirus software did not find any problems.
My PC is working correctly.

Considering the consequence, was the application affected by the system error,
not a third-party attack?

Report · Mar 22, 2022

Hi there,

We're sorry for the delay. Are you still having trouble with the issue? Would you mind telling us about the version of the Creative Cloud Application? Since when have you been seeing this issue? Does it start after installing the Creative Cloud app? Have you tried any troubleshooting steps?

If you're receiving the same error while working on other apps which are installed in your computer then, please check this link and see if that helps: https://answers.microsoft.com/en-us/windows/forum/all/solvederror-system-detected-an-overrun-of-a-st...

Regards,

Tarun

Report · Aug 02, 2022

I have an inference. The inference is based upon the following: Adobe's reputation; my experience of Adobe products; the fact that I saw this error message moments after allow some Adobe Reader component - a component that I do not use - through my firewall. The inference is: this is an Adobe bug. Given the scariness of the error message, and the seeming fact that after I dismissed the message explorer restarted, it is a serious error.