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

Reflection Detection #288

Open
gfs opened this issue Sep 16, 2020 · 0 comments
Open

Reflection Detection #288

gfs opened this issue Sep 16, 2020 · 0 comments
Labels
rule Related to a default Application Inspector Rule

Comments

@gfs
Copy link
Contributor

gfs commented Sep 16, 2020

I'm not sure how exactly this applies to other languages but this is a particular issue in C#.

Using Reflection can allow for dynamic behavior at runtime, including dynamic access to APIs which are not discernable at static analysis time. Application Inspector should report when an app using reflection in a way that would allow such behavior.

If you want a project to test reflection rules against see OAT.

Proposal:

I don't think we want to overgrab here, so there are some things that seem okay.

Check the Version Number by reflecting the assembly information from a type.
Read an embedded file

And things that are less common that might be interesting:

Create an object using invoke/constructorinfo
Loading assemblies at runtime
Invoke a method (for example using invoke method)
etc.

@gfs gfs added the enhancement New feature or request label Sep 16, 2020
@guyacosta guyacosta self-assigned this Sep 20, 2020
@gfs gfs added rule Related to a default Application Inspector Rule and removed enhancement New feature or request labels May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rule Related to a default Application Inspector Rule
Projects
None yet
Development

No branches or pull requests

2 participants