ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows 7 "Total Meltdown" from MS Meltdown Patch, Major Security Vulnerability

    IT Discussion
    windows 7 windows security meltdown microsoft patch toms hardware
    5
    7
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mlnews
      last edited by

      Security researchers are warning that Microsoft's Windows 7 Meltdown patch is so bad that it makes security much worse compared to the Meltdown risk it is supposed to fix.

      "..the fix that Microsoft provided to Windows 7 computers for the Meltdown flaw, which could allow attackers to read kernel memory at a speed of 120 KB/s, would now allow attackers to read the same kernel memory with a speed of gigabytes per second."

      The new bug allows any process to read the complete memory contents of the system, and it also makes it possible to write code to arbitrary memory, too.

      1 Reply Last reply Reply Quote 3
      • S
        scottalanmiller
        last edited by

        Whoops

        1 Reply Last reply Reply Quote 0
        • C
          CloudKnight
          last edited by

          0_1522279659220_Homer-Simpson.jpg

          S 1 Reply Last reply Reply Quote 1
          • S
            scottalanmiller @CloudKnight
            last edited by

            @stuartjordan pretty much sums it up.

            1 Reply Last reply Reply Quote 1
            • D
              Danp
              last edited by

              I thought this was resolved in the March patches.

              S 1 Reply Last reply Reply Quote 0
              • S
                scottalanmiller @Danp
                last edited by

                @danp said in Windows 7 "Total Meltdown" from MS Meltdown Patch, Major Security Vulnerability:

                I thought this was resolved in the March patches.

                They've since broken it again 😉

                1 Reply Last reply Reply Quote 1
                • O
                  Obsolesce
                  last edited by

                  You see! This is why you shouldn't patch!

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • First post
                    Last post