honest pendant
Hello,
I have developed nuclei templates consisting of matchers and extractors aimed at enhancing our workflow efficiency.
The primary objectives of these templates are as follows:
Step 1: Identification of Spring Actuators within a GitHub repository post-checkout.
Step 2: Localization of URIs following the format of https://*.targetcompany.tld
Step 3: Accessing the identified URI/Actuator.
Each script operates autonomously and has demonstrated success in its respective function.
Currently, my focus is on integrating these scripts into a seamless workflow, structured around three distinct steps:
Step 1: Identification of Actuator endpoints within the source code.
Step 2: Detection and extraction of https:// URIs upon Actuator identification.
Step 3: Construction of a URI based on the extracted URIs, subsequently accessing the Actuator.
I am encountering a challenge regarding the functionality of nuclei workflows.
Specifically, I am uncertain whether nuclei workflows permit searching within local files for steps 1 and 2, followed by the initiation of an HTTP request to the target in step 3.
So basically it will construct a path in Step 3 that should look like:
Moreover, if such functionality is supported, I am interested to know if it allows for chaining similar to subtemplates, as depicted in the attached screenshot.
I eagerly await any insights or guidance you may offer on this matter.
mortal pecan
