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

Suggestion: Add RFI/LFI Vulnerability Dectection #2

Open
GoogleCodeExporter opened this issue Aug 1, 2015 · 4 comments
Open

Suggestion: Add RFI/LFI Vulnerability Dectection #2

GoogleCodeExporter opened this issue Aug 1, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Can you add a module for scanning for Local and Remote File Includes?

Original issue reported on code.google.com by itspa...@gmail.com on 17 May 2012 at 2:11

@GoogleCodeExporter
Copy link
Author

Yes that should be relatively simple enough to implement. I will try fit it in 
for the next release.

The test that checks for potentially insecure direct object references looks 
for file names, or paths, in the URL query string but does not actually go the 
step further and manipulate them to test for RFI/LFI.

Original comment by webvuls...@gmail.com on 21 May 2012 at 12:11

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Original comment by webvuls...@gmail.com on 21 May 2012 at 12:12

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Using dynamic methods for this is far better than using someone elses shell. 
See code.google.com/p/fimap for ideas. 
Adding RFI/LFI to this would be excellent - I think a good compromise would be 
to have it test for LFI/RFI on all parameters, while also using the rfilist.dat 
file floating around (I will link when I find it) to check paths, just in case.
Loving the project though!

Original comment by the.info...@gmail.com on 9 Jun 2012 at 4:52

@GoogleCodeExporter
Copy link
Author

Great that you like the project! Yes I agree, I think the scanner should have 
support for this vulnerability as it can be a high-risk one. I released another 
version yesterday but, unfortunately, I only had a few days to spend on the 
project and had a few issues to fix so I did not think I would fit this in. I 
should definitely be able to fit it in for the next one though. Thanks for the 
feedback and suggestions!

Original comment by webvuls...@gmail.com on 10 Jun 2012 at 4:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant