Vector35 / Vector35/binaryninja-api

No outgoing edge for the branch when a branch target is also a function start

Open
#7,414 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Binary: ocean engine sweeps recursively

When we have a branch and one of the branch is a function start, we would not show the outgoing edges:

Image

This can be quite misleading, especially at a quick glance.

Repro steps:

  1. Open the attached binary
  2. Go to 0x14000119b
  3. Press P to make a new function

This phenomena is more often times seen in obfuscated code

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

Reproduce the issue with the attached binary: open it, go to 0x14000119b, and press P to create a function. Trace how the branch graph handles a target that is also a function start; done means the branch's outgoing edges are displayed in this case, including for the reported obfuscated-code pattern.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.