you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 4 months ago (4 children)

Microsoft confirmed the issue on June 18 and said a fix would not arrive until July 14. The company attributed the bug to a security hardening change that closed a 23-year-old unchecked-buffer vulnerability in the Windows Shell’s desktop.ini processor.

Inspiring confidence!

  • source
  • hideshow 4 child comments
  • [–] 2 points 4 months ago (2 children)

    I'm confused by that last sentence. Does mean that the bug stems from patching a 23-year old vulnerability, or that the bug is because of a patch made to fix the vulnerability 23 years ago?

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (1 reply)