Skip to content

[Rule: New] Potential Web Server Fuzzing Attempts Detected #4720

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MakoWish
Copy link
Contributor

Pull Request

Issue link(s):

Summary

This rule attempts to detect potential fuzzing attempts against web servers. Fuzzing is a malicious attempt to find misconfigurations, local file inclusions, directory traversal, or other vulnerabilities in a web service. These attempts typically generate numerous error status codes (403, 404, etc.), so this rule looks for a sequence of these status codes from the same source IP to the same destination IP.

How To Test

Checklist

  • Added a label for the type of pr: bug, enhancement, schema, maintenance, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
  • Added the meta:rapid-merge label if planning to merge within 24 hours
  • Secret and sensitive material has been managed correctly
  • Automated testing was updated or added to match the most common scenarios
  • Documentation and comments were added for features that require explanation

Contributor checklist

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

Successfully merging this pull request may close these issues.

1 participant