-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse LC_DYLD_CHAINED_FIXUPS
and LC_DYLD_EXPORTS_TRIE
in the macho module
#301
Comments
@latonis FYI, in case you have bandwith for taking at look at this. |
will take a look today :) |
#303 parses the exports_trie load command 😄 |
#305 parses the fixups |
plusvic
pushed a commit
that referenced
this issue
Feb 6, 2025
Implements the parsing required for exports defined via `LC_DYLD_EXPORTS_TRIE` as described in #301.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, yara-x retrieves the imports and exports of a Mach-O binary only by parsing the
LC_DYLD_INFO_ONLY
andLC_DYLD_INFO
commands. However, the Mach-O binary may contain newer commands,LC_DYLD_CHAINED_FIXUPS
andLC_DYLD_EXPORTS_TRIE
, instead of the former two.For example, the binary with SHA-256
3c7879d0b6419b39f9a3ea6372576c25152d9bbc9edafe4953e3eb8ee3a89bad
has these commands, but a rule containingmacho.has_export("_MsoABTerm")
will never match on it despite having the export.More info: https://github.com/qyang-nj/llios/blob/main/dynamic_linking/chained_fixups.md
The text was updated successfully, but these errors were encountered: