2 ms·

> games don't need memory safety if they're single player, or even multiplayer co-op against AI. I've seen a bug in handle convert function* in Warcraft 3 tha

by Ygg2 4y ago

> games don't need memory safety if they're single player, or even multiplayer co-op against AI. I've seen a bug in handle convert function* in Warcraft 3 that resulted in bunch of maps, some singleplayer, some coop, some MP that lead to crashes (E can't find much material about it). So no, memory security matters even in SP games with user made content and bug. Attacker can spoof or take a user mod and exploit it for their own gains * Warcraft 3 had a really rudimentary language called JASS, however due to a way some handle convert function could leak address of objects, an entire new language stack (vJASS) was formed around it. Many maps embraced vJass. And several years later it turned out that function could be exploited.

unsafecast 4y ago
> I've seen a bug in handle convert function* in Warcraft 3 that resulted in bunch of maps, some singleplayer, some coop, some MP that lead to crashes (E can't find much material about it). Crashes that didn't cause a lot of damage. Using a language like Rust could add way more overhead than it's worth. The GP's point was that some applications just don't require complete safety, a crash or two won't kill anyone (which could happen literally in a hospital computer for example).
- Ygg2 4y ago
  > Crashes that didn't cause a lot of damage. Update. Crashes and RCE in fanmade maps. Looking at https://wc3we.fandom.com/wiki/Jass_Coding https://wc3we.fandom.com/wiki/Jass_Coding I found a reference to the bug being fixed in 1.24. And tracking that down lead to: https://gaming-tools.com/warcraft-3/patch-1-24/ https://gaming-tools.com/warcraft-3/patch-1-24/ One of the errors fixed: > Bug Fix: Fixed an __exploit that allowed users to execute arbitrary code__ in Warcraft 3 Funmaps. > Bug Fix: Fixed several World Editor crashes. > New JASS has table functions have been added to the Warcraft 3 World Editor, to fix unsafe type casting.(Save Item Handle, Unit Handle, Load Item Handle, Load Unit Handle, Get Handle ID). EDIT: I was right originally, game error in modded games can lead to horrible exploits.

by Ygg2 4y ago

unsafecast 4y ago

> I've seen a bug in handle convert function* in Warcraft 3 that resulted in bunch of maps, some singleplayer, some coop, some MP that lead to crashes (E can't find much material about it). Crashes that didn't cause a lot of damage. Using a language like Rust could add way more overhead than it's worth. The GP's point was that some applications just don't require complete safety, a crash or two won't kill anyone (which could happen literally in a hospital computer for example).

Ygg2 4y ago
> Crashes that didn't cause a lot of damage. Update. Crashes and RCE in fanmade maps. Looking at https://wc3we.fandom.com/wiki/Jass_Coding https://wc3we.fandom.com/wiki/Jass_Coding I found a reference to the bug being fixed in 1.24. And tracking that down lead to: https://gaming-tools.com/warcraft-3/patch-1-24/ https://gaming-tools.com/warcraft-3/patch-1-24/ One of the errors fixed: > Bug Fix: Fixed an __exploit that allowed users to execute arbitrary code__ in Warcraft 3 Funmaps. > Bug Fix: Fixed several World Editor crashes. > New JASS has table functions have been added to the Warcraft 3 World Editor, to fix unsafe type casting.(Save Item Handle, Unit Handle, Load Item Handle, Load Unit Handle, Get Handle ID). EDIT: I was right originally, game error in modded games can lead to horrible exploits.