Thanks for your reply JustSid.
Now, i am still waiting for a reply from the developers too.

I have no code for checking if an image is good or bad, and I also am not sure that such code can be found in online libraries, as it's an unusual task. Most libraries just assume that the image is good. So probably you have to code that yourself in a lite-C script.

Basically you need to do a consistency check of the header of any image format that you want to load. Dependent on the compression algorithm, you might also need to check the content.

Sorry, but in that case you are using shitty libraries. All libraries I've mentioned above do check the image instead of simply trusting third party content.
Malicious images have been used as attack vectors for remote code execution and privilege escalation in the past, doing a quick search over the CVEs filed in the past few years yields dozens of results.

You might want to argue that it's just a game and no one cares about games, at least that's the attitude of mot game developers (CryTek famously screwed up their Diffie-Hellman handhsake implementation in Crysis), but I personally would prefer to spend a few more CPU cycles checking the image than publishing an attack vector into my users systems. YMMV.

There are no "shitty libraries", whatever that means. Maybe you misunderstood something. It is theoretically possible to transport malicious code in images, but no library will "check the image" for that. An image library is for loading images, not for detecting malicious content.

The only thing an image loader can do is checking the consistency of the image header, and this only to a certain degree. For PC games, the most common image loading library is DirectX, which is also used by Gamestudio. It tends to crash with bad images, so it seems not to do any checks of that kind. If you want to check the image in any way, you need to do that by script before loading it.

@jcl does it crash or does it throw exceptions?

An exception is not an alternative to a crash, it is an event in a software program that happens _after_ a crash, and causes the error messages that are discussed in this thread.

http://en.wikipedia.org/wiki/Exception_handling

Noooot really. An exception is not always caused by a Crash. The core of it(and its handling) is the the rewinding of the stack to a known state including an id/message of what or why it happend.

Thanks for your reply, excuse me for the late.