Zynq: Use after free in DisplayAuthenicationCertificates
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 64
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
The header authentication certificate is pushed into aCs, then freed before it is displayed.
https://github.com/Xilinx/bootgen/blob/0e336a00dcff5842648f4a1e9f919abf7c960d97/zynq/src/readimage-zynq.cpp#L264-L278
https://github.com/Xilinx/bootgen/blob/0e336a00dcff5842648f4a1e9f919abf7c960d97/zynq/src/readimage-zynq.cpp#L300-L303
Contributor guide
No contributing guide indexed for this repository
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 in zynq/src/readimage-zynq.cpp at DisplayAuthenicationCertificates and inspect the certificate handling at the linked lines 264-278 and 300-303. Trace when the header certificate is added to aCs and freed; done means the display path no longer accesses freed certificate data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100