Firmware

Structure, crypto, unpack boundaries, IPC

🌱 This series follows firmware work in three aspects: 🔭 Obtain the system to analyze: unpack, recover, and reach a filesystem or binary set worth studying when vendors make that hard. 🔭 Map the attack surface: e.g. exposed services, update paths, IPC interfaces, trust boundaries — what can be reached before talking about impact. 🔭 Vulnerability research and PoC: turn that surface into issues and, where appropriate, constrained proofs; public notes here stay careful and sanitized.

I would like provide interesting findings about firmware analysis to the community.

Briefs

No briefs yet.

Analysis

No analysis posts yet.