Well so far my first conclusion:
When chosing save attachment... it apperently tries to decode whatever it
thinks it is... resulting in some binary garbage... kinda nice since I wrote
*** shit in that test ;) :)
Can you "decode it" and find out what I wrote ? ;) LOL funny.
Anyway this could present a dangerous attack vector... (which is probably
already well known...)
However still kinda interesting because if there is a bug in the decode
process which could be exploited...
then even saving an attachment to the disk could be dangerous ?!
And maybe that's not yet a well known exploit/attack vector ? ;)
I hope I don't trigger any script kiddies or researches out there !
THIS USENET WORLD COULD BECOME DANGEROUS !
I LIKE IT ! ;) =D LOL.
In other words... please do bring down the system to a screaming DEATH.
I would enjoy seeing that... but be friendly... just write one little file
to the disk saying:
YOUR BASE BELONG TO US.TXT
And inside it would say:
YOUR HARDDISK COULD HAVE BEEN FORMATTED, THAT'S WHY ALL YOUR BASE COULD HAVE
BELONGED TO US ! ;) =D