6 ms·

Not to sound like a broken record but…. This was yet another memory management bug that would have been prevented if using a memory safe language

• a1a106ed5 5y ago
  On a brighter note, apple is currently in the process of converting almost all iMessage components to Swift for this reason. I'm sure it is taking many engineering hours, and image parsers/open source libraries like this are the most difficult to convert.
  • zionic 5y ago
    Let’s hope they make swift work of it
  • deleted 5y ago
    [deleted]
  • lenkite 5y ago
    Is there a link that mentions this ? The bug was in the ImageIO/Core Graphics layer so are they re-writing all Core Graphics components in Swift ?
    • smoldesu 5y ago
      Yeah, something tells me that they're not going to be rewriting an image decoder to have a runtime...
  • mensetmanusman 5y ago
    1000 FTEs thwart the world’s nation state hackers?
  • saagarjha 5y ago
    Just one component, the one that parses incoming messages. The problem here is that it parsed the message and decided to pass it to ImageIO, which is written in C++.
• zionic 5y ago
  I’m only a few more CVE’s from advocating C++ and Objective(ly)-C(rap) proponents be subject to registration and public humiliation whenever the (inevitable) next issue occurs. I get it, legacy crap has momentum and you can’t ignore that. What’s not ok is the mountain of people who pretend that’s not a problem.
  • deleted 5y ago
    [deleted]
  • pjmlp 5y ago
    Hence why having legal liability is so relevant for making this a reality. The industry will only really change when pushed to do so.
• trasz 5y ago
  Or memory safe hardware.