In order to use a Repeater from within a local network, you must first make sure it has a proper access to all the target applications.
You can use the
nexploit-cli configure --nogui command to run a simple connectivity testing process.
- The machine on which the Repeater will be run, must have the latest version of the Nexploit CLI.
- A valid API key (
API token) with the following scopes:
You can create an organization API key or a personal API key.
- A valid
REPEATER_ID. To create a Repeater, see Managing Repeaters.
Run the command
nexploit-cli configure --noguiin your terminal.
The Nexploit Network Testing wizard is launched.
Repeater IDin the relative fields.
The CLI runs the first stage of the external communication diagnostics:
- Validating that the connection to amq.app.neuralegion.com:5672 at port 5672 is open is required for the Repeater to reach the scan engine.
- Validating that the connection to nexploit.app at port is open is required to reach the Nexploit API endpoints.
- Verifying provided Token and Repeater ID is required to validate the credentials.
The diagnostics results are provided next to the validation parameters.
After the external communication diagnostics has passed, the CLI switches to the validation of the Repeater communication with local target application(s).
- Enter the target URL(s) to test if the Repeater can reach them.
The internal communication diagnostics starts, and the Repeater tries to reach the specified applications.
- Once the diagnostics is completed, you can see how many targets cannot be reached by the Repeater.
To exit the wizard, close the terminal.
Updated about 1 month ago