-
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
Create CVE-2017-1000353.yaml #11191
base: main
Are you sure you want to change the base?
Create CVE-2017-1000353.yaml #11191
Conversation
Jenkins Unauthenticated Remote Code Execution
👉 To complete your submission, sign up on Algora, link your Github account and submit the data for your PR. |
Thanks so much for your contribution @hnd3884 ! :) |
@hnd3884, thank you so much for sharing this template with the community and contributing to this project 🍻 Can you confirm if this CVE can’t be written using HTTP/TCP + helpers or the JS protocol? We avoid adding code templates for CVEs that can be achieved using HTTP, TCP, or JavaScript, as such templates are blocked by default and won’t produce results. Therefore, we prioritize creating templates with other protocols unless exceptions are made. |
Dear @princechaddha, The reason i think it could not be written using HTTP/TCP + helpers or the JS protocol is that we have to prepare serialized data with complex steps (find index, , and the serialized payload also can not be generated by builtin ysoserial tool. The exploit steps are as same as CVE-2016-9299, with different gadget chain https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2016/CVE-2016-9299.yaml . I tried both http and tcp and i'm not farmiliar with javascript |
When i tried to use two tcp request, It work perfectly if i specify interact url and manually check for dns request. But when i use {{interactsh-url}} to auto detect using interact protocol, nuclei keeps return |
/claim #11185
Jenkins Unauthenticated Remote Code Execution
Template / PR Information
Provide full url of Jenkins like below
The template exploit unsafe deserialization and execute command
curl https://{{interactsh-url}}
so use interactsh protocol as matcherTemplate Validation
I've validated this template locally?
Additional Details (leave it blank if not applicable)
POC
Additional References: