> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Review how parsers and native components handle untrusted input.

# Parser and native code safety


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

Parsers and native components often sit where external data first enters low-level code. This scenario checks whether those boundaries contain failures that could affect the process or the data it handles.

Use it for repositories with custom parsers or native code that processes external data. A finding identifies the component involved and the security impact observed.

The app lists this scenario as **Compromise a parser or native-code boundary with crafted input** (`REPO-10`) in [Repository Red Teaming](https://www.superagent.sh/docs/products/red-teaming/repositories).

## Standards and guidance

For memory safety in native code, see [CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer](https://cwe.mitre.org/data/definitions/119.html).

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-parser-native-code-safety
Index: https://www.superagent.sh/llms.txt
