tomcat-manager-deploy

Remote code execution via Tomcat Manager is achieved by deploying a malicious WAR file containing a JSP reverse shell. Once deployed, triggering the JSP establishes a reverse shell connection back to the attacker for server access.

Deploying a WAR file via the Tomcat Manager text API requires authenticated manager-script credentials. The process involves generating a JSP reverse shell WAR and sending an HTTP request to the Manager endpoint to upload and trigger it.

Creating a WAR reverse shell for Apache Tomcat exploitation involves generating a JSP payload packaged as a WAR file. This can be done manually or using msfvenom to produce the payload for deployment to the target server.

Yes, the Tomcat Manager HTML interface supports WAR deployment for remote code execution. Both the HTML interface and the text API are viable deployment methods when accessible with valid manager-gui or manager-script credentials.

Deploying a WAR file to Tomcat Manager requires valid credentials with manager-script or manager-gui roles. These credentials authenticate access to the Manager application, enabling the upload of malicious WAR files for RCE.

Yes, Tomcat Manager WAR deployment includes cleanup procedures after establishing a reverse shell. The workflow covers WAR generation, deployment, reverse shell delivery, and post-exploitation cleanup to remove the malicious application.