Add TPM 2.0
10
TPM-2.0.md
Normal file
10
TPM-2.0.md
Normal file
@@ -0,0 +1,10 @@
|
|||||||
|
TPM 2.0 is not generally "compromised" or broken, but it is not infallible. While no widespread remote exploits exist, vulnerabilities (like the 2023
|
||||||
|
[CryptParameterDecryption](https://www.google.com/search?q=CryptParameterDecryption&ved=2ahUKEwitiMLF0eCSAxVmElkFHW1aBAMQgK4QegQIARAB) issue) allow for specific, localized memory corruption. Physical attacks, such as intercepting data on the bus between the CPU and discrete TPM, can expose keys.
|
||||||
|
Key Aspects of TPM 2.0 Security:
|
||||||
|
|
||||||
|
Vulnerabilities: Researchers have identified potential out-of-bounds read vulnerabilities in the TPM 2.0 library specification.
|
||||||
|
Physical Attack Vector: Attacks against the physical LPC or SPI bus connecting a discrete TPM to the motherboard can bypass protections to read data like encryption keys.
|
||||||
|
Mitigation: Software updates from vendors (BIOS/firmware updates) are used to address identified vulnerabilities in the specification.
|
||||||
|
Best Practices: For high-security needs, TPM 2.0 is often paired with user authentication (PIN/password) to prevent automatic key loading.
|
||||||
|
|
||||||
|
While TPM 2.0 remains a critical component of modern security, it is just one layer of a secure system.
|
||||||
Reference in New Issue
Block a user