Jump to content

Search the Community

Showing results for tags 'spectre'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Malwarebytes News
    • Beta Testing Program
  • Malware Removal Help
    • Windows Malware Removal Help & Support
    • Mac Malware Removal Help & Support
    • Mobile Malware Removal Help & Support
    • Malware Removal Self-Help Guides
  • Malwarebytes for Home Support
    • Malwarebytes 3 Support Forum
    • Malwarebytes for Mac Support Forum
    • Malwarebytes for Android Support Forum
    • Malwarebytes for iOS Support
    • False Positives
    • Comments and Suggestions
  • Malwarebytes for Business Support
    • Malwarebytes Endpoint Protection
    • Malwarebytes Incident Response (includes Breach Remediation)
    • Malwarebytes Endpoint Security
    • Malwarebytes Business Products Comments and Suggestions
  • Malwarebytes Tools and Other Products
    • Malwarebytes AdwCleaner
    • Malwarebytes Junkware Removal Tool Support
    • Malwarebytes Anti-Rootkit BETA Support
    • Malwarebytes Techbench USB (Legacy)
    • Malwarebytes Secure Backup discontinued
    • Other Tools
    • Malwarebytes Tools Comments and Suggestions
  • General Computer Help and Security Updates
    • BSOD, Crashes, Kernel Debugging
    • General Windows PC Help
  • Research Center
    • Newest Rogue-Ransomware Threats
    • Newest Malware Threats
    • Newest Mobile Threats
    • Newest IP or URL Threats
    • Newest Mac Threats
    • Report Scam Phone Numbers
  • General
    • General Chat
    • Forums Announcements & Feedback

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Location


Interests

Found 5 results

  1. Please read the following article for further information regarding the recent Meltdown and Spectre Vulnerabilities reported on January 3, 2018, by the Google Project Zero team Also, from our Malwarebytes Labs Meltdown and Spectre: what you need to know Meltdown and Spectre fallout: patching problems persist https://blog.malwarebytes.com/cybercrime/exploits/2018/01/meltdown-and-spectre-fallout-patching-problems-persist/
  2. WARNING!: The following post is for INFORMATIONAL PURPOSES ONLY! I do NOT advise that anyone use this as any kind of tutorial or guide unless they are absolutely certain that they know what they are doing, are prepared to potentially break, hose, crash/BSOD their system, potentially resulting in the loss of data or other system damage/malfunction. I take no responsibility for anyone who chooses to attempt this and ends up damaging and/or crashing their system or wiping any/all data from their OS or anything else that might potentially go wrong in the course of attempting these actions. So, with that scary disclaimer out of the way, here is a story about persistence in the face of planned obsolescence. I'm still using Windows 7 (with no plans to upgrade to any newer version of Windows any time soon and it seems I'm not alone) but I'm running fairly modern hardware (an Intel i7-7700K (Kaby Lake) based system). Unfortunately this means that, at least currently, Microsoft doesn't support any of the CPU microcode updates for my system to secure it against any of the recently exposed vulnerabilities that have been making headlines lately (the now infamous Spectre and Meltdown vulnerabilities; additional info here) because a) I'm not running the only OS they seem to care too much about right now, the glorious Windows 10, and b) because I'm using a modern CPU, which according to MS is not an officially supported combination (even though the two work quite well together, as does my new Samsung 960 PRO NVME SSD and all the other new/modern parts I chose to use in my laptop). This means I had to use a sort of "hack" in order to be able to download/install updates through Windows Update (done ), and that I had to either hope that the OEM who built my laptop would publish a microcode update for my BIOS (unlikely given their smaller size and specialized clientele), or that MS would have a change of heart and push out a version of Intel's microcode update for my CPU to Windows 7 users (not frickin' likely given how adamant they are about this whole "DOWNGRADE UPGRADE TO WINDOWS 10 NAAAAAAOOOOOWWWW!!!!!" kick they seem to be on these days). So, I sought alternatives. I knew (thanks to the fact that MS is doing so for Windows 10, with Intel's assistance) that it was possible to patch my CPU microcode via a driver within the operating system in order to apply some of the mitigations without having to locate a patched BIOS for my motherboard, I just had to find a way to do so in Windows 7. I'd all but given up hope when I just happened to be doing some searching/reading (this thing we old folks call "research" ) on the subject to see if there were any new developments on the Kaby Lake/Windows 7 CPU microcode front, and low and behold, a glimmer of hope. I read the thread thoroughly several times and learned that, not only had Intel actually published their latest CPU microcode for my chip on their website (for Linux, but thankfully it's universal), but someone actually made a tool to use that same microcode to patch CPUs running Windows via their own custom driver that even reports the microcode's status/functionality (or not) to Event Viewer so that I can monitor it (though I also followed the advice in the thread to verify it myself using a tool fit for that purpose). So after all of this, I can now confirm that I'm running Intel's CPU microcode version 84 which, as of this writing, is the latest version available from Intel for my particular chip !: So there you have it. An outdated awesome OS with an exclusive Intel patch. I'm happy , especially with this, my Windows Updates, and my best-in-class exploit protection thanks to Malwarebytes 3 which helps to fend off other pesky, as of yet unpatched (and even unknown) vulnerabilities. Life is good.
  3. What is the best CURRENT options to protect our company from Meltdown and Spectre? We have both Windows 2003 Server and Windows XP with Malwarebytes protection. Our company is in the process of migrating software and it is NECESSARY to keep these computers running with these specific operating systems for the next months to operate this until the migration is complete. Our current software will only operate on Windows 2003 server and Windows XP. Upgrading the operating system is not a viable option. Any timely help and guidance would be greatly appreciated. Thank you in advance.
  4. When windows security patches addressing meltdown security vulnerability were released on January 3, Malwarebytes was not supported, and hence it did not set registry keys required in order to get the update. So I uninstalled Malwarebytes and installed the security update from Windows update. Now, Malwarebytes states that a database update fixes the compatibility issue. But if I download and install Malwarebytes again, will it automatically come with the latest "database update"? Or will I have to run an update from inside it, to ensure compatibility with the January windows security patches? If latter, can it cause crashes or BSODs during the time internal when it's installed but not fully updated? (Because it's essentially incompatible during that time) Thanks!
  5. Hi there, I'm using Malwarebytes 3.3.1.2183. I see that Meltdown / Spectre Vulnerabilites are supposed to be mitigated by Microsoft hotfixes (KB4056892-97) patches, and before the patch, the AV companies are strictly instructed to prepare the system for the patch. I read "HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" registry key is added to system during patching process. What i would like to know: Isn't Microsoft creating that key if we install the hotfix patch? Or Malwarebytes creating the key during 1.0.3624 update? What behaviours would happen if i update Malwarebytes update package version to 1.0.3624 and DO NOT INSTALL Microsoft hotfix on KB4056897? Will i still have this key or any registry/filesystem modification, if i just update Malwarebytes update package to 1.0.3624? I just want to get latest malware database definitions as well. Thanks for the tip!
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.