Intel Management Engine - Revision history

Mr Pollo at 20:44, 5 March 2026

2026-03-05T20:44:32Z

← Older revision		Revision as of 20:44, 5 March 2026
Line 1:		Line 1:
	{{Incomplete ~~section~~}}{{StubNotice}}{{ProductCargo		{{Incomplete}}{{StubNotice}}{{ProductCargo
	\|Company=Intel		\|Company=Intel
	\|ProductLine=Intel Management Engine		\|ProductLine=Intel Management Engine
Line 57:		Line 57:
	\|2020		\|2020
	\|Several vulnerabilities were found in Intel AMT, allowing hackers to add a root kit.<ref name=":3" /><ref>{{Cite web \|last=Larabe \|first=Michael \|date=2020-09-08 \|title=Intel AMT Hit By Another "Critical" Security Vulnerability \|url=https://www.semiaccurate.com/2016/01/20/intel-puts-out-secure-cpus-based-on-insecurity/ \|url-status=live \|access-date=2026-02-03 \|website=phoronix \|archive-url=http://web.archive.org/web/20260108035650/https://www.semiaccurate.com/2016/01/20/intel-puts-out-secure-cpus-based-on-insecurity/ \|archive-date=8 Jan 2026}}</ref>		\|Several vulnerabilities were found in Intel AMT, allowing hackers to add a root kit.<ref name=":3" /><ref>{{Cite web \|last=Larabe \|first=Michael \|date=2020-09-08 \|title=Intel AMT Hit By Another "Critical" Security Vulnerability \|url=https://www.semiaccurate.com/2016/01/20/intel-puts-out-secure-cpus-based-on-insecurity/ \|url-status=live \|access-date=2026-02-03 \|website=phoronix \|archive-url=http://web.archive.org/web/20260108035650/https://www.semiaccurate.com/2016/01/20/intel-puts-out-secure-cpus-based-on-insecurity/ \|archive-date=8 Jan 2026}}</ref>
	\|CVE 2020-0535<ref>{{Cite web \|~~first~~=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0535 Detail \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0535 \|url-status=live \|access-date=2026-02-03 \|website=nist.gov \|archive-url=http://web.archive.org/web/20260104090546/https://nvd.nist.gov/vuln/detail/CVE-2020-0535 \|archive-date=4 Jan 2026}}</ref><ref>{{Cite web \|~~first~~=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0531 \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0531 \|url-status=live \|access-date=2026-02-03 \|website=Nist \|archive-url=http://web.archive.org/web/20250822152535/https://nvd.nist.gov/vuln/detail/CVE-2020-0531 \|archive-date=22 Aug 2025}}</ref><ref>{{Cite web \|~~first~~=Intel \|date=2020-11-10 \|title=2020.2 IPU – Intel® CSME, SPS, TXE, AMT and DAL Advisory \|url=https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00391.html \|url-status=live \|access-date=2026-02-03 \|website=Intel \|archive-url=http://web.archive.org/web/20251201040922/https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00391.html \|archive-date=1 Dec 2025}}</ref>		\|CVE 2020-0535<ref>{{Cite web \|author=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0535 Detail \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0535 \|url-status=live \|access-date=2026-02-03 \|website=nist.gov \|archive-url=http://web.archive.org/web/20260104090546/https://nvd.nist.gov/vuln/detail/CVE-2020-0535 \|archive-date=4 Jan 2026}}</ref><ref>{{Cite web \|author=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0531 \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0531 \|url-status=live \|access-date=2026-02-03 \|website=Nist \|archive-url=http://web.archive.org/web/20250822152535/https://nvd.nist.gov/vuln/detail/CVE-2020-0531 \|archive-date=22 Aug 2025}}</ref><ref>{{Cite web \|author=Intel \|date=2020-11-10 \|title=2020.2 IPU – Intel® CSME, SPS, TXE, AMT and DAL Advisory \|url=https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00391.html \|url-status=live \|access-date=2026-02-03 \|website=Intel \|archive-url=http://web.archive.org/web/20251201040922/https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00391.html \|archive-date=1 Dec 2025}}</ref>
	\|}		\|}

Bananabot: Added archive URLs for 20 citation(s) using CRWCitationBot

2026-02-23T05:45:57Z

Added archive URLs for 20 citation(s) using CRWCitationBot

Show changes

AnotherConsumerRightsPerson: http to https with AutoWikiBrowser, replaced: http: → https: (2)

2026-02-11T17:47:39Z

http to https with AutoWikiBrowser, replaced: http: → https: (2)

← Older revision		Revision as of 17:47, 11 February 2026
Line 10:		Line 10:
	\|Logo=Intel logo.svg}}		\|Logo=Intel logo.svg}}

	The '''[[Intel]] Management Engine (ME)''' is an embedded microcontroller integrated into Intel's chipsets since 2008. From version 11 onwards, it runs a (closed-source) modified version of [https://www.minix3.org/ MINIX] as its operating system.<ref name=":4">{{Cite web \|date=2023-09-26 \|title=What is Intel® Management Engine? \|url=https://www.intel.com/content/www/us/en/support/articles/000008927/software/chipset-software.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref><ref name=":5">{{Cite web \|last=Ermolov \|first=Mark \|last2=Goryachy \|first2=Maxim \|date=28 Aug 2017 \|title=Disabling Intel ME 11 via undocumented mode \|url=https://web.archive.org/web/20201201175708/~~http~~://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 \|url-status=dead \|access-date=2026-02-04 \|website=Positive Technologies}}</ref><ref>{{Cite web \|last=Tanenbaum \|first=Andrew S. \|title=An Open Letter to Intel \|url=https://www.cs.vu.nl/~ast/intel/ \|url-status=live \|access-date=2026-02-04 \|website=www.cs.vu.nl}}</ref>.		The '''[[Intel]] Management Engine (ME)''' is an embedded microcontroller integrated into Intel's chipsets since 2008. From version 11 onwards, it runs a (closed-source) modified version of [https://www.minix3.org/ MINIX] as its operating system.<ref name=":4">{{Cite web \|date=2023-09-26 \|title=What is Intel® Management Engine? \|url=https://www.intel.com/content/www/us/en/support/articles/000008927/software/chipset-software.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref><ref name=":5">{{Cite web \|last=Ermolov \|first=Mark \|last2=Goryachy \|first2=Maxim \|date=28 Aug 2017 \|title=Disabling Intel ME 11 via undocumented mode \|url=https://web.archive.org/web/20201201175708/https://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 \|url-status=dead \|access-date=2026-02-04 \|website=Positive Technologies}}</ref><ref>{{Cite web \|last=Tanenbaum \|first=Andrew S. \|title=An Open Letter to Intel \|url=https://www.cs.vu.nl/~ast/intel/ \|url-status=live \|access-date=2026-02-04 \|website=www.cs.vu.nl}}</ref>.

	The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.<ref name=":6">{{Cite web \|date=2021-02-18 \|title=Getting Started with Intel® Active Management Technology \|url=https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html \|access-date=2026-02-04 \|publisher=Intel}}</ref>		The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.<ref name=":6">{{Cite web \|date=2021-02-18 \|title=Getting Started with Intel® Active Management Technology \|url=https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html \|access-date=2026-02-04 \|publisher=Intel}}</ref>
Line 40:		Line 40:
	\|-		\|-
	\|2009		\|2009
	\|A "Ring -3 Rootkit" for the Q35 chipset was demonstrated by Invisible Things Lab, allowing an attacker to execute code, even when Intel AMT was disabled in the BIOS.<ref>{{Cite web \|last=Tereshkin \|first=Alexander \|last2=Wojtczuk \|first2=Rafal \|date=29 Jul 2009 \|title=Introducing Ring -3 Rootkits \|url=https://blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|url-status=live \|archive-url=https://web.archive.org/web/20251205092502/~~http~~://www.blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|archive-date=2025-12-05 \|access-date=2026-02-04 \|publisher=Blackhat}}</ref> The bug was subsequently patched by Intel.<ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref>		\|A "Ring -3 Rootkit" for the Q35 chipset was demonstrated by Invisible Things Lab, allowing an attacker to execute code, even when Intel AMT was disabled in the BIOS.<ref>{{Cite web \|last=Tereshkin \|first=Alexander \|last2=Wojtczuk \|first2=Rafal \|date=29 Jul 2009 \|title=Introducing Ring -3 Rootkits \|url=https://blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|url-status=live \|archive-url=https://web.archive.org/web/20251205092502/https://www.blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|archive-date=2025-12-05 \|access-date=2026-02-04 \|publisher=Blackhat}}</ref> The bug was subsequently patched by Intel.<ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref>
	\|'''No CVE'''		\|'''No CVE'''
	\|-		\|-

SinexTitan: better linking

2026-02-04T18:33:32Z

better linking

← Older revision		Revision as of 18:33, 4 February 2026
Line 10:		Line 10:
	\|Logo=Intel logo.svg}}		\|Logo=Intel logo.svg}}

	The '''Intel Management Engine (ME)''' is an embedded microcontroller integrated into Intel's chipsets since 2008. From version 11 onwards, it runs a (closed-source) modified version of [https://www.minix3.org/ MINIX] as its operating system.<ref name=":4">{{Cite web \|date=2023-09-26 \|title=What is Intel® Management Engine? \|url=https://www.intel.com/content/www/us/en/support/articles/000008927/software/chipset-software.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref><ref name=":5">{{Cite web \|last=Ermolov \|first=Mark \|last2=Goryachy \|first2=Maxim \|date=28 Aug 2017 \|title=Disabling Intel ME 11 via undocumented mode \|url=https://web.archive.org/web/20201201175708/http://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 \|url-status=dead \|access-date=2026-02-04 \|website=Positive Technologies}}</ref><ref>{{Cite web \|last=Tanenbaum \|first=Andrew S. \|title=An Open Letter to Intel \|url=https://www.cs.vu.nl/~ast/intel/ \|url-status=live \|access-date=2026-02-04 \|website=www.cs.vu.nl}}</ref>.		The '''[[Intel]] Management Engine (ME)''' is an embedded microcontroller integrated into Intel's chipsets since 2008. From version 11 onwards, it runs a (closed-source) modified version of [https://www.minix3.org/ MINIX] as its operating system.<ref name=":4">{{Cite web \|date=2023-09-26 \|title=What is Intel® Management Engine? \|url=https://www.intel.com/content/www/us/en/support/articles/000008927/software/chipset-software.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref><ref name=":5">{{Cite web \|last=Ermolov \|first=Mark \|last2=Goryachy \|first2=Maxim \|date=28 Aug 2017 \|title=Disabling Intel ME 11 via undocumented mode \|url=https://web.archive.org/web/20201201175708/http://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 \|url-status=dead \|access-date=2026-02-04 \|website=Positive Technologies}}</ref><ref>{{Cite web \|last=Tanenbaum \|first=Andrew S. \|title=An Open Letter to Intel \|url=https://www.cs.vu.nl/~ast/intel/ \|url-status=live \|access-date=2026-02-04 \|website=www.cs.vu.nl}}</ref>.

	The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.<ref name=":6">{{Cite web \|date=2021-02-18 \|title=Getting Started with Intel® Active Management Technology \|url=https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html \|access-date=2026-02-04 \|publisher=Intel}}</ref>		The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.<ref name=":6">{{Cite web \|date=2021-02-18 \|title=Getting Started with Intel® Active Management Technology \|url=https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html \|access-date=2026-02-04 \|publisher=Intel}}</ref>
Line 73:		Line 73:
	==See also==		==See also==

	*[[~~Intel~~]]		*[[AMD Platform Security Processor]]
	*[[Intel CPUs stability issue]]		*[[Intel CPUs stability issue]]

SinexTitan: Intel-ligent edit

2026-02-04T18:00:51Z

Intel-ligent edit

← Older revision		Revision as of 18:00, 4 February 2026
Line 79:		Line 79:
	<references />		<references />
	[[Category:{{PAGENAME}}]]		[[Category:{{PAGENAME}}]]
			[[Category:Intel]]

Beeldscherm: Added and modified some sources

2026-02-04T16:24:41Z

Added and modified some sources

← Older revision		Revision as of 16:24, 4 February 2026
Line 10:		Line 10:
	\|Logo=Intel logo.svg}}		\|Logo=Intel logo.svg}}

	The '''Intel Management Engine (ME)''' is an embedded microcontroller integrated into Intel's chipsets since 2008. From version 11 onwards, it runs a (closed-source) modified version of [https://www.minix3.org/ MINIX] as its operating system.<ref name=":4">{{Cite web \|date=2023-09-26 \|title=What is Intel® Management Engine? \|url=https://www.intel.com/content/www/us/en/support/articles/000008927/software/chipset-software.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref><ref name=":5">{{Cite web \|last=Ermolov \|first=Mark \|last2=Goryachy \|first2=Maxim \|date=28 Aug 2017 \|title=Disabling Intel ME 11 via undocumented mode \|url=https://web.archive.org/web/20201201175708/http://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 \|url-status=dead \|access-date=2026-02-04 \|website=Positive Technologies}}</ref>.		The '''Intel Management Engine (ME)''' is an embedded microcontroller integrated into Intel's chipsets since 2008. From version 11 onwards, it runs a (closed-source) modified version of [https://www.minix3.org/ MINIX] as its operating system.<ref name=":4">{{Cite web \|date=2023-09-26 \|title=What is Intel® Management Engine? \|url=https://www.intel.com/content/www/us/en/support/articles/000008927/software/chipset-software.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref><ref name=":5">{{Cite web \|last=Ermolov \|first=Mark \|last2=Goryachy \|first2=Maxim \|date=28 Aug 2017 \|title=Disabling Intel ME 11 via undocumented mode \|url=https://web.archive.org/web/20201201175708/http://blog.ptsecurity.com/2017/08/disabling-intel-me.html?m=1 \|url-status=dead \|access-date=2026-02-04 \|website=Positive Technologies}}</ref><ref>{{Cite web \|last=Tanenbaum \|first=Andrew S. \|title=An Open Letter to Intel \|url=https://www.cs.vu.nl/~ast/intel/ \|url-status=live \|access-date=2026-02-04 \|website=www.cs.vu.nl}}</ref>.

	The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.<ref name=":6">{{Cite web \|date=2021-02-18 \|title=Getting Started with Intel® Active Management Technology \|url=https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html \|access-date=2026-02-04 \|publisher=Intel}}</ref>		The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.<ref name=":6">{{Cite web \|date=2021-02-18 \|title=Getting Started with Intel® Active Management Technology \|url=https://www.intel.com/content/www/us/en/developer/articles/guide/getting-started-with-active-management-technology.html \|access-date=2026-02-04 \|publisher=Intel}}</ref>
Line 40:		Line 40:
	\|-		\|-
	\|2009		\|2009
	\|A "Ring -3 Rootkit" for the Q35 chipset was demonstrated by Invisible Things Lab, allowing an attacker to execute code, even when Intel AMT was disabled in the BIOS.<ref>{{Cite web \|last=Tereshkin \|first=Alexander \|last2=Wojtczuk \|first2=Rafal \|date=29 Jul 2009 \|title=Introducing Ring -3 Rootkits \|url=https://blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|url-status=live \|archive-url=https://web.archive.org/web/20251205092502/http://www.blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|archive-date=2025-12-05 \|access-date=2026-02-04 \|publisher=Blackhat}}</ref> The bug was subsequently patched by Intel.<ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref> <ref name=":0">{{Cite web \|first=402 Payment Required \|date=2023-06-29 \|title=Intel Management Engine \|url=https://www.youtube.com/watch?v=lQ8k79yNH2A \|url-status=live \|access-date=2026-02-03 \|website=Youtube}}</ref><ref name=":2">{{Cite web \|last=Robin \|first=Thibaud \|date=2025-03-02 \|title=The Mysterious Story of a Troubling Intel Chip \|url=https://blog.trackflaw.com/en/the-mysterious-story-of-a-disturbing-intel-flea/ \|url-status=live \|access-date=2026-02-03 \|website=TrackFlaw}}</ref>		\|A "Ring -3 Rootkit" for the Q35 chipset was demonstrated by Invisible Things Lab, allowing an attacker to execute code, even when Intel AMT was disabled in the BIOS.<ref>{{Cite web \|last=Tereshkin \|first=Alexander \|last2=Wojtczuk \|first2=Rafal \|date=29 Jul 2009 \|title=Introducing Ring -3 Rootkits \|url=https://blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|url-status=live \|archive-url=https://web.archive.org/web/20251205092502/http://www.blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|archive-date=2025-12-05 \|access-date=2026-02-04 \|publisher=Blackhat}}</ref> The bug was subsequently patched by Intel.<ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref>
	\|'''No CVE'''		\|'''No CVE'''
	\|-		\|-
	\|2010		\|2010
	\|An individual by the name of Vassilios Vereris discovered an bypass that allow attackers to remotely enable Intel AMT.<ref>{{Cite web \|date=2026-02-03 \|title=Disabling Intel ME in Firmware \|url=https://ecrsecurity.com/files/DisableIntelME.pdf \|url-status=live \|access-date=2026-02-03 \|website=ecrsecurity}}</ref><ref>{{Cite web \|last=Ververis \|first=Vassilios \|year=2010 \|title=Security Evaluation of Intel's Active Management Technology \|url=https://ia801400.us.archive.org/35/items/100402-vassilios-ververis-with-cover/100402-Vassilios_Ververis-with-cover.pdf \|website=archive.org}}</ref~~> <ref name=":0" /><ref name=":2" /~~>		\|An individual by the name of Vassilios Vereris discovered an bypass that allow attackers to remotely enable Intel AMT.<ref name=":0">{{Cite web \|date=2026-02-03 \|title=Disabling Intel ME in Firmware \|url=https://ecrsecurity.com/files/DisableIntelME.pdf \|url-status=live \|access-date=2026-02-03 \|website=ecrsecurity}}</ref><ref>{{Cite web \|last=Ververis \|first=Vassilios \|year=2010 \|title=Security Evaluation of Intel's Active Management Technology \|url=https://ia801400.us.archive.org/35/items/100402-vassilios-ververis-with-cover/100402-Vassilios_Ververis-with-cover.pdf \|website=archive.org}}</ref>
	\|'''No CVE'''		\|'''No CVE'''
	\|-		\|-
	\|2017		\|2017
	\|Discovered by Maksim Malyutin from Embedi, a bug in Intel AMT allows a hacker to gain admin privileges from a remote location.<ref name=":0" /> Reportedly, Intel was aware of this more than 5 years prior to the report SemiAccurate gave to Intel, however it was dismissed for unknown reasons.<ref>{{Cite web \|last=Demerjian \|first=Charlie \|date=2017-05-01 \|title=Remote security exploit in all 2008+ Intel platforms \|url=https://www.semiaccurate.com/2017/05/01/remote-security-exploit-2008-intel-platforms/ \|url-status=live \|access-date=2026-02-03 \|website=SemiAccurate}}</ref> <ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2017-05-02 \|title=Intel AMT Vulnerability Shows Intel’s Management Engine Can Be Dangerous \|url=https://www.tomshardware.com/news/intel-amt-vulnerability-me-dangerous,34300.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref><ref>{{Cite web \|date=2025-01-11 \|title=The Vulnerability Uncovered \|url=https://umatechnology.org/intel-amt-vulnerability-business-laptops-can-be-exploited-in-mere-seconds/ \|url-status=live \|access-date=2026-02-03 \|website=UMA Technology}}</ref~~><ref name=":0" /~~>		\|Discovered by Maksim Malyutin from Embedi, a bug in Intel AMT allows a hacker to gain admin privileges from a remote location.<ref name=":0" /> Reportedly, Intel was aware of this more than 5 years prior to the report SemiAccurate gave to Intel, however it was dismissed for unknown reasons.<ref>{{Cite web \|last=Demerjian \|first=Charlie \|date=2017-05-01 \|title=Remote security exploit in all 2008+ Intel platforms \|url=https://www.semiaccurate.com/2017/05/01/remote-security-exploit-2008-intel-platforms/ \|url-status=live \|access-date=2026-02-03 \|website=SemiAccurate}}</ref><ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2017-05-02 \|title=Intel AMT Vulnerability Shows Intel’s Management Engine Can Be Dangerous \|url=https://www.tomshardware.com/news/intel-amt-vulnerability-me-dangerous,34300.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref><ref>{{Cite web \|date=2025-01-11 \|title=The Vulnerability Uncovered \|url=https://umatechnology.org/intel-amt-vulnerability-business-laptops-can-be-exploited-in-mere-seconds/ \|url-status=live \|access-date=2026-02-03 \|website=UMA Technology}}</ref>
	\|CVE-2017-5689.<ref>{{Cite web \|date=2017-05-02 \|title=CVE-2017-5689 Detail \|url=https://nvd.nist.gov/vuln/detail/cve-2017-5689 \|url-status=live \|access-date=2026-02-03 \|website=Nist}}</ref>		\|CVE-2017-5689.<ref>{{Cite web \|date=2017-05-02 \|title=CVE-2017-5689 Detail \|url=https://nvd.nist.gov/vuln/detail/cve-2017-5689 \|url-status=live \|access-date=2026-02-03 \|website=Nist}}</ref>
	\|-		\|-
	\|2018		\|2018
	\|Researchers at F-Secure discovered an exploit regarding Intel AMT that allows a hacker with physical access to the machine to bypass the user, BIOS, Bitlocker, and TPM passwords in a matter of 30 seconds. This bug is more severe against corporate laptops. <ref name=":3">{{Cite web \|last=Waldman \|first=Arielle \|date=2020-09-09 \|title=Intel patches critical flaw in Active Management Technology \|url=https://www.techtarget.com/searchsecurity/news/252488831/Intel-patches-critical-flaw-in-Active-Management-Technology \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Ashford \|first=Warwick \|date=2018-01-18 \|title=F-Secure highlights another critical Intel security issue \|url=https://www.computerweekly.com/news/450433078/F-secure-highlights-another-critical-Intel-security-issue \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Subramaniam \|first=Vaidyanathan \|date=2018-01-14 \|title=Gone in 30 seconds: New Intel AMT exploit is scarier than you can ever fathom \|url=https://www.notebookcheck.net/Gone-in-30-seconds-New-Intel-AMT-exploit-is-scarier-than-you-can-ever-fathom.278216.0.html \|url-status=live \|access-date=2026-02-03 \|website=Notebook Check}}</ref><ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2018-01-12 \|title=Intel AMT Allows BitLocker Bypass In Under A Minute \|url=https://www.tomshardware.com/news/intel-amt-bitlocker-bios-bypass,36321.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref>		\|Researchers at F-Secure discovered an exploit regarding Intel AMT that allows a hacker with physical access to the machine to bypass the user, BIOS, Bitlocker, and TPM passwords in a matter of 30 seconds. This bug is more severe against corporate laptops.<ref name=":3">{{Cite web \|last=Waldman \|first=Arielle \|date=2020-09-09 \|title=Intel patches critical flaw in Active Management Technology \|url=https://www.techtarget.com/searchsecurity/news/252488831/Intel-patches-critical-flaw-in-Active-Management-Technology \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Ashford \|first=Warwick \|date=2018-01-18 \|title=F-Secure highlights another critical Intel security issue \|url=https://www.computerweekly.com/news/450433078/F-secure-highlights-another-critical-Intel-security-issue \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Subramaniam \|first=Vaidyanathan \|date=2018-01-14 \|title=Gone in 30 seconds: New Intel AMT exploit is scarier than you can ever fathom \|url=https://www.notebookcheck.net/Gone-in-30-seconds-New-Intel-AMT-exploit-is-scarier-than-you-can-ever-fathom.278216.0.html \|url-status=live \|access-date=2026-02-03 \|website=Notebook Check}}</ref><ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2018-01-12 \|title=Intel AMT Allows BitLocker Bypass In Under A Minute \|url=https://www.tomshardware.com/news/intel-amt-bitlocker-bios-bypass,36321.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref>
	\|'''No CVE'''		\|'''No CVE'''
	\|-		\|-
Line 65:		Line 65:
	==Tools and Tips==		==Tools and Tips==

	There is no official method to disable the ME, however there have been tools and tips developed to allow (partially) disabling the ME.<ref name=":1">{{Cite web \|title=Intel’s Management Engine \|url=https://puri.sm/learn/intel-me/ \|url-status=live \|access-date=2026-02-04 \|publisher=Purism}}</ref>		There is no official method to disable the ME, however there have been tools and tips developed to allow (partially) disabling the ME.<ref name=":0" /><ref name=":1">{{Cite web \|title=Intel’s Management Engine \|url=https://puri.sm/learn/intel-me/ \|url-status=live \|access-date=2026-02-04 \|publisher=Purism}}</ref>

	*[https://github.com/corna/me_cleaner ME Cleaner Tool]		*[https://github.com/corna/me_cleaner ME Cleaner Tool]

Beeldscherm: Some additional information on AMT and the 2009 vulnerability, also fixed small mistakes

2026-02-04T15:46:46Z

Some additional information on AMT and the 2009 vulnerability, also fixed small mistakes

← Older revision		Revision as of 15:46, 4 February 2026
Line 16:		Line 16:
	The power state of the ME is independent from the rest of the system, allowing it to run while the system is turned off, assuming that the system is still receiving power.<ref name=":4" />		The power state of the ME is independent from the rest of the system, allowing it to run while the system is turned off, assuming that the system is still receiving power.<ref name=":4" />

	Additionally, Intel ME also contains several measures to check if it's been tampered with. Several of these measures conclude being inaccessible to the machine BIOS or chosen Operating System, scanning the entire machine every 30 minutes to verify if signature is signed or else the entire machine shutdown, and making it exceptionally difficult to reverse engineer.		Additionally, Intel ME also contains several measures to check if it's been tampered with. These include being inaccessible to the machine BIOS or OS, scanning the entire machine every 30 minutes to verify if signature is signed (otherwise shutting down the system)<sup>[source?]</sup>, and making it exceptionally difficult to reverse engineer.

	Additionally, Intel ME also contains several measures to check if it's been tampered with. These include being inaccessible to the machine BIOS or OS, scanning the entire machine every 30 minutes to verify if signature is signed (otherwise shutting down the system), and making it exceptionally difficult to reverse engineer.
	==Intel AMT==		==Intel AMT==
	One of the services utilizing the capabilities of the Intel ME is '''Intel Active Management (AMT)'''. It is part of a set of technologies marketed as Intel vPro. Intel AMT is built into most modern Intel CPUs, including but not limited to the Intel Core i5, Intel Core i7, Intel Core M, and Intel Xeon series. The AMT has full access to the system and can bypass system firewalls<ref name=":6" /><ref>{{Cite web \|date=2021-01-05 \|title=Intel® Active Management Technology Developers Guide \|url=https://www.intel.com/content/www/us/en/docs/active-management-technology/developer-guide/2021/overview.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref>.		One of the services utilizing the capabilities of the Intel ME is '''Intel Active Management (AMT)'''. It is part of a set of technologies marketed as Intel vPro. Intel AMT is built into most modern Intel CPUs, including but not limited to the Intel Core i5, Intel Core i7, Intel Core M, and Intel Xeon series. The AMT has full access to the system and can bypass system firewalls.<ref name=":6" /><ref>{{Cite web \|date=2021-01-05 \|title=Intel® Active Management Technology Developers Guide \|url=https://www.intel.com/content/www/us/en/docs/active-management-technology/developer-guide/2021/overview.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref> By default, AMT is enabled, on supported chips. AMT support is listed under the "Security & Reliability" section on the intel product website ([https://www.intel.com/content/www/us/en/products/sku/230496/intel-core-i913900k-processor-36m-cache-up-to-5-80-ghz/specifications.html example]).
	[[File:Intel ME boot sequence.png\|alt=Intel ME Boot Sequence for Laptops/Computers \|thumb\|Booting Process]]		[[File:Intel ME boot sequence.png\|alt=Intel ME Boot Sequence for Laptops/Computers \|thumb\|Booting Process]]
	AMT allows remote management of the system by using the ME's network access, exposing 2 ports through which commands can be issued. Some of the many features of the AMT are:<ref name=":6" />		AMT allows remote management of the system by using the ME's network access, exposing 2 ports through which commands can be issued. Some of the many features of the AMT are:<ref name=":6" />
Line 42:		Line 40:
	\|-		\|-
	\|2009		\|2009
	\|~~Developed~~ by Invisible Things Lab, it was ~~discovered that a~~ bug ~~allowed it to access the machine memory~~. <ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref><ref name=":0">{{Cite web \|first=402 Payment Required \|date=2023-06-29 \|title=Intel Management Engine \|url=https://www.youtube.com/watch?v=lQ8k79yNH2A \|url-status=live \|access-date=2026-02-03 \|website=Youtube}}</ref><ref name=":2">{{Cite web \|last=Robin \|first=Thibaud \|date=2025-03-02 \|title=The Mysterious Story of a Troubling Intel Chip \|url=https://blog.trackflaw.com/en/the-mysterious-story-of-a-disturbing-intel-flea/ \|url-status=live \|access-date=2026-02-03 \|website=TrackFlaw}}</ref>		\|A "Ring -3 Rootkit" for the Q35 chipset was demonstrated by Invisible Things Lab, allowing an attacker to execute code, even when Intel AMT was disabled in the BIOS.<ref>{{Cite web \|last=Tereshkin \|first=Alexander \|last2=Wojtczuk \|first2=Rafal \|date=29 Jul 2009 \|title=Introducing Ring -3 Rootkits \|url=https://blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|url-status=live \|archive-url=https://web.archive.org/web/20251205092502/http://www.blackhat.com/presentations/bh-usa-09/TERESHKIN/BHUSA09-Tereshkin-Ring3Rootkit-SLIDES.pdf \|archive-date=2025-12-05 \|access-date=2026-02-04 \|publisher=Blackhat}}</ref> The bug was subsequently patched by Intel.<ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref> <ref name=":0">{{Cite web \|first=402 Payment Required \|date=2023-06-29 \|title=Intel Management Engine \|url=https://www.youtube.com/watch?v=lQ8k79yNH2A \|url-status=live \|access-date=2026-02-03 \|website=Youtube}}</ref><ref name=":2">{{Cite web \|last=Robin \|first=Thibaud \|date=2025-03-02 \|title=The Mysterious Story of a Troubling Intel Chip \|url=https://blog.trackflaw.com/en/the-mysterious-story-of-a-disturbing-intel-flea/ \|url-status=live \|access-date=2026-02-03 \|website=TrackFlaw}}</ref>
	\|'''~~Can't Find~~'''		\|'''No CVE'''
	\|-		\|-
	\|2010		\|2010
	\|An individual by the name of Vassilios Vereris discovered an bypass that allow attackers to remotely enable Intel AMT.~~<ref name=":0" />~~<ref>{{Cite web \|date=2026-02-03 \|title=Disabling Intel ME in Firmware \|url=https://ecrsecurity.com/files/DisableIntelME.pdf \|url-status=live \|access-date=2026-02-03 \|website=ecrsecurity}}</ref><ref name=":2" />		\|An individual by the name of Vassilios Vereris discovered an bypass that allow attackers to remotely enable Intel AMT.<ref>{{Cite web \|date=2026-02-03 \|title=Disabling Intel ME in Firmware \|url=https://ecrsecurity.com/files/DisableIntelME.pdf \|url-status=live \|access-date=2026-02-03 \|website=ecrsecurity}}</ref><ref>{{Cite web \|last=Ververis \|first=Vassilios \|year=2010 \|title=Security Evaluation of Intel's Active Management Technology \|url=https://ia801400.us.archive.org/35/items/100402-vassilios-ververis-with-cover/100402-Vassilios_Ververis-with-cover.pdf \|website=archive.org}}</ref> <ref name=":0" /><ref name=":2" />
	\|'''~~Can't Find~~'''		\|'''No CVE'''
	\|-		\|-
	\|2017		\|2017
	\|Discovered by Maksim Malyutin from Embedi, a bug in Intel AMT allows an hacker to gain admin privileges from a remote location.<ref name=":0" /> Reportedly, Intel ~~new about~~ this more than 5 years prior ~~from~~ the report SemiAccurate gave to ~~intel~~, however it was dismissed for unknown reasons.<ref>{{Cite web \|last=Demerjian \|first=Charlie \|date=2017-05-01 \|title=Remote security exploit in all 2008+ Intel platforms \|url=https://www.semiaccurate.com/2017/05/01/remote-security-exploit-2008-intel-platforms/ \|url-status=live \|access-date=2026-02-03 \|website=SemiAccurate}}</ref> <ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2017-05-02 \|title=Intel AMT Vulnerability Shows Intel’s Management Engine Can Be Dangerous \|url=https://www.tomshardware.com/news/intel-amt-vulnerability-me-dangerous,34300.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref><ref>{{Cite web \|date=2025-01-11 \|title=The Vulnerability Uncovered \|url=https://umatechnology.org/intel-amt-vulnerability-business-laptops-can-be-exploited-in-mere-seconds/ \|url-status=live \|access-date=2026-02-03 \|website=UMA Technology}}</ref><ref name=":0" />		\|Discovered by Maksim Malyutin from Embedi, a bug in Intel AMT allows a hacker to gain admin privileges from a remote location.<ref name=":0" /> Reportedly, Intel was aware of this more than 5 years prior to the report SemiAccurate gave to Intel, however it was dismissed for unknown reasons.<ref>{{Cite web \|last=Demerjian \|first=Charlie \|date=2017-05-01 \|title=Remote security exploit in all 2008+ Intel platforms \|url=https://www.semiaccurate.com/2017/05/01/remote-security-exploit-2008-intel-platforms/ \|url-status=live \|access-date=2026-02-03 \|website=SemiAccurate}}</ref> <ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2017-05-02 \|title=Intel AMT Vulnerability Shows Intel’s Management Engine Can Be Dangerous \|url=https://www.tomshardware.com/news/intel-amt-vulnerability-me-dangerous,34300.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref><ref>{{Cite web \|date=2025-01-11 \|title=The Vulnerability Uncovered \|url=https://umatechnology.org/intel-amt-vulnerability-business-laptops-can-be-exploited-in-mere-seconds/ \|url-status=live \|access-date=2026-02-03 \|website=UMA Technology}}</ref><ref name=":0" />
	\|CVE-2017-5689.<ref>{{Cite web \|date=2017-05-02 \|title=CVE-2017-5689 Detail \|url=https://nvd.nist.gov/vuln/detail/cve-2017-5689 \|url-status=live \|access-date=2026-02-03 \|website=Nist}}</ref>		\|CVE-2017-5689.<ref>{{Cite web \|date=2017-05-02 \|title=CVE-2017-5689 Detail \|url=https://nvd.nist.gov/vuln/detail/cve-2017-5689 \|url-status=live \|access-date=2026-02-03 \|website=Nist}}</ref>
	\|-		\|-
	\|2018		\|2018
	\|Researchers at F-Secure discovered an exploit regarding Intel AMT that allows an hacker with physical access to the machine to bypass an user, BIOS, Bitlocker, and TPM passwords in a matter of 30 seconds. This bug is more severe against corporate laptops. <ref name=":3">{{Cite web \|last=Waldman \|first=Arielle \|date=2020-09-09 \|title=Intel patches critical flaw in Active Management Technology \|url=https://www.techtarget.com/searchsecurity/news/252488831/Intel-patches-critical-flaw-in-Active-Management-Technology \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Ashford \|first=Warwick \|date=2018-01-18 \|title=F-Secure highlights another critical Intel security issue \|url=https://www.computerweekly.com/news/450433078/F-secure-highlights-another-critical-Intel-security-issue \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Subramaniam \|first=Vaidyanathan \|date=2018-01-14 \|title=Gone in 30 seconds: New Intel AMT exploit is scarier than you can ever fathom \|url=https://www.notebookcheck.net/Gone-in-30-seconds-New-Intel-AMT-exploit-is-scarier-than-you-can-ever-fathom.278216.0.html \|url-status=live \|access-date=2026-02-03 \|website=Notebook Check}}</ref><ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2018-01-12 \|title=Intel AMT Allows BitLocker Bypass In Under A Minute \|url=https://www.tomshardware.com/news/intel-amt-bitlocker-bios-bypass,36321.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref>		\|Researchers at F-Secure discovered an exploit regarding Intel AMT that allows a hacker with physical access to the machine to bypass the user, BIOS, Bitlocker, and TPM passwords in a matter of 30 seconds. This bug is more severe against corporate laptops. <ref name=":3">{{Cite web \|last=Waldman \|first=Arielle \|date=2020-09-09 \|title=Intel patches critical flaw in Active Management Technology \|url=https://www.techtarget.com/searchsecurity/news/252488831/Intel-patches-critical-flaw-in-Active-Management-Technology \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Ashford \|first=Warwick \|date=2018-01-18 \|title=F-Secure highlights another critical Intel security issue \|url=https://www.computerweekly.com/news/450433078/F-secure-highlights-another-critical-Intel-security-issue \|url-status=live \|access-date=2026-02-03 \|website=TechTarget}}</ref><ref>{{Cite web \|last=Subramaniam \|first=Vaidyanathan \|date=2018-01-14 \|title=Gone in 30 seconds: New Intel AMT exploit is scarier than you can ever fathom \|url=https://www.notebookcheck.net/Gone-in-30-seconds-New-Intel-AMT-exploit-is-scarier-than-you-can-ever-fathom.278216.0.html \|url-status=live \|access-date=2026-02-03 \|website=Notebook Check}}</ref><ref>{{Cite web \|last=Armasu \|first=Lucian \|date=2018-01-12 \|title=Intel AMT Allows BitLocker Bypass In Under A Minute \|url=https://www.tomshardware.com/news/intel-amt-bitlocker-bios-bypass,36321.html \|url-status=live \|access-date=2026-02-03 \|website=Tom's Hardware}}</ref>
	\|no CVE ~~number~~		\|'''No CVE'''
	\|-		\|-
	\|2020		\|2020
	\|Several vulnerabilities were found in Intel AMT ~~that allows~~ hackers to add a root kit. <ref name=":3" /><ref>{{Cite web \|last=Larabe \|first=Michael \|date=2020-09-08 \|title=Intel AMT Hit By Another "Critical" Security Vulnerability \|url=https://www.semiaccurate.com/2016/01/20/intel-puts-out-secure-cpus-based-on-insecurity/ \|url-status=live \|access-date=2026-02-03 \|website=phoronix}}</ref>		\|Several vulnerabilities were found in Intel AMT, allowing hackers to add a root kit.<ref name=":3" /><ref>{{Cite web \|last=Larabe \|first=Michael \|date=2020-09-08 \|title=Intel AMT Hit By Another "Critical" Security Vulnerability \|url=https://www.semiaccurate.com/2016/01/20/intel-puts-out-secure-cpus-based-on-insecurity/ \|url-status=live \|access-date=2026-02-03 \|website=phoronix}}</ref>
	\|CVE 2020-0535<ref>{{Cite web \|first=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0535 Detail \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0535 \|url-status=live \|access-date=2026-02-03 \|website=nist.gov}}</ref><ref>{{Cite web \|first=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0531 \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0531 \|url-status=live \|access-date=2026-02-03 \|website=Nist}}</ref><ref>{{Cite web \|first=Intel \|date=2020-11-10 \|title=2020.2 IPU – Intel® CSME, SPS, TXE, AMT and DAL Advisory \|url=https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00391.html \|url-status=live \|access-date=2026-02-03 \|website=Intel}}</ref>		\|CVE 2020-0535<ref>{{Cite web \|first=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0535 Detail \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0535 \|url-status=live \|access-date=2026-02-03 \|website=nist.gov}}</ref><ref>{{Cite web \|first=National Vulnerability Database \|date=2020-06-15 \|title=CVE-2020-0531 \|url=https://nvd.nist.gov/vuln/detail/CVE-2020-0531 \|url-status=live \|access-date=2026-02-03 \|website=Nist}}</ref><ref>{{Cite web \|first=Intel \|date=2020-11-10 \|title=2020.2 IPU – Intel® CSME, SPS, TXE, AMT and DAL Advisory \|url=https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00391.html \|url-status=live \|access-date=2026-02-03 \|website=Intel}}</ref>
	\|}		\|}
Line 67:		Line 65:
	==Tools and Tips==		==Tools and Tips==

	~~While Intel ME~~ is ~~normally not possible~~ to be disable ~~(except in some cases)~~, there have been tools and tips developed to allow (partially) disabling the ME.<ref>{{Cite web \|title=Intel’s Management Engine \|url=https://puri.sm/learn/intel-me/ \|url-status=live \|access-date=2026-02-04 \|publisher=Purism}}</ref>		There is no official method to disable the ME, however there have been tools and tips developed to allow (partially) disabling the ME.<ref name=":1">{{Cite web \|title=Intel’s Management Engine \|url=https://puri.sm/learn/intel-me/ \|url-status=live \|access-date=2026-02-04 \|publisher=Purism}}</ref>

	*[https://github.com/corna/me_cleaner ME Cleaner Tool]		*[https://github.com/corna/me_cleaner ME Cleaner Tool]
	*Using an CPU or Computer made before 2008.		*Using an CPU or Computer made before 2008
	*Buying Computers with Intel ME ~~completely~~ disabled like [https://puri.sm/ Purism] and [https://system76.com/ System76]		*Buying Computers with Intel ME disabled like [https://puri.sm/ Purism]<ref name=":1" /> and [https://system76.com/ System76]

	==See also==		==See also==

SquidthePlummer: cleaned things up and added a little bit more information and made corrections on some of the origional claims I've made

2026-02-04T02:59:44Z

cleaned things up and added a little bit more information and made corrections on some of the origional claims I've made

← Older revision		Revision as of 02:59, 4 February 2026
Line 21:		Line 21:
	==Intel AMT==		==Intel AMT==
	One of the services utilizing the capabilities of the Intel ME is '''Intel Active Management (AMT)'''. It is part of a set of technologies marketed as Intel vPro. Intel AMT is built into most modern Intel CPUs, including but not limited to the Intel Core i5, Intel Core i7, Intel Core M, and Intel Xeon series. The AMT has full access to the system and can bypass system firewalls<ref name=":6" /><ref>{{Cite web \|date=2021-01-05 \|title=Intel® Active Management Technology Developers Guide \|url=https://www.intel.com/content/www/us/en/docs/active-management-technology/developer-guide/2021/overview.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref>.		One of the services utilizing the capabilities of the Intel ME is '''Intel Active Management (AMT)'''. It is part of a set of technologies marketed as Intel vPro. Intel AMT is built into most modern Intel CPUs, including but not limited to the Intel Core i5, Intel Core i7, Intel Core M, and Intel Xeon series. The AMT has full access to the system and can bypass system firewalls<ref name=":6" /><ref>{{Cite web \|date=2021-01-05 \|title=Intel® Active Management Technology Developers Guide \|url=https://www.intel.com/content/www/us/en/docs/active-management-technology/developer-guide/2021/overview.html \|url-status=live \|access-date=2026-02-04 \|publisher=Intel}}</ref>.
			[[File:Intel ME boot sequence.png\|alt=Intel ME Boot Sequence for Laptops/Computers \|thumb\|Booting Process]]
	AMT allows remote management of the system by using the ME's network access, exposing 2 ports through which commands can be issued. Some of the many features of the AMT are:<ref name=":6" />		AMT allows remote management of the system by using the ME's network access, exposing 2 ports through which commands can be issued. Some of the many features of the AMT are:<ref name=":6" />

	* Access to hardware information		*Access to hardware information

	* Remote power control		*Remote power control
	* [https://software.intel.com/sites/manageability/HLAPI_Documentation/default.htm?turl=Documents%2Fbootcontrol.htm Boot control]		*[https://software.intel.com/sites/manageability/HLAPI_Documentation/default.htm?turl=Documents%2Fbootcontrol.htm Boot control]
	* Wake-on-LAN/Wake on wireless LAN		*Wake-on-LAN/Wake on wireless LAN
	* Remote Schedule Maintenance (outside firewall)		*Remote Schedule Maintenance (outside firewall)
	* KVM (keyboard, video, mouse) remote control		*KVM (keyboard, video, mouse) remote control
	* Updating firmware		*Updating firmware

	==Security==		==Security==
Line 43:		Line 43:
	\|2009		\|2009
	\|Developed by Invisible Things Lab, it was discovered that a bug allowed it to access the machine memory. <ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref><ref name=":0">{{Cite web \|first=402 Payment Required \|date=2023-06-29 \|title=Intel Management Engine \|url=https://www.youtube.com/watch?v=lQ8k79yNH2A \|url-status=live \|access-date=2026-02-03 \|website=Youtube}}</ref><ref name=":2">{{Cite web \|last=Robin \|first=Thibaud \|date=2025-03-02 \|title=The Mysterious Story of a Troubling Intel Chip \|url=https://blog.trackflaw.com/en/the-mysterious-story-of-a-disturbing-intel-flea/ \|url-status=live \|access-date=2026-02-03 \|website=TrackFlaw}}</ref>		\|Developed by Invisible Things Lab, it was discovered that a bug allowed it to access the machine memory. <ref>{{Cite web \|date=2008-08-26 \|title=Intel patches the Q35 bug \|url=https://theinvisiblethings.blogspot.com/2008/08/intel-patches-q35-bug.html \|url-status=live \|access-date=2026-02-03 \|website=The Invisible Things Lab's blog}}</ref><ref name=":0">{{Cite web \|first=402 Payment Required \|date=2023-06-29 \|title=Intel Management Engine \|url=https://www.youtube.com/watch?v=lQ8k79yNH2A \|url-status=live \|access-date=2026-02-03 \|website=Youtube}}</ref><ref name=":2">{{Cite web \|last=Robin \|first=Thibaud \|date=2025-03-02 \|title=The Mysterious Story of a Troubling Intel Chip \|url=https://blog.trackflaw.com/en/the-mysterious-story-of-a-disturbing-intel-flea/ \|url-status=live \|access-date=2026-02-03 \|website=TrackFlaw}}</ref>
	\|~~CVE-2008-1234~~		\|'''Can't Find'''
	\|-		\|-
	\|2010		\|2010
Line 80:		Line 80:
	==References==		==References==
	<references />		<references />

	~~https://www.youtube.com/watch?v=Lr-9aCMUXzI~~

	~~https://www.csoonline.com/article/562761/researchers-say-now-you-too-can-disable-intel-me-backdoor-thanks-to-the-nsa.html intel response to backdoor accusa~~

	~~https://www.youtube.com/watch?v=RPC5f7EJN6U~~

	<ref name=":1">{{Cite web \|last=Portnoy \|first=Erica \|last2=Eckersley \|first2=Peter \|date=2017-05-08 \|title=Intel's Management Engine is a security hazard, and users need a way to disable it \|url=https://www.eff.org/deeplinks/2017/05/intels-management-engine-security-hazard-and-users-need-way-disable-it \|url-status=live \|access-date=2026-02-03 \|website=Electronic Frontier Foundation}}</ref>
	~~https://leeneubecker.com/intels-secret-backdoor-can-now-be-turned-off/~~

	~~https://hackaday.com/2017/12/11/what-you-need-to-know-about-the-intel-management-engine/~~

	~~https://www.youtube.com/watch?v=ZpXkJqTAY5Y~~

	~~https://www.youtube.com/watch?v=lQ8k79yNH2A~~
	[[Category:{{PAGENAME}}]]		[[Category:{{PAGENAME}}]]

SquidthePlummer: somebody edited it before, however they did an amazing job and save me extra hours, thanks man!

2026-02-04T02:53:19Z

somebody edited it before, however they did an amazing job and save me extra hours, thanks man!

← Older revision		Revision as of 02:53, 4 February 2026
Line 16:		Line 16:
	The power state of the ME is independent from the rest of the system, allowing it to run while the system is turned off, assuming that the system is still receiving power.<ref name=":4" />		The power state of the ME is independent from the rest of the system, allowing it to run while the system is turned off, assuming that the system is still receiving power.<ref name=":4" />

			Additionally, Intel ME also contains several measures to check if it's been tampered with. Several of these measures conclude being inaccessible to the machine BIOS or chosen Operating System, scanning the entire machine every 30 minutes to verify if signature is signed or else the entire machine shutdown, and making it exceptionally difficult to reverse engineer.

	Additionally, Intel ME also contains several measures to check if it's been tampered with. These include being inaccessible to the machine BIOS or OS, scanning the entire machine every 30 minutes to verify if signature is signed (otherwise shutting down the system), and making it exceptionally difficult to reverse engineer.		Additionally, Intel ME also contains several measures to check if it's been tampered with. These include being inaccessible to the machine BIOS or OS, scanning the entire machine every 30 minutes to verify if signature is signed (otherwise shutting down the system), and making it exceptionally difficult to reverse engineer.
Line 34:		Line 35:
	==Security==		==Security==
	Intel ME follows security by obscurity, a concept that if people are unable to view the code, then it makes it more secure, however it's known to be ineffective and posing a huge security risks. Leaves many of these vulnerabilities unpatchable.		Intel ME follows security by obscurity, a concept that if people are unable to view the code, then it makes it more secure, however it's known to be ineffective and posing a huge security risks. Leaves many of these vulnerabilities unpatchable.

	~~https://www.youtube.com/watch?v=D9BBXBZ5Ifs showcase 1 (2007-09-20)~~

	~~https://www.youtube.com/watch?v=joeEBJeUfbk showcase 2 (both ysainthilaire~~
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 67:		Line 64:
	==Hidden Deals==		==Hidden Deals==
	Around 2017, an undocumented flag was discovered that, when set, disables a large portion of the ME. This feature appears to have been requested by the NSA.<ref name=":5" /><ref>{{Cite web \|last=Claburn \|first=Thomas \|date=29 Aug 2017 \|title=Intel ME controller chip has secret kill switch \|url=https://www.theregister.com/2017/08/29/intel_management_engine_can_be_disabled/ \|url-status=live \|access-date=2026-02-04 \|website=The Register}}</ref>		Around 2017, an undocumented flag was discovered that, when set, disables a large portion of the ME. This feature appears to have been requested by the NSA.<ref name=":5" /><ref>{{Cite web \|last=Claburn \|first=Thomas \|date=29 Aug 2017 \|title=Intel ME controller chip has secret kill switch \|url=https://www.theregister.com/2017/08/29/intel_management_engine_can_be_disabled/ \|url-status=live \|access-date=2026-02-04 \|website=The Register}}</ref>

	==Tools and Tips==		==Tools and Tips==

Line 97:		Line 95:

	https://www.youtube.com/watch?v=lQ8k79yNH2A		https://www.youtube.com/watch?v=lQ8k79yNH2A


	~~turn all the above links into references, though as of writing this i do not have will power to continue.~~
	[[Category:{{PAGENAME}}]]		[[Category:{{PAGENAME}}]]

2001:4C3C:F02:6E00:3106:192D:57B5:36D4: Added additional information about ME and AMT, removed some incomplete text.

2026-02-04T01:57:07Z

Added additional information about ME and AMT, removed some incomplete text.

Show changes