MemoryMap UI fails to find malformed section names when attempting to open the context menu

Open
#8,251 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
desktop, reverse-engineering

Research direction

Reproduce the issue with a malformed binary, then trace the MemoryMap sidebar or Pane UI view's context-menu handling and the log error when locating the section name. The work is done when right-clicking a malformed section opens editing for its attributes without requiring Python API changes.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

  • Binary Ninja Version: 5.4.9784-dev personal
  • Edition: Non-Commercial
  • OS: Arch Ubuntu Linux
  • OS Version: 7.0.11-arch1-1
  • CPU Architecture: x64

Bug Description:
Please provide a clear and concise description of what happened.

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open a malformed binary with invalid section names
  2. Try to use the MemoryMap sidebar or Pane UI view to edit the section by right clicking
  3. Log output shows an error finding the section name. I was able to use the python API to view the section information, remove the auto sections, and add new user defines ones.

Expected Behavior:
Would like to be able to use the context menu to edit the section attributes when malformed binaries use custom/invalid section names

Screenshots/Video Recording:
Image

Let me know if more information or the binary is needed

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

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.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.