mandiant / mandiant/GoReSym

Macho Miss

Open
#67 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
1.1k
Forks
110
Avg merge
3d 2h
Merged PRs (30d)
1

Description

738f838e6bb7ffc1104aeebf19a1829ef52fda4cc1934d49188ec1d80d330f4b

* stomped magic
* arm64 moduledata miss
* moduledata `bytes.Index` hits bogus bytes at start and doesn't try next match
* section data reading logic seems off

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

Start with commit 738f838e6bb7ffc1104aeebf19a1829ef52fda4cc1934d49188ec1d80d330f4b and trace Mach-O handling for magic detection, arm64 moduledata matching, and section data reads. Reproduce the reported miss and determine what successful symbol recovery should look like for the affected binary.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
reverse-engineering, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.