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

add context vars in code and multi #5051

Conversation

tovask
Copy link
Contributor

@tovask tovask commented Apr 15, 2024

make the extracted variables available in subsequence code or multiprotocol templates when executing in a workflow

fix #4797

make the extracted variables available in subsequence templates when executing in a workflow

fix projectdiscovery#4797
})
// path2 responds with the value of the "extracted" query parameter, e.g.: /path2?extracted=blog.projectdiscovery.io => blog.projectdiscovery.io
router.GET("/path2", func(w http.ResponseWriter, r *http.Request, _ httprouter.Params) {
fmt.Fprintf(w, "%s", r.URL.Query().Get("extracted"))

Check warning

Code scanning / CodeQL

Reflected cross-site scripting Medium

Cross-site scripting vulnerability due to
user-provided value
.
@GeorginaReeder
Copy link

Thanks for your contribution @tovask , we appreciate it!

Copy link
Member

@tarunKoyalwar tarunKoyalwar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm !

@ehsandeep
Copy link
Member

thank you @tovask for implementing fix for it.

@ehsandeep ehsandeep merged commit bec7cb2 into projectdiscovery:dev Apr 16, 2024
12 checks passed
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 this pull request may close these issues.

Extracted variables not recognized if the next Template in the Workflow uses the code protocol
4 participants