If you're actually following it proves exactly what I'm saying, the gif has nothing to do with it, Firefox isn't blowing up opening that gif, it's hitting whatever framework leak exists.
This is like saying "DOCX bluescreens Windows" (which implies something that could possibly be exploited in some pretty scary ways) when in reality Word just happens to make some syscall that bluescreens Windows no matter who calls it
I don’t know why you made up your mind on this without having any details.
The person reporting is the author of a graphics editor, he damn well knows the difference between a bug in his own editor and system frameworks. The issue seems to be with opening the GIF via default system frameworks, not anything special the editor is doing. Chances are it will affect any other programs using the same frameworks, maybe even GIF viewers.
"DOCX bluescreens Windows" is exactly how your hypothetical scenario would be described.
"Bush hid the facts" is described as a Notepad bug, even though it's a bug in a specific WinAPI function used by Notepad and thus would also affect other programs that used that function. It was discovered on Notepad, it became popular as a bug of Notepad, and so it's considered a Notepad bug.
It'd be kind of crazy if there was something inherent to the TXT that when opened in any program made that bug occur! But the issue was with Notepad! Much more believable!
Windows bug would be acceptable too, or WinAPI bug :)
This isn't that complicated, I don't mind teaching y'all how to not write non-clickbait headlines
This is like saying "DOCX bluescreens Windows" (which implies something that could possibly be exploited in some pretty scary ways) when in reality Word just happens to make some syscall that bluescreens Windows no matter who calls it