TPM PCR rewrites might fail to badfet attacks
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
The TPM libraries don't necessarily make sure that the values written to the PCRs are correctly recorded. A potential vulnerability exists if a badfet style device can interfere with the low-speed LPC bus. One approach is to read the values back and ensure that they match the expected value, although this is still potentially vulnerable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TPM libraries and the code paths that write PCR values, then review how an LPC-bus device could interfere with those writes. Determine whether read-back verification is sufficient and define a test or other evidence showing that PCR values are correctly recorded despite the described attack.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100