Ghidra: backend may identify functions as labels
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
### Description
One Ghidra backend limitation found during testing is that it may identify what should be a function as a label during its analysis.
### Steps to Reproduce
See mimikatz.exe_:0x40e5c2
**Expected behavior:**
Should be identified as a function (FUN_0040e5c2)
**Actual behavior:**
Ghidra identifies this address as a label instead (LAB_0040e5c2)
### Versions
```
Ghidra 10.3.2
capa 6.0.0
```
Contributor guide
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.
Research direction
Start by reproducing the Ghidra backend behavior at mimikatz.exe_:0x40e5c2 with Ghidra 10.3.2 and capa 6.0.0. Trace how the backend classifies that address, then verify that the result identifies FUN_0040e5c2 as a function rather than LAB_0040e5c2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100