<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Intel AMT - quick temporary fix until new BIOS release ? in Intel vPro® Platform</title>
    <link>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516742#M6099</link>
    <description>&lt;P&gt;Sorry I forgot to stop the services before to delete them and checking back, so adding&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sc stop LMS&lt;/P&gt;&lt;P&gt;sc stop jhi_service&lt;/P&gt;</description>
    <pubDate>Thu, 11 May 2017 06:27:42 GMT</pubDate>
    <dc:creator>RCarc</dc:creator>
    <dc:date>2017-05-11T06:27:42Z</dc:date>
    <item>
      <title>Intel AMT - quick temporary fix until new BIOS release ?</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516740#M6097</link>
      <description>&lt;P&gt;My quick temporary fix regarding CVE-2017-5689 vulnerability until you can apply a new BIOS update:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Change default admin name account to something random, do not create another admin account:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this approach viable if admin account name is unknown to attacker ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Update 7-05-2017:&lt;/P&gt;&lt;P&gt;This method was confirmed by other professionals to be effective for protecting your computer from remote AMT login !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Renaming default admin name account to something random will protect your computer with AMT active &lt;B&gt;only&lt;/B&gt; from other host accessing your AMT computer by LAN or WAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;It will NOT protect you from login/attack via local interface with LMS access !!!&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;It is best to use AMT with TLS so connection and traffic will be encrypted and admin name account can't be sniffed !&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Remember you are still vulnerable from attack via local interface LMS access !!!&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are looking for 100% protection then follow Intel advisory and unprovison and disable AMT !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;A href="https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00075&amp;amp;languageid=en-fr"&gt;https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00075&amp;amp;languageid=en-fr&lt;/A&gt; &lt;A href="https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00075&amp;amp;languageid=en-fr"&gt;https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00075&amp;amp;languageid=en-fr&lt;/A&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Lucian L.&lt;/P&gt;</description>
      <pubDate>Sat, 06 May 2017 12:48:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516740#M6097</guid>
      <dc:creator>LL4</dc:creator>
      <dc:date>2017-05-06T12:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Intel AMT - quick temporary fix until new BIOS release ?</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516741#M6098</link>
      <description>&lt;P&gt;I just set up the following into a domain-logon script to disable and or delete files as suggested in the INTEL-SA-00075 Mitigation Guide. Can someone confirm whether this fix will be enough until we can apply the announced manufacturers' BIOS patches ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot, Rosario&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REM disable Intel AMT and LMS for security reasons&lt;/P&gt;&lt;P&gt;sc config LMS start=disabled&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;sc config jhi_service start=disabled&lt;P&gt;rem sc delete LMS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;rem sc delete jhi_service&lt;P&gt;rem erase /f /s /q "&lt;A&gt;C:\Program&lt;/A&gt; Files (x86)\Intel\Intel(R) Management Engine Components\LMS\LMS.exe"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;rem erase /f /s /q "&lt;A&gt;C:\Program&lt;/A&gt; Files (x86)\Intel\Intel(R) Management Engine Components\DAL\jhi_service.exe"&lt;P&gt;rem or everything in there&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;rem erase /f /s /q "&lt;A&gt;C:\Program&lt;/A&gt; Files (x86)\Intel\Intel(R) Management Engine Components\*.*"&lt;P&gt;&lt;/P&gt;&lt;P&gt;rem check back and write into log files:&lt;/P&gt;&lt;P&gt;netstat -na | findstr "\&amp;lt;16993\&amp;gt; \&amp;lt;16992\&amp;gt; \&amp;lt;16994\&amp;gt; \&amp;lt;16995\&amp;gt; \&amp;lt;623\&amp;gt; \&amp;lt;664\&amp;gt;" &amp;gt;&amp;gt; &lt;A&gt;c:\temp\intelLMS.log&lt;/A&gt;&lt;/P&gt;&lt;P&gt;start &lt;A&gt;c:\windows\IntelLMS\Intel-SA-00075-console.exe&lt;/A&gt; -f -p &lt;A&gt;c:\temp\&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 14:20:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516741#M6098</guid>
      <dc:creator>RCarc</dc:creator>
      <dc:date>2017-05-10T14:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: Intel AMT - quick temporary fix until new BIOS release ?</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516742#M6099</link>
      <description>&lt;P&gt;Sorry I forgot to stop the services before to delete them and checking back, so adding&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sc stop LMS&lt;/P&gt;&lt;P&gt;sc stop jhi_service&lt;/P&gt;</description>
      <pubDate>Thu, 11 May 2017 06:27:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/Intel-AMT-quick-temporary-fix-until-new-BIOS-release/m-p/516742#M6099</guid>
      <dc:creator>RCarc</dc:creator>
      <dc:date>2017-05-11T06:27:42Z</dc:date>
    </item>
  </channel>
</rss>

