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

Possible error in CVE-2017-7529.yaml matcher #424

Closed
savushkin-yauheni opened this issue Sep 7, 2020 · 3 comments · Fixed by #425
Closed

Possible error in CVE-2017-7529.yaml matcher #424

savushkin-yauheni opened this issue Sep 7, 2020 · 3 comments · Fixed by #425

Comments

@savushkin-yauheni
Copy link
Contributor

words:
- "Server: nginx"
- "Content-Range"
condition: and
part: header

Hi guys!
If you check 2 exploits for that cve you will see that Content-Range should be in the body, so right now it produces false positives :
https://gist.githubusercontent.com/BlackVirusScript/75fae10a037c376555b0ad3f3da1a966/raw/d1cc081053636711881ea45c84e0971d5babe103/CVE-2017-7529.py
nixawk/labs#15

Thank you.

@toufik-airane
Copy link
Contributor

Can you check that PR? #425
Thanks.

@ehsandeep ehsandeep linked a pull request Sep 7, 2020 that will close this issue
@toufik-airane
Copy link
Contributor

Dear @savushkin-yauheni the fix was accepted, would you mind to test the new template? Thanks.

@savushkin-yauheni
Copy link
Contributor Author

Dear @savushkin-yauheni the fix was accepted, would you mind to test the new template? Thanks.

It looks fine! Thank you ;)

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

Successfully merging a pull request may close this issue.

2 participants