-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Added CVE-2015-1635 #9123
Added CVE-2015-1635 #9123
Conversation
Thanks for this contribution @PhillipoTF2 |
Hello @PhillipoTF2, thank you so much for sharing this template with the community and contributing to this project 🍻 |
Hey, |
Quick update:
From what I can tell the template it working as expected against patched and unpatched test VMs. I have not tested this yet against Windows 7, 8 or 8.1 however I will test on those systems once I can get a test VM of those spun up. For this template I did have to match on the words 'HTTP Error 416' rather than the status code 416 as for some reason Windows Server 2012 hosts were not being picked up using the status code. However, Matching on the words seems perfectly fine from what I can tell. Please do reply with any more information you need or to bring up any potential issues. |
Hello, @PhillipoTF2. Thank you very much for sharing the debug info with us. I've added an additional matcher to the template. Please let us know if everything seems good. |
Seems fine to me. Happy with the changes. Thanks for your help with this template :) |
Template / PR Information
Template Validation
I've validated this template locally?
Additional Details (leave it blank if not applicable)
This is a working template for CVE-2015-1635. I am aware that there was a previous PR for CVE-2015-1635 that was rejected for an insufficient matching condition. I believe that this template should be sufficient. You may notice that I opt to match on the words "HTTP ERROR 416" rather than a status code, this is because during testing I was unable to get it to match on the status code on some versions of Windows Server. If you have any suggested changes it will be great to hear from you :)
Additional References: