Binary Ninja marks .efi file as modified with no user action
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- desktop, reverse-engineering
Research direction
No source file or test is named. First reproduce the issue with the attached efi_files.zip on the listed platforms and versions, then trace how opening and analyzing an EFI file marks the database dirty. Done means an untouched .efi file does not show as modified and closing it does not prompt to save.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 5.3 and 6.1.10594
- Edition: Ultimate
- OS: macOS, Windows 11
- OS Version: macOS Tahoe 26.5.2, Win11 10.0.26200 N/A Build 26200
- CPU Architecture: x64
Bug Description:
After opening a .efi file and performing no actions on it, Binary Ninja indicates that the analysis database has been modified (a dot appears next to the file name in the tab). Closing the file then prompts a save dialog, even though no changes were made by the user.
This has been observed across versions 5.3 and 6.1.10594, and reproduced on both macOS and Windows 11.
Steps To Reproduce:
- Open a .efi file in Binary Ninja
- Perform no actions on the file
- Observe that the tab shows a dot next to the file name, indicating the analysis database has been modified
- Close the file
- Observe that a save prompt dialog appears
Binary:
efi_files.zip
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 20
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Vector35/binaryninja-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8540 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8446 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8444 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Vector35/binaryninja-api#8441 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Vector35/binaryninja-api#8404 ·
All issues in Vector35/binaryninja-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·