<p align="center">
<a href="https://spyboy.in/twitter">
<img src="https://img.shields.io/badge/-TWITTER-black?logo=twitter&style=for-the-badge">
</a>
<a href="https://spyboy.in/">
<img src="https://img.shields.io/badge/-spyboy.in-black?logo=google&style=for-the-badge">
</a>
<a href="https://spyboy.blog/">
<img src="https://img.shields.io/badge/-spyboy.blog-black?logo=wordpress&style=for-the-badge">
</a>
<a href="https://spyboy.in/Discord">
<img src="https://img.shields.io/badge/-Discord-black?logo=discord&style=for-the-badge">
</a>
</p>
<br>
<img width="100%" align="centre" src="https://cdn.discordapp.com/attachments/1141162711464550430/1152291533563891793/websecp.png" />
<h4 align="center"> Web Security Assessment Tool, Bypass 403</h4>
A cutting-edge utility designed exclusively for web security aficionados, penetration testers, and system administrators. WebSecProbe is your advanced toolkit for conducting intricate web security assessments with precision and depth. This robust tool streamlines the intricate process of scrutinizing web servers and applications, allowing you to delve into the technical nuances of web security and fortify your digital assets effectively.
<h4 align="center"> This tool is a Proof of Concept and is for Educational Purposes Only. </h4>
---
WebSecProbe is designed to perform a series of HTTP requests to a target URL with various payloads in order to test for potential security vulnerabilities or misconfigurations. Here's a brief overview of what the code does:
- It takes user input for the target URL and the path.
- It defines a list of payloads that represent different HTTP request variations, such as URL-encoded characters, special headers, and different HTTP methods.
- It iterates through each payload and constructs a full URL by appending the payload to the target URL.
- For each constructed URL, it sends an HTTP GET request using the requests library, and it captures the response status code and content length.
- It prints the constructed URL, status code, and content length for each request, effectively showing the results of each variation's response from the target server.
- After testing all payloads, it queries the Wayback Machine (a web archive) to check if there are any archived snapshots of the target URL/path. If available, it prints the closest archived snapshot's information.
> Does This Tool Bypass 403 ?
> It doesn't directly attempt to bypass a 403 Forbidden status code. The code's purpose is more about testing the behavior of the server when different requests are made, including requests with various payloads, headers, and URL variations. While some of the payloads and headers in the code might be used in certain scenarios to test for potential security misconfigurations or weaknesses, it doesn't guarantee that it will bypass a 403 Forbidden status code.
> In summary, this code is a tool for exploring and analyzing a web server's responses to different requests, but whether or not it can bypass a 403 Forbidden status code depends on the specific configuration and security measures implemented by the target server.
<br>
<details>
<summary>Click to expand: Payload Breakdown</summary>
Here's a brief breakdown of the payloads:
- **Empty String:**
- An empty string as a payload.
- **URL Encoding (%2e):**
- URL encoding of a dot (.) concatenated with the path.
- **Path with Slash (/):**
- Path followed by a slash (/).
- **Double Slash (//):**
- Double slash before and after the path.
- **Path with Current Directory (./):**
- Current directory (./) before and after the path.
- **Request Header (-H X-Original-URL):**
- X-Original-URL header with the path.
- **Request Header (-H X-Custom-IP-Authorization):**
- X-Custom-IP-Authorization header with the IP address 127.0.0.1.
- **Request Header (-H X-Forwarded-For):**
- X-Forwarded-For header with the IP address http://127.0.0.1 and 127.0.0.1:80.
- **Request Header (-H X-rewrite-url):**
- X-rewrite-url header with the path.
- **URL Encoding (%20 and %09):**
- URL encoding with space (%20) and tab (%09).
- **Query Parameter (?):**
- Query parameter with a question mark (?).
- **Path with HTML Extension (.html):**
- Path with .html extension.
- **Path with Query String (/?anything):**
- Path followed by a query string.
- **Fragment Identifier (#):**
- Fragment identifier with a hash (#).
- **POST Request Header (-H Content-Length:0 -X POST):**
- Content-Length header set to 0 and a POST request.
- **Wildcard (*):**
- Wildcard after the path.
- **Path with PHP Extension (.php):**
- Path with .php extension.
- **Path with JSON Extension (.json):**
- Path with .json extension.
- **HTTP Method (-X TRACE):**
- TRACE HTTP method.
- **Request Header (-H X-Host):**
- X-Host header with the IP address 127.0.0.1.
- **Path Traversal (..;/):**
- Path traversal.
- **Whitespace at the Beginning (" " + self.path):**
- Whitespace added at the beginning of the path.
- **Path with Semicolon (;):**
- Semicolon added before and after the path.
- **Path with Extra Slashes:**
- Test for bypassing by adding extra slashes (e.g., //path).
- **Path with URL-encoded Slash:**
- Use URL-encoded slash to bypass (e.g., %2Fpath).
- **Path with Double URL-encoded Slash:**
- Use double URL-encoded slash (e.g., %252Fpath).
- **Path with Path Parameter:**
- Add a path parameter (e.g., /path;parameter).
- **Path with Query Parameter in Path:**
- Add a query parameter within the path (e.g., /path?parameter).
- **Path with Additional Dots:**
- Add additional dots in the path (e.g., /path/../path).
- **Path with Unicode Encoding:**
- Use Unicode encoding to represent characters (e.g., %u002Fpath).
- **Path with Double URL-encoded Dot:**
- Use double URL-encoded dot (e.g., %252E).
- **Path with URL-encoded Null Byte:**
- Use URL-encoded null byte (e.g., %00).
- **Path with Hex Encoding:**
- Use hex encoding for characters in the path (e.g., /path%2Ehtml).
This list covers a variety of common techniques used in web security testing. However, the effectiveness of these payloads depends on the specific vulnerabilities or misconfigurations present in the target system.
</details>
---
<h4 align="center">
OS compatibility :
<br><br>
<img src="https://img.shields.io/badge/Windows-05122A?style=for-the-badge&logo=windows">
<img src="https://img.shields.io/badge/Linux-05122A?style=for-the-badge&logo=linux">
<img src="https://img.shields.io/badge/Android-05122A?style=for-the-badge&logo=android">
<img src="https://img.shields.io/badge/macOS-05122A?style=for-the-badge&logo=macos">
</h4>
<h4 align="center">
Requirements:
<br><br>
<img src="https://img.shields.io/badge/Python-05122A?style=for-the-badge&logo=python">
<img src="https://img.shields.io/badge/Git-05122A?style=for-the-badge&logo=git">
</h4>
### ⭔ PYPI Installation : https://pypi.org/project/WebSecProbe/
---
```
pip install WebSecProbe
```
#### How To Run On CLI:
`WebSecProbe <URL> <Path>`
Example:
```
WebSecProbe https://example.com admin-login
```
#### Python Code
```py
from WebSecProbe.main import WebSecProbe
if __name__ == "__main__":
url = 'https://example.com' # Replace with your target URL
path = 'admin-login' # Replace with your desired path
probe = WebSecProbe(url, path)
probe.run()
```
---
#### 💬 If having issue [Chat here](https://discord.gg/ZChEmMwE8d)
[](https://discord.gg/ZChEmMwE8d)
### ⭔ Snapshots:
---
<img width="100%" align="centre" src="https://cdn.discordapp.com/attachments/1141162711464550430/1151709638262263858/Screenshot_2023-09-14_at_8.11.44_AM.png" />
Raw data
{
"_id": null,
"home_page": "https://github.com/spyboy-productions/WebSecProbe/",
"name": "WebSecProbe",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "HTTP-Request-Analysis,bypass-403,Header-Injection,Historical-Analysis,Payload-Variations,Vulnerability-Assessment",
"author": "Spyboy",
"author_email": "contact@spyboy.in",
"download_url": "https://files.pythonhosted.org/packages/80/95/a11c9bd16788371c640c4d829388fd6081cd047ab4b091b30cd7d7de5a77/WebSecProbe-0.0.11.tar.gz",
"platform": null,
"description": "<p align=\"center\">\n <a href=\"https://spyboy.in/twitter\">\n <img src=\"https://img.shields.io/badge/-TWITTER-black?logo=twitter&style=for-the-badge\">\n </a>\n \n <a href=\"https://spyboy.in/\">\n <img src=\"https://img.shields.io/badge/-spyboy.in-black?logo=google&style=for-the-badge\">\n </a>\n \n <a href=\"https://spyboy.blog/\">\n <img src=\"https://img.shields.io/badge/-spyboy.blog-black?logo=wordpress&style=for-the-badge\">\n </a>\n \n <a href=\"https://spyboy.in/Discord\">\n <img src=\"https://img.shields.io/badge/-Discord-black?logo=discord&style=for-the-badge\">\n </a>\n \n</p>\n\n<br>\n\n<img width=\"100%\" align=\"centre\" src=\"https://cdn.discordapp.com/attachments/1141162711464550430/1152291533563891793/websecp.png\" />\n\n\n<h4 align=\"center\"> Web Security Assessment Tool, Bypass 403</h4>\n\nA cutting-edge utility designed exclusively for web security aficionados, penetration testers, and system administrators. WebSecProbe is your advanced toolkit for conducting intricate web security assessments with precision and depth. This robust tool streamlines the intricate process of scrutinizing web servers and applications, allowing you to delve into the technical nuances of web security and fortify your digital assets effectively.\n\n<h4 align=\"center\"> This tool is a Proof of Concept and is for Educational Purposes Only. </h4> \n\n---\n\nWebSecProbe is designed to perform a series of HTTP requests to a target URL with various payloads in order to test for potential security vulnerabilities or misconfigurations. Here's a brief overview of what the code does:\n\n- It takes user input for the target URL and the path.\n- It defines a list of payloads that represent different HTTP request variations, such as URL-encoded characters, special headers, and different HTTP methods.\n- It iterates through each payload and constructs a full URL by appending the payload to the target URL.\n- For each constructed URL, it sends an HTTP GET request using the requests library, and it captures the response status code and content length.\n- It prints the constructed URL, status code, and content length for each request, effectively showing the results of each variation's response from the target server.\n- After testing all payloads, it queries the Wayback Machine (a web archive) to check if there are any archived snapshots of the target URL/path. If available, it prints the closest archived snapshot's information.\n\n> Does This Tool Bypass 403 ?\n\n> It doesn't directly attempt to bypass a 403 Forbidden status code. The code's purpose is more about testing the behavior of the server when different requests are made, including requests with various payloads, headers, and URL variations. While some of the payloads and headers in the code might be used in certain scenarios to test for potential security misconfigurations or weaknesses, it doesn't guarantee that it will bypass a 403 Forbidden status code.\n\n> In summary, this code is a tool for exploring and analyzing a web server's responses to different requests, but whether or not it can bypass a 403 Forbidden status code depends on the specific configuration and security measures implemented by the target server.\n\n<br>\n\n<details>\n <summary>Click to expand: Payload Breakdown</summary>\n\n Here's a brief breakdown of the payloads:\n\n - **Empty String:**\n - An empty string as a payload.\n\n - **URL Encoding (%2e):**\n - URL encoding of a dot (.) concatenated with the path.\n\n - **Path with Slash (/):**\n - Path followed by a slash (/).\n\n - **Double Slash (//):**\n - Double slash before and after the path.\n\n - **Path with Current Directory (./):**\n - Current directory (./) before and after the path.\n\n - **Request Header (-H X-Original-URL):**\n - X-Original-URL header with the path.\n\n - **Request Header (-H X-Custom-IP-Authorization):**\n - X-Custom-IP-Authorization header with the IP address 127.0.0.1.\n\n - **Request Header (-H X-Forwarded-For):**\n - X-Forwarded-For header with the IP address http://127.0.0.1 and 127.0.0.1:80.\n\n - **Request Header (-H X-rewrite-url):**\n - X-rewrite-url header with the path.\n\n - **URL Encoding (%20 and %09):**\n - URL encoding with space (%20) and tab (%09).\n\n - **Query Parameter (?):**\n - Query parameter with a question mark (?).\n\n - **Path with HTML Extension (.html):**\n - Path with .html extension.\n\n - **Path with Query String (/?anything):**\n - Path followed by a query string.\n\n - **Fragment Identifier (#):**\n - Fragment identifier with a hash (#).\n\n - **POST Request Header (-H Content-Length:0 -X POST):**\n - Content-Length header set to 0 and a POST request.\n\n - **Wildcard (*):**\n - Wildcard after the path.\n\n - **Path with PHP Extension (.php):**\n - Path with .php extension.\n\n - **Path with JSON Extension (.json):**\n - Path with .json extension.\n\n - **HTTP Method (-X TRACE):**\n - TRACE HTTP method.\n\n - **Request Header (-H X-Host):**\n - X-Host header with the IP address 127.0.0.1.\n\n - **Path Traversal (..;/):**\n - Path traversal.\n\n - **Whitespace at the Beginning (\" \" + self.path):**\n - Whitespace added at the beginning of the path.\n\n - **Path with Semicolon (;):**\n - Semicolon added before and after the path.\n\n - **Path with Extra Slashes:**\n - Test for bypassing by adding extra slashes (e.g., //path).\n\n - **Path with URL-encoded Slash:**\n - Use URL-encoded slash to bypass (e.g., %2Fpath).\n\n - **Path with Double URL-encoded Slash:**\n - Use double URL-encoded slash (e.g., %252Fpath).\n\n - **Path with Path Parameter:**\n - Add a path parameter (e.g., /path;parameter).\n\n - **Path with Query Parameter in Path:**\n - Add a query parameter within the path (e.g., /path?parameter).\n\n - **Path with Additional Dots:**\n - Add additional dots in the path (e.g., /path/../path).\n\n - **Path with Unicode Encoding:**\n - Use Unicode encoding to represent characters (e.g., %u002Fpath).\n\n - **Path with Double URL-encoded Dot:**\n - Use double URL-encoded dot (e.g., %252E).\n\n - **Path with URL-encoded Null Byte:**\n - Use URL-encoded null byte (e.g., %00).\n\n - **Path with Hex Encoding:**\n - Use hex encoding for characters in the path (e.g., /path%2Ehtml).\n\n This list covers a variety of common techniques used in web security testing. However, the effectiveness of these payloads depends on the specific vulnerabilities or misconfigurations present in the target system.\n\n</details>\n\n\n\n---\n\n<h4 align=\"center\">\n OS compatibility :\n <br><br>\n <img src=\"https://img.shields.io/badge/Windows-05122A?style=for-the-badge&logo=windows\">\n <img src=\"https://img.shields.io/badge/Linux-05122A?style=for-the-badge&logo=linux\">\n <img src=\"https://img.shields.io/badge/Android-05122A?style=for-the-badge&logo=android\">\n <img src=\"https://img.shields.io/badge/macOS-05122A?style=for-the-badge&logo=macos\">\n</h4>\n\n<h4 align=\"center\"> \nRequirements:\n<br><br>\n<img src=\"https://img.shields.io/badge/Python-05122A?style=for-the-badge&logo=python\">\n<img src=\"https://img.shields.io/badge/Git-05122A?style=for-the-badge&logo=git\">\n</h4>\n\n### \u2b54 PYPI Installation : https://pypi.org/project/WebSecProbe/\n---\n```\npip install WebSecProbe\n```\n\n#### How To Run On CLI:\n\n`WebSecProbe <URL> <Path>`\n\nExample: \n```\nWebSecProbe https://example.com admin-login\n```\n\n#### Python Code\n```py\nfrom WebSecProbe.main import WebSecProbe\n\nif __name__ == \"__main__\":\n url = 'https://example.com' # Replace with your target URL\n path = 'admin-login' # Replace with your desired path\n\n probe = WebSecProbe(url, path)\n probe.run()\n\n```\n\n---\n\n#### \ud83d\udcac If having issue [Chat here](https://discord.gg/ZChEmMwE8d)\n[](https://discord.gg/ZChEmMwE8d)\n\n### \u2b54 Snapshots:\n---\n\n<img width=\"100%\" align=\"centre\" src=\"https://cdn.discordapp.com/attachments/1141162711464550430/1151709638262263858/Screenshot_2023-09-14_at_8.11.44_AM.png\" />\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Web Security Assessment Tool",
"version": "0.0.11",
"project_urls": {
"Homepage": "https://github.com/spyboy-productions/WebSecProbe/"
},
"split_keywords": [
"http-request-analysis",
"bypass-403",
"header-injection",
"historical-analysis",
"payload-variations",
"vulnerability-assessment"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "3fb1c475004efc59eb35069da7d713f2000ba0c77410f022846309ba00df51b5",
"md5": "ae2fe084dc688a2b3269a15a5bf1f028",
"sha256": "070a3caf1bf53d1a0f26e12ef6f8dc7cfcdcabf9f2d7c008f6c4c2c425ad7704"
},
"downloads": -1,
"filename": "WebSecProbe-0.0.11-py3-none-any.whl",
"has_sig": false,
"md5_digest": "ae2fe084dc688a2b3269a15a5bf1f028",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 7453,
"upload_time": "2023-11-26T08:27:21",
"upload_time_iso_8601": "2023-11-26T08:27:21.581953Z",
"url": "https://files.pythonhosted.org/packages/3f/b1/c475004efc59eb35069da7d713f2000ba0c77410f022846309ba00df51b5/WebSecProbe-0.0.11-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "8095a11c9bd16788371c640c4d829388fd6081cd047ab4b091b30cd7d7de5a77",
"md5": "a1100a477fcc37cd494cd039aed67977",
"sha256": "38a6cacf71d24edc32c7f24d52d2c905368741cc64516ae8320f7f9ac556824e"
},
"downloads": -1,
"filename": "WebSecProbe-0.0.11.tar.gz",
"has_sig": false,
"md5_digest": "a1100a477fcc37cd494cd039aed67977",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 7368,
"upload_time": "2023-11-26T08:27:23",
"upload_time_iso_8601": "2023-11-26T08:27:23.160161Z",
"url": "https://files.pythonhosted.org/packages/80/95/a11c9bd16788371c640c4d829388fd6081cd047ab4b091b30cd7d7de5a77/WebSecProbe-0.0.11.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-11-26 08:27:23",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "spyboy-productions",
"github_project": "WebSecProbe",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "websecprobe"
}
JSON
