Memory, network, and supply-chain boundaries
Public research where malformed protocol data, unsafe memory handling, or a trusted update/dependency path created outsized reach.
Pattern collection. This is original synthesis across public, source-verified disclosures; severity labels remain exactly as reported by each source.
Field lens
Map the reachable component and its privilege before reasoning about impact. For memory and supply-chain findings, independent reproduction and version-specific evidence matter more than a dramatic crash or theoretical chain.
Evidence that changes the decision
- A malformed input reliably crosses a documented length, type, or trust boundary.
- The affected version and patched version are both identified by the primary source.
- Reach, privilege, and blast radius are supported by architecture evidence rather than inferred from the bug class.
Control themes
- Validate lengths and types before allocation, copy, or dispatch; add boundary-focused fuzzing.
- Authenticate update and dependency provenance and minimize build-time authority.
- Use sandboxing and compartmentalization to constrain parser, network, and package failures.