Skip to content
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

GUID mismatch in dotnet module #2057

Open
bartblaze opened this issue Mar 20, 2024 · 0 comments
Open

GUID mismatch in dotnet module #2057

bartblaze opened this issue Mar 20, 2024 · 0 comments
Labels

Comments

@bartblaze
Copy link

bartblaze commented Mar 20, 2024

Describe the bug
Using Yara to extract some .NET information from a binary, in this example, eb0746edea71e38e7b09c10994371999634fa09ec7662a5ba14105ad86f4ad19, it reports the following:

Typelib: 1EA4DBF0-3C3B-11CF-810C-00AA00389B71
# of GUIDs: 1
dotnet.guid: 0
 -> guid = cd277104-27a2-4dea-8628-a9cc7d91df1b

However, using ILdasm or a custom tool (using the dnlib library), we get:

MVID: cd277104-27a2-4dea-8628-a9cc7d91df1b
  GUID: 1EA4DBF0-3C3B-11CF-810C-00AA00389B71
  TYPELIB Version: 1.1

Suggestion:
The 2nd GUID should be renamed as MVID to avoid confusion. I'll see if I can do a PR at some point.

To Reproduce
You can review yourself by parsing the accessibility DLL from .NET:
https://www.virustotal.com/gui/file/eb0746edea71e38e7b09c10994371999634fa09ec7662a5ba14105ad86f4ad19/details
Note that VT does report the correct values.

Expected behavior
Yara classifies GUID/Typelib and MVID accordingly.

Screenshots
From ILSpy for the same DLL as above:

ilspy

Please complete the following information:

  • OS: Win 10 x64
  • YARA version: 4.5.0

Additional context
N/A

@bartblaze bartblaze added the bug label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant