Recent capa version don't work with sample dumped from memory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
Description
I have dumped the UPX packed sample a27afd3ec5b3f2e705347b2c39847fcd659e430396abd081109db0e7f96d1d3e from memory using pd64. capa 7.3-8.0 does not detect any capabilities in the dumped sample, while capa 7.0-7.2 does.
I wonder why capa does not detect the capabilities of this sample in the newer versions and if we can fix it.
capa 7.3-8.0 does detect capabilities on the UPX unpacked version (unpacked using upx -d after renaming the sections).
Steps to Reproduce
- Execute
a27afd3ec5b3f2e705347b2c39847fcd659e430396abd081109db0e7f96d1d3e - Dump the executed process with
pd64 -pid <PID> - Run capa 7.3 and 7.2 on the dumped sample
Versions
capa 7.3-8.0 standalone tool.
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 reported comparison: run capa 7.2 and 7.3-8.0 on the pd64 memory dump, then compare the result with the UPX-unpacked sample. Trace the version change affecting dumped UPX samples; done means newer versions detect the same capabilities as 7.0-7.2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100