<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Beeldscherm</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Beeldscherm"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/Beeldscherm"/>
	<updated>2026-04-29T05:38:46Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=PHH_Mortgage_Corporation&amp;diff=36259</id>
		<title>PHH Mortgage Corporation</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=PHH_Mortgage_Corporation&amp;diff=36259"/>
		<updated>2026-02-05T18:25:30Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Modified a weirdly structured sentence&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{CompanyCargo&lt;br /&gt;
|Description=&lt;br /&gt;
|Founded=2008&lt;br /&gt;
|Industry=Finance&lt;br /&gt;
|Logo=PHH-Mortgage.png&lt;br /&gt;
|ParentCompany=&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Website=https://www.phhmortgage.com/&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;&#039;PHH Mortgage Corporation&#039;&#039;&#039; is a subsidiary of Onity Group, Inc., a privately held mortgage servicer and lender based in Florida. As of June 10, 2024, Onity Mortgage has been established as a DBA (Doing Business As) of PHH Mortgage.&amp;lt;ref&amp;gt;https://business.phhmortgage.com/BusinessPHH/media/BusinessPHH/Pdf/PHH_Onity-FAQs.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:OnityGroupCompanyTree PHHMortgageCorporation V1.png|alt=Tree describing company relationships under the Onity Group, highlighting PHH Mortgage Corporation in light blue|thumb|549x549px|PHH Mortgage Corporation structure according to SEC filings.&amp;lt;ref&amp;gt;{{Cite web |date=27 Nov 2024 |title=ONITY GROUP INC. 8-K |url=https://www.sec.gov/Archives/edgar/data/873860/000149315224048499/ex10-2.htm |access-date=7 Mar 2024 |website=Securities and Exchange Commission}}&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
PHH Mortgage Corporation, a non-bank residential mortgage servicer, has faced multiple allegations related to improper loan servicing practices, impacting borrowers across the United States. The company has been accused of failing to properly apply borrower payments, charging unauthorized fees, and mishandling loan modification requests. In some cases, PHH provided misleading information to homeowners facing foreclosure, and in others, it failed to maintain accurate records or oversee third-party vendors involved in servicing and foreclosure processes.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These practices have led to financial hardship for many homeowners, with some experiencing delays or miscommunications that resulted in foreclosures or loss of modification opportunities.&amp;lt;ref&amp;gt;https://www.nj.gov/oag/newsreleases18/PHH_Complaint-for-filing-v1.pdf&amp;lt;/ref&amp;gt; In response to these allegations, PHH has reached settlements, including restitution for affected borrowers and commitments to adopt improved servicing standards.&amp;lt;ref&amp;gt;https://www.nj.gov/oag/newsreleases18/PHH_Consent-Judgment.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
&lt;br /&gt;
===$6.25 Million Consumer Fraud Act Settlement (&#039;&#039;2011&#039;&#039;)===&lt;br /&gt;
In a settlement announced by Acting Attorney General John J. Hoffman,&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=John |date=4 Dec 2013 |title=Acting Attorney General Announces $6.25 Million Settlement Resolving Consumer Fraud Act Allegations Against PHH Mortgage |url=https://nj.gov/oag/newsreleases13/pr20131204a.html |access-date=7 Mar 2025 |website=The State of New Jersey Office of Attorney General}},&amp;lt;/ref&amp;gt; New Jersey reached a $6.25 million agreement with PHH Mortgage Corporation to resolve allegations that the company misled financially struggling homeowners seeking loan modifications or assistance to avoid foreclosure.&lt;br /&gt;
&lt;br /&gt;
===$45 Million Multi-State Settlement (&#039;&#039;2018&#039;&#039;)===&lt;br /&gt;
In a multi-state settlement announced by Attorney General Christopher S. Porrino,&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Porrino |first=Christopher |date=3 Jan 2018 |title=Attorney General Porrino Announces $45 Million Multi-State Settlement with PHH Mortgage Corporation |url=https://www.nj.gov/oag/newsreleases18/pr20180103b.html |access-date=7 Mar 2025}},&amp;lt;/ref&amp;gt; New Jersey reached a $45 million agreement with PHH Mortgage Corporation to resolve allegations of improper mortgage loan servicing. The settlement, which includes more than 45 states and the District of Columbia, addresses claims that PHH Mortgage failed to properly service loans over a four-year period.&lt;br /&gt;
&lt;br /&gt;
Between January 1, 2009, and December 31, 2012, PHH Mortgage Corporation was accused of engaging in improper mortgage servicing practices. The alleged improper mortgage servicing practices include:&lt;br /&gt;
&lt;br /&gt;
*Misapplying borrower payments and maintaining inaccurate account statements.&lt;br /&gt;
*Charging unauthorized fees for default-related services.&lt;br /&gt;
*Providing conflicting and misleading information to borrowers facing foreclosure.&lt;br /&gt;
*Failing to respond adequately to borrower complaints and loan modification requests.&lt;br /&gt;
*Mishandling loss mitigation applications and documentation.&lt;br /&gt;
*Lacking proper loan servicing records and foreclosure documentation.&lt;br /&gt;
*Inadequately supervising third-party vendors involved in servicing and foreclosure.&lt;br /&gt;
*Submitting foreclosure documents with inaccurate or incomplete information.&lt;br /&gt;
*Using improperly executed affidavits in foreclosure proceedings.&lt;br /&gt;
*Lacking a structured process for document preparation, execution, and notarization in foreclosure cases.&lt;br /&gt;
&lt;br /&gt;
===Mortgage Service Center===&lt;br /&gt;
Mortgage Service Center is a registered DBA of PHH Mortgage Corporation,&amp;lt;ref&amp;gt;https://mblsportal.sos.state.mn.us/Business/SearchDetails?filingGuid=b9c14d71-c21d-ea11-918b-00155d01b4fc&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://extranet.dfi.in.gov/ConsumerCredit/EntityDetails/2881&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;https://licensing.coag.gov/s/license-report/a1mcs000001xAl2AAE/sup4000219005&amp;lt;/ref&amp;gt; and engages in direct marketing by utilizing publicly available county records, including property details such as closing dates, loan amounts, lender names, mortgagor names, and addresses, to contact new homeowners with mortgage-related offers.&lt;br /&gt;
&lt;br /&gt;
By referencing details related to a homeowner&#039;s recent mortgage, Mortgage Service Center aims to establish credibility and engage potential customers.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=User:Beeldscherm&amp;diff=36129</id>
		<title>User:Beeldscherm</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=User:Beeldscherm&amp;diff=36129"/>
		<updated>2026-02-04T19:15:31Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Information&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;likes: Linux&lt;br /&gt;
&lt;br /&gt;
dislikes: AI&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=AMD_Platform_Security_Processor&amp;diff=36127</id>
		<title>AMD Platform Security Processor</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=AMD_Platform_Security_Processor&amp;diff=36127"/>
		<updated>2026-02-04T19:08:06Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Added to concerns and vulnerabilities sections.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductCargo&lt;br /&gt;
|Company=AMD&lt;br /&gt;
|ReleaseYear=2013&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Surveillance, Security, Hardware, Computers, Firmware&lt;br /&gt;
|Description=An autonomous chip running closed-source code with full system access, found on most AMD platforms.&lt;br /&gt;
|Logo=AMD logo.svg|Website=https://www.amd.com/en.html}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;[[AMD]] Platform Security Processor (PSP)&#039;&#039;&#039;, also known as the &#039;&#039;&#039;AMD Secure Processor&#039;&#039;&#039;, is an autonomous processor embedded on most modern AMD CPU&#039;s since 2013. The PSP has full access to memory and is capable of running without the main CPU cores being active.&amp;lt;ref&amp;gt;{{Cite web |last=Eichner |first=Alexander |last2=Buhren |first2=Robert |date=2020-08-05 |title=All you ever wanted to know about the AMD Platform Security Processor and were afraid to emulate |url=https://i.blackhat.com/USA-20/Wednesday/us-20-Buhren-All-You-Ever-Wanted-To-Know-About-The-AMD-Platform-Security-Processor-And-Were-Afraid-To-Emulate.pdf |url-status=live |access-date=2026-02-04 |website=blackhat.com}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
AMD has not provided much information about the PSP, but several features are know, including:&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |date=2023-04-17 |title=Reversing the AMD Secure Processor (PSP) |url=https://dayzerosec.com/blog/2023/04/17/reversing-the-amd-secure-processor-psp.html |url-status=live |archive-url=https://web.archive.org/web/20260112172321/https://dayzerosec.com/blog/2023/04/17/reversing-the-amd-secure-processor-psp.html |archive-date=2026-01-12 |access-date=2026-02-04 |website=dayzerosec.com}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*CPU initialization&lt;br /&gt;
*Hardware-accelerated cryptography&lt;br /&gt;
*Hardware/software integrity verification ([[wikipedia:Trusted_Platform_Module|TPM]])&lt;br /&gt;
*Facilitating Secure Encrypted Virtualization ([https://www.amd.com/en/developer/sev.html SEV])&lt;br /&gt;
There is no official way of disabling the PSP. Since it has responsibilities during the boot sequence, it is likely to be impossible to remove the PSP entirely without breaking the system.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; Around 2018, some users reported seeing a BIOS option to disable the PSP. &amp;lt;ref&amp;gt;{{Cite web |last=Cimpanu |first=Catalin |date=2018-01-06 |title=Security Flaw in AMD&#039;s Secure Chip-On-Chip Processor Disclosed Online |url=https://www.bleepingcomputer.com/news/security/security-flaw-in-amds-secure-chip-on-chip-processor-disclosed-online/ |url-status=live |archive-url=https://web.archive.org/web/20251219104119/https://www.bleepingcomputer.com/news/security/security-flaw-in-amds-secure-chip-on-chip-processor-disclosed-online/ |archive-date=2025-12-19 |access-date=2026-02-04 |website=BleepingComputer}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Concerns==&lt;br /&gt;
AMD has denied requests to open-source the software running on the PSP.&amp;lt;ref&amp;gt;{{Cite web |last=Williams |first=Rob |date=19 Jul 2017 |title=AMD Confirms It Won&#039;t Opensource EPYC&#039;s Platform Security Processor Code |url=https://hothardware.com/news/amd-confirms-it-will-not-be-opensourcing-epycs-platform-security-processor-code |url-status=live |archive-url=https://web.archive.org/web/20251123014437/https://hothardware.com/news/amd-confirms-it-will-not-be-opensourcing-epycs-platform-security-processor-code |archive-date=2025-11-23 |access-date=2026-02-04 |website=HotHardware}}&amp;lt;/ref&amp;gt; This means that the inner workings of the PSP cannot be independently verified and bug-fixing can only be performed by AMD. This is an example of [[Security through obscurity|&amp;quot;security through obscurity&amp;quot;]], which has been criticized for taking away consumer rights.&lt;br /&gt;
&lt;br /&gt;
Some have accused the AMD PSP of having a backdoor because of its closed nature, full system access, and AMD&#039;s secrecy and unwillingness to make the code public.&amp;lt;ref&amp;gt;{{Cite web |date=15 Mar 2021 |title=Every modern computer has a backdoor |url=https://www.sysjolt.com/2021/every-modern-computer-has-a-backdoor/ |url-status=live |access-date=2026-02-04 |website=sysjolt.com}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vulnerabilities==&lt;br /&gt;
There have been several vulnerabilities related to AMD&#039;s PSP.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!Date&lt;br /&gt;
!Vulnerability&lt;br /&gt;
!CVE&lt;br /&gt;
|-&lt;br /&gt;
|2020&lt;br /&gt;
|Incorrect BIOS image length validation by the PSP might cause arbitrary code execution.&lt;br /&gt;
|[https://nvd.nist.gov/vuln/detail/CVE-2020-12944 CVE-2020-12944]&lt;br /&gt;
|-&lt;br /&gt;
|2020&lt;br /&gt;
|Due to a vulnerability in the PSP, an attacker can modify registers and possibly bypass ROM protections.&lt;br /&gt;
|[https://nvd.nist.gov/vuln/detail/CVE-2020-12961 CVE-2020-12961]&lt;br /&gt;
|-&lt;br /&gt;
|2021&lt;br /&gt;
|Insufficient verification of image decrypted by PSP may lead to arbitrary code execution.&lt;br /&gt;
|[https://nvd.nist.gov/vuln/detail/CVE-2021-26315 CVE-2021-26315]&lt;br /&gt;
|-&lt;br /&gt;
|2021&lt;br /&gt;
|Using the PSP, low-privilege users are able to send driver requests, allowing data leakage.&lt;br /&gt;
|[https://nvd.nist.gov/vuln/detail/CVE-2021-26333 CVE-2021-26333]&lt;br /&gt;
|-&lt;br /&gt;
|2021&lt;br /&gt;
|Insufficient address validation in PSP firmware may lead to arbitrary code execution.&lt;br /&gt;
|[https://nvd.nist.gov/vuln/detail/CVE-2021-46771 CVE-2021-46771]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[AMD]]&lt;br /&gt;
*[[Intel Management Engine]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;br /&gt;
[[Category:AMD]]&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=AMD_Platform_Security_Processor&amp;diff=36121</id>
		<title>AMD Platform Security Processor</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=AMD_Platform_Security_Processor&amp;diff=36121"/>
		<updated>2026-02-04T18:31:51Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Added information and concerns.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductCargo&lt;br /&gt;
|Company=AMD&lt;br /&gt;
|ReleaseYear=2013&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Surveillance, Security, Hardware, Computers, Firmware&lt;br /&gt;
|Description=An autonomous chip running closed-source code with full system access, found on most AMD platforms.&lt;br /&gt;
|Logo=AMD logo.svg|Website=https://www.amd.com/en.html}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;AMD Platform Security Processor (PSP)&#039;&#039;&#039;, also known as the &#039;&#039;&#039;AMD Secure Processor&#039;&#039;&#039;, is an autonomous processor embedded on most modern AMD CPU&#039;s since 2013. The PSP has full access to memory and is capable of running without the main CPU cores being active.&amp;lt;ref&amp;gt;{{Cite web |last=Eichner |first=Alexander |last2=Buhren |first2=Robert |date=2020-08-05 |title=All you ever wanted to know about the AMD Platform Security Processor and were afraid to emulate |url=https://i.blackhat.com/USA-20/Wednesday/us-20-Buhren-All-You-Ever-Wanted-To-Know-About-The-AMD-Platform-Security-Processor-And-Were-Afraid-To-Emulate.pdf |url-status=live |access-date=2026-02-04 |website=blackhat.com}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
AMD has not provided much information about the PSP, but several features are know, including:&amp;lt;ref&amp;gt;{{Cite web |date=2023-04-17 |title=Reversing the AMD Secure Processor (PSP) |url=https://dayzerosec.com/blog/2023/04/17/reversing-the-amd-secure-processor-psp.html |url-status=live |archive-url=https://web.archive.org/web/20260112172321/https://dayzerosec.com/blog/2023/04/17/reversing-the-amd-secure-processor-psp.html |archive-date=2026-01-12 |access-date=2026-02-04 |website=dayzerosec.com}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* CPU initialization&lt;br /&gt;
* Hardware-accelerated cryptography&lt;br /&gt;
* Hardware/software integrity verification ([[wikipedia:Trusted_Platform_Module|TPM]])&lt;br /&gt;
* Facilitating Secure Encrypted Virtualization ([https://www.amd.com/en/developer/sev.html SEV])&lt;br /&gt;
&lt;br /&gt;
==Concerns==&lt;br /&gt;
AMD has denied requests to open-source the software running on the PSP.&amp;lt;ref&amp;gt;{{Cite web |last=Williams |first=Rob |date=19 Jul 2017 |title=AMD Confirms It Won&#039;t Opensource EPYC&#039;s Platform Security Processor Code |url=https://hothardware.com/news/amd-confirms-it-will-not-be-opensourcing-epycs-platform-security-processor-code |url-status=live |archive-url=https://web.archive.org/web/20251123014437/https://hothardware.com/news/amd-confirms-it-will-not-be-opensourcing-epycs-platform-security-processor-code |archive-date=2025-11-23 |access-date=2026-02-04 |website=HotHardware}}&amp;lt;/ref&amp;gt; This means that the inner workings of the PSP cannot be independently verified and bugfixes can only be performed by AMD. This is an example of [[Security through obscurity|&amp;quot;security through obscurity&amp;quot;]], which has been criticized for taking away consumer rights.&lt;br /&gt;
&lt;br /&gt;
==Vulnerabilities==&lt;br /&gt;
{{Ph-C-Inc}}&#039;&#039;&#039;[Placeholder]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* [[AMD]]&lt;br /&gt;
* [[Intel Management Engine]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;br /&gt;
[[Category:AMD]]&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=AMD_Platform_Security_Processor&amp;diff=36113</id>
		<title>AMD Platform Security Processor</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=AMD_Platform_Security_Processor&amp;diff=36113"/>
		<updated>2026-02-04T17:46:27Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Created page for AMD PSP&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ProductCargo&lt;br /&gt;
|Company=AMD&lt;br /&gt;
|ReleaseYear=2013&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Surveillance, Security, Hardware, Computers, Firmware&lt;br /&gt;
|Description=An autonomous chip running closed-source code with full system access, found on most AMD platforms.&lt;br /&gt;
}}&lt;br /&gt;
{{Ph-C-Int}}&lt;br /&gt;
&lt;br /&gt;
==Consumer-impact summary==&lt;br /&gt;
{{Ph-C-CIS}}&lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
{{Ph-C-Inc}}&lt;br /&gt;
This is a list of all consumer-protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===Example incident one (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
{{Main|link to the main CR Wiki article}}&lt;br /&gt;
Short summary of the incident (could be the same as the summary preceding the article).&lt;br /&gt;
===Example incident two (&#039;&#039;date&#039;&#039;)===&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
{{Ph-C-SA}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Intel_Management_Engine&amp;diff=36103</id>
		<title>Intel Management Engine</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Intel_Management_Engine&amp;diff=36103"/>
		<updated>2026-02-04T16:24:41Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Added and modified some sources&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete section}}{{StubNotice}}{{ProductCargo&lt;br /&gt;
|Company=Intel&lt;br /&gt;
|ProductLine=Intel Management Engine&lt;br /&gt;
|ReleaseYear=2008&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Service&lt;br /&gt;
|Category=Surveillance, Security, Computers, Articles in Need of Additional Work&lt;br /&gt;
|Website=https://www.intel.com/content/www/us/en/homepage.html&lt;br /&gt;
|Description=An autonomous embedded microcontroller present on Intel chipsets with root system access.&lt;br /&gt;
|Logo=Intel logo.svg}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Intel Management Engine (ME)&#039;&#039;&#039; is an embedded microcontroller integrated into Intel&#039;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.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Additionally, Intel ME also contains several measures to check if it&#039;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)&amp;lt;sup&amp;gt;[source?]&amp;lt;/sup&amp;gt;, and making it exceptionally difficult to reverse engineer.&lt;br /&gt;
==Intel AMT==&lt;br /&gt;
One of the services utilizing the capabilities of the Intel ME is &#039;&#039;&#039;Intel Active Management (AMT)&#039;&#039;&#039;. 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.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt; By default, AMT is enabled, on supported chips. AMT support is listed under the &amp;quot;Security &amp;amp; Reliability&amp;quot; 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]).&lt;br /&gt;
[[File:Intel ME boot sequence.png|alt=Intel ME Boot Sequence for Laptops/Computers |thumb|Booting Process]]&lt;br /&gt;
AMT allows remote management of the system by using the ME&#039;s network access, exposing 2 ports through which commands can be issued. Some of the many features of the AMT are:&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Access to hardware information&lt;br /&gt;
&lt;br /&gt;
*Remote power control&lt;br /&gt;
*[https://software.intel.com/sites/manageability/HLAPI_Documentation/default.htm?turl=Documents%2Fbootcontrol.htm Boot control]&lt;br /&gt;
*Wake-on-LAN/Wake on wireless LAN&lt;br /&gt;
*Remote Schedule Maintenance (outside firewall)&lt;br /&gt;
*KVM (keyboard, video, mouse) remote control&lt;br /&gt;
*Updating firmware&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
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&#039;s  known to be ineffective and posing a huge security risks. Leaves many of these vulnerabilities unpatchable.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
|Date&lt;br /&gt;
|Description&lt;br /&gt;
|CVE&lt;br /&gt;
|-&lt;br /&gt;
|2009&lt;br /&gt;
|A &amp;quot;Ring -3 Rootkit&amp;quot; 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.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt; The bug was subsequently patched by Intel.&amp;lt;ref&amp;gt;{{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&#039;s blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|&#039;&#039;&#039;No CVE&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|2010&lt;br /&gt;
|An individual by the name of Vassilios Vereris discovered an bypass that allow attackers to remotely enable Intel AMT.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Ververis |first=Vassilios |year=2010 |title=Security Evaluation of Intel&#039;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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|&#039;&#039;&#039;No CVE&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|2017&lt;br /&gt;
|Discovered by Maksim Malyutin from Embedi, a bug in Intel AMT allows a hacker to gain admin privileges from a remote location.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; 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.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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&#039;s Hardware}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|CVE-2017-5689.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|2018&lt;br /&gt;
|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.&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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&#039;s Hardware}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|&#039;&#039;&#039;No CVE&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|2020&lt;br /&gt;
|Several vulnerabilities were found in Intel AMT, allowing hackers to add a root kit.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Larabe |first=Michael |date=2020-09-08 |title=Intel AMT Hit By Another &amp;quot;Critical&amp;quot; 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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|CVE 2020-0535&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Hidden Deals==&lt;br /&gt;
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.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
==Tools and Tips==&lt;br /&gt;
&lt;br /&gt;
There is no official method to disable the ME, however there have been tools and tips developed to allow (partially) disabling the ME.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |title=Intel’s Management Engine |url=https://puri.sm/learn/intel-me/ |url-status=live |access-date=2026-02-04 |publisher=Purism}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[https://github.com/corna/me_cleaner ME Cleaner Tool]&lt;br /&gt;
*Using an CPU or Computer made before 2008&lt;br /&gt;
*Buying Computers with Intel ME disabled like [https://puri.sm/ Purism]&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; and [https://system76.com/ System76]&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Intel]]&lt;br /&gt;
*[[Intel CPUs stability issue]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Intel_Management_Engine&amp;diff=36101</id>
		<title>Intel Management Engine</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Intel_Management_Engine&amp;diff=36101"/>
		<updated>2026-02-04T15:46:46Z</updated>

		<summary type="html">&lt;p&gt;Beeldscherm: Some additional information on AMT and the 2009 vulnerability, also fixed small mistakes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete section}}{{StubNotice}}{{ProductCargo&lt;br /&gt;
|Company=Intel&lt;br /&gt;
|ProductLine=Intel Management Engine&lt;br /&gt;
|ReleaseYear=2008&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Service&lt;br /&gt;
|Category=Surveillance, Security, Computers, Articles in Need of Additional Work&lt;br /&gt;
|Website=https://www.intel.com/content/www/us/en/homepage.html&lt;br /&gt;
|Description=An autonomous embedded microcontroller present on Intel chipsets with root system access.&lt;br /&gt;
|Logo=Intel logo.svg}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Intel Management Engine (ME)&#039;&#039;&#039; is an embedded microcontroller integrated into Intel&#039;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.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:5&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The ME is able to access the LAN adapter, giving it access to networks the system is connected to, both wired and wireless.&amp;lt;ref name=&amp;quot;:6&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Additionally, Intel ME also contains several measures to check if it&#039;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)&amp;lt;sup&amp;gt;[source?]&amp;lt;/sup&amp;gt;, and making it exceptionally difficult to reverse engineer.&lt;br /&gt;
==Intel AMT==&lt;br /&gt;
One of the services utilizing the capabilities of the Intel ME is &#039;&#039;&#039;Intel Active Management (AMT)&#039;&#039;&#039;. 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.&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt; By default, AMT is enabled, on supported chips. AMT support is listed under the &amp;quot;Security &amp;amp; Reliability&amp;quot; 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]).&lt;br /&gt;
[[File:Intel ME boot sequence.png|alt=Intel ME Boot Sequence for Laptops/Computers |thumb|Booting Process]]&lt;br /&gt;
AMT allows remote management of the system by using the ME&#039;s network access, exposing 2 ports through which commands can be issued. Some of the many features of the AMT are:&amp;lt;ref name=&amp;quot;:6&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Access to hardware information&lt;br /&gt;
&lt;br /&gt;
*Remote power control&lt;br /&gt;
*[https://software.intel.com/sites/manageability/HLAPI_Documentation/default.htm?turl=Documents%2Fbootcontrol.htm Boot control]&lt;br /&gt;
*Wake-on-LAN/Wake on wireless LAN&lt;br /&gt;
*Remote Schedule Maintenance (outside firewall)&lt;br /&gt;
*KVM (keyboard, video, mouse) remote control&lt;br /&gt;
*Updating firmware&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
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&#039;s  known to be ineffective and posing a huge security risks. Leaves many of these vulnerabilities unpatchable.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
|Date&lt;br /&gt;
|Description&lt;br /&gt;
|CVE&lt;br /&gt;
|-&lt;br /&gt;
|2009&lt;br /&gt;
|A &amp;quot;Ring -3 Rootkit&amp;quot; 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.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt; The bug was subsequently patched by Intel.&amp;lt;ref&amp;gt;{{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&#039;s blog}}&amp;lt;/ref&amp;gt; &amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|&#039;&#039;&#039;No CVE&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|2010&lt;br /&gt;
|An individual by the name of Vassilios Vereris discovered an bypass that allow attackers to remotely enable Intel AMT.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Ververis |first=Vassilios |year=2010 |title=Security Evaluation of Intel&#039;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}}&amp;lt;/ref&amp;gt; &amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;:2&amp;quot; /&amp;gt;&lt;br /&gt;
|&#039;&#039;&#039;No CVE&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|2017&lt;br /&gt;
|Discovered by Maksim Malyutin from Embedi, a bug in Intel AMT allows a hacker to gain admin privileges from a remote location.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; 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.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt; &amp;lt;ref&amp;gt;{{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&#039;s Hardware}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt;&lt;br /&gt;
|CVE-2017-5689.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|2018&lt;br /&gt;
|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. &amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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&#039;s Hardware}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|&#039;&#039;&#039;No CVE&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|2020&lt;br /&gt;
|Several vulnerabilities were found in Intel AMT, allowing hackers to add a root kit.&amp;lt;ref name=&amp;quot;:3&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Larabe |first=Michael |date=2020-09-08 |title=Intel AMT Hit By Another &amp;quot;Critical&amp;quot; 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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|CVE 2020-0535&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Hidden Deals==&lt;br /&gt;
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.&amp;lt;ref name=&amp;quot;:5&amp;quot; /&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
==Tools and Tips==&lt;br /&gt;
&lt;br /&gt;
There is no official method to disable the ME, however there have been tools and tips developed to allow (partially) disabling the ME.&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |title=Intel’s Management Engine |url=https://puri.sm/learn/intel-me/ |url-status=live |access-date=2026-02-04 |publisher=Purism}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[https://github.com/corna/me_cleaner ME Cleaner Tool]&lt;br /&gt;
*Using an CPU or Computer made before 2008&lt;br /&gt;
*Buying Computers with Intel ME disabled like [https://puri.sm/ Purism]&amp;lt;ref name=&amp;quot;:1&amp;quot; /&amp;gt; and [https://system76.com/ System76]&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Intel]]&lt;br /&gt;
*[[Intel CPUs stability issue]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Beeldscherm</name></author>
	</entry>
</feed>