---
name: validate-memory-corruption
description: Evidence bar and stage classification for memory corruption in native code, from a reproducible fault to sandbox escape. Use when validating a finding that claims a crash, overflow, use-after-free or other native-parser bug.
---

# Validate memory corruption

- Identify the evidenced product build, affected component, platform and relevant mitigations; make assumptions about the deployed environment explicit.
- Classify the strongest demonstrated stage precisely: reproducible fault, controlled disclosure, controlled read, controlled write, instruction-pointer or native control, native execution inside the current sandbox, or sandbox escape and host execution. Never label a crash, sanitiser trace, or controlled pointer as RCE.
- Do not repeatedly exercise an unstable production payload or require sandbox escape to validate a demonstrated memory-corruption issue.