Vector35 / Vector35/binaryninja-api

It is possible to create variables that do not fit within section/segment bounds

Open
#3,741 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Core Effort: Trivial Impact: Low
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

  1. Go to the end of a section.
  2. Create a new array data variable that would obviously exceed the section end.
  3. Observe chaos.

This works with arrays as well integer types, etc. Presumably it also works with structures.

Before

image

After

image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing variable creation at the end of a section, then trace how section and segment bounds are checked for arrays and integer types; consider structures as another case. Done means variables that exceed their section or segment bounds are prevented or handled safely without causing chaos.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.