BUG BOUNTYFIELD MANUAL
Vulnerability reference
Markdown
0 / 5 checkedChecks last until this page reloads.

Out-of-bounds memory read

A parser or native consumer reads outside the valid extent of an object or buffer, potentially causing a crash or disclosure depending on how the result is used.

Candidate CWE: CWE-125

Test hypothesis#

Build the real parser with AddressSanitizer, provide realistic byte input through its public API, and minimize a reproducible failure. Verify lengths and object ownership in the harness. Check a supported consumer separately; prove returned adjacent synthetic data if claiming disclosure.

Evidence required#

Minimal input and hash, revision, compiler flags, symbolized read/allocation trace, relevant sizes, and supported API invocation. A crashing read does not by itself prove information disclosure.

Rule out false positives#

Harness passes an incorrect size or invalid pointer contrary to the API contract; fault occurs only in test scaffolding; or an ordinary bounds-checked error is mistaken for a memory access.

Playbook and command references#

Find the associated command snippets

Referenced by these target playbooks#

Report checklist#

  • Capture the affected version, configuration, identities, and object ownership.
  • Preserve a valid baseline and a negative control.
  • Reproduce the forbidden data access, action, or state change on controlled fixtures.
  • Explain the intended security rule and why the observed behavior violates it.
  • State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

Conditional ATT&CK mapping#

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.

Primary references#

Back to the complete vulnerability catalog