method_4_exploitation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
method_4_exploitation [2022/12/31 22:26] – [Tool: SQLMap] gman | method_4_exploitation [2023/01/12 00:27] (current) – [Defaults] gman | ||
---|---|---|---|
Line 49: | Line 49: | ||
---- | ---- | ||
+ | ====== Defaults ====== | ||
+ | |||
+ | Many folks leave many devices with factory defaults. You can quickly look up the default login creds here: | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * [[https:// | ||
+ | |||
+ | ---- | ||
====== Tools ====== | ====== Tools ====== | ||
Line 189: | Line 198: | ||
* It works with a variety of protocols. | * It works with a variety of protocols. | ||
* It's a bit more difficult to use. The author says it's "less script kiddie friendly." | * It's a bit more difficult to use. The author says it's "less script kiddie friendly." | ||
- | |||
- | ---- | ||
- | |||
- | ====== Shells ====== | ||
- | |||
- | ===== Reverse Shells ===== | ||
- | |||
- | {{ : | ||
- | |||
- | In a reverse shell, a victim machine connects back to us at the attack machine. | ||
- | * You will use reverse shells 95% of the time | ||
- | |||
- | https:// | ||
- | http:// | ||
- | |||
- | **PHP Reverse Shell: | ||
- | * Instructions: | ||
- | * Download: https:// | ||
- | |||
- | ===== Bind Shells ===== | ||
- | |||
- | {{ : | ||
- | |||
- | In a bind shell, we connect to the target. | ||
- | * You fire off an exploint into the target machine, open up a port, and then use the attack machine to connect. | ||
- | |||
- | https:// | ||
---- | ---- | ||
Line 223: | Line 205: | ||
===== Command ===== | ===== Command ===== | ||
- | here | + | **Command Injection Attacks:** These are attacks that attempt to send commands through a web app to the operating system. |
+ | * It would give you the ability to directly manipulate the o/s. | ||
+ | * On Linux, use the '' | ||
+ | |||
+ | **Example: | ||
+ | * When we create our account with the username " | ||
+ | * '' | ||
+ | * Using command injection, you add commands to our user input: | ||
+ | * '' | ||
+ | * This would result in a command like this: | ||
+ | * '' | ||
+ | * And that's bad. | ||
===== SQLi ===== | ===== SQLi ===== | ||
Line 238: | Line 231: | ||
Automates SQLi enumeration and exploitation. Use it only after you have manually verified there is indeed an SQLi vulnerability on the target. | Automates SQLi enumeration and exploitation. Use it only after you have manually verified there is indeed an SQLi vulnerability on the target. | ||
- | ===== Blind SQLi ===== | + | ==== Blind SQLi ==== |
Blind SQL injection takes two forms: boolean-based (T/F) and timing-based. | Blind SQL injection takes two forms: boolean-based (T/F) and timing-based. | ||
Line 269: | Line 262: | ||
* They automate these timing-based attacks, making them fairly easy. | * They automate these timing-based attacks, making them fairly easy. | ||
+ | ---- | ||
+ | |||
+ | ====== Shells ====== | ||
+ | |||
+ | ===== Reverse Shells ===== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In a reverse shell, a victim machine connects back to us at the attack machine. | ||
+ | * You will use reverse shells 95% of the time | ||
+ | |||
+ | https:// | ||
+ | http:// | ||
+ | |||
+ | **PHP Reverse Shell: | ||
+ | * Instructions: | ||
+ | * Download: https:// | ||
+ | |||
+ | ===== Bind Shells ===== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In a bind shell, we connect to the target. | ||
+ | * You fire off an exploint into the target machine, open up a port, and then use the attack machine to connect. | ||
+ | |||
+ | https:// | ||
---- | ---- |
method_4_exploitation.1672525607.txt.gz · Last modified: by gman