[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABSPBW0MKVWG7GSHCTPPBK":3,"skill-same:01M7ABSPBW0MKVWG7GSHCTPPBK":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7ABSPBW0MKVWG7GSHCTPPBK","testing-for-business-logic-vulnerabilities",null,"Manually identifies flaws in application business logic - price manipulation, multi-step workflow bypass, and privilege escalation - by intercepting and modifying requests with Burp Suite, going beyond what automated vulnerability scanners detect. Use for e-commerce checkout\u002Fcart flows, voucher and rewards systems, or any assessment where scanners find little but business rules need scrutiny.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-business-logic-vulnerabilities\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-business-logic-vulnerabilities\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing-for-business-logic-vulnerabilities\ndescription: Manually identifies flaws in application business logic - price manipulation,\n  multi-step workflow bypass, and privilege escalation - by intercepting and modifying\n  requests with Burp Suite, going beyond what automated vulnerability scanners detect.\n  Use for e-commerce checkout\u002Fcart flows, voucher and rewards systems, or any assessment\n  where scanners find little but business rules need scrutiny.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- penetration-testing\n- business-logic\n- owasp\n- web-security\n- burpsuite\n- manual-testing\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1068\n---\n\n# Testing for Business Logic Vulnerabilities\n\n## When to Use\n\n- During authorized penetration tests when automated scanners have found few technical vulnerabilities\n- When assessing e-commerce platforms for pricing, cart, and payment flow manipulations\n- For testing multi-step workflows (registration, checkout, approval processes) for bypass opportunities\n- When evaluating rate-limited features like vouchers, coupons, referrals, and rewards systems\n- During security assessments of financial applications, voting systems, or any application with critical business rules\n\n## Prerequisites\n\n- **Authorization**: Written penetration testing agreement covering business logic testing\n- **Burp Suite Professional**: For intercepting and modifying multi-step request flows\n- **Application understanding**: Thorough knowledge of the application's intended business workflows\n- **Multiple test accounts**: Accounts at different privilege levels and states\n- **Browser DevTools**: For examining client-side validation logic\n- **Documentation**: Business requirements or user stories describing expected behavior\n\n## Workflow\n\n### Step 1: Map Business Workflows and Rules\n\nDocument all critical business processes and their expected constraints.\n\n```\n# Critical business flows to map:\n# 1. Registration\u002FOnboarding flow\n#    - Email verification requirements\n#    - Account approval process\n#    - Role assignment logic\n\n# 2. E-commerce\u002FPurchase flow\n#    - Product selection → Cart → Checkout → Payment → Confirmation\n#    - Price calculation logic\n#    - Discount\u002Fcoupon application\n#    - Quantity limits\n#    - Shipping cost calculation\n\n# 3. Authentication\u002FAuthorization flow\n#    - Login → MFA → Dashboard\n#    - Password reset → Token → New password\n#    - Role escalation\u002Fapproval\n\n# 4. Financial transactions\n#    - Balance check → Transfer → Confirmation\n#    - Withdrawal limits\n#    - Currency conversion\n\n# Document expected constraints:\n# - Minimum order amounts\n# - Maximum quantity per item\n# - Coupon usage limits (one per user)\n# - Referral reward caps\n# - Withdrawal daily limits\n# - Account verification requirements before certain actions\n```\n\n### Step 2: Test Price and Quantity Manipulation\n\nIntercept and modify price, quantity, and total values in requests.\n\n```bash\n# Test negative quantity\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": -1, \"price\": 99.99}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test zero price\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 1, \"price\": 0}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test extremely large quantity\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 999999999}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test decimal\u002Ffloat manipulation\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 0.001, \"price\": 0.01}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test integer overflow\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 2147483647}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Modify total amount directly in checkout request\n# Intercept in Burp and change total from 299.99 to 0.01\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"cart_id\": \"abc123\", \"total\": 0.01, \"payment_method\": \"card\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcheckout\"\n```\n\n### Step 3: Test Workflow Step Bypass\n\nAttempt to skip required steps in multi-step processes.\n\n```bash\n# Skip email verification\n# Instead of: Register → Verify email → Access dashboard\n# Try: Register → Access dashboard directly\ncurl -s -H \"Authorization: Bearer $UNVERIFIED_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fdashboard\"\n\n# Skip payment step\n# Instead of: Cart → Shipping → Payment → Confirmation\n# Try: Cart → Confirmation (skip payment)\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"cart_id\": \"abc123\", \"shipping_address\": \"123 Main St\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Forders\u002Fconfirm\"\n\n# Skip MFA step\n# Instead of: Login → MFA → Dashboard\n# Try: Login → Dashboard (skip MFA)\n# After successful password auth, directly access protected resources\n\n# Skip approval process\n# Instead of: Submit request → Manager approval → Access granted\n# Try: Submit request → Access granted (skip approval)\n\n# Repeat a step that should be one-time\n# Apply same coupon code multiple times\nfor i in $(seq 1 5); do\n  curl -s -X POST \\\n    -H \"Authorization: Bearer $TOKEN\" \\\n    -H \"Content-Type: application\u002Fjson\" \\\n    -d '{\"coupon_code\": \"DISCOUNT50\"}' \\\n    \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fapply-coupon\"\n  echo \"Attempt $i\"\ndone\n```\n\n### Step 4: Test Race Conditions in Business Logic\n\nExploit timing windows in concurrent request processing.\n\n```bash\n# Race condition on coupon application\n# Send multiple identical requests simultaneously\nfor i in $(seq 1 10); do\n  curl -s -X POST \\\n    -H \"Authorization: Bearer $TOKEN\" \\\n    -H \"Content-Type: application\u002Fjson\" \\\n    -d '{\"coupon_code\": \"ONETIME50\"}' \\\n    \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fapply-coupon\" &\ndone\nwait\n\n# Race condition on balance transfer\n# If user has $100, try to transfer $100 to two accounts simultaneously\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\": \"user_b\", \"amount\": 100}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Ftransfer\" &\n\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\": \"user_c\", \"amount\": 100}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Ftransfer\" &\nwait\n\n# Race condition on reward claiming\n# Using Burp Turbo Intruder for precise timing:\n# 1. Send request to Turbo Intruder\n# 2. Use race condition script template\n# 3. Send 20+ requests simultaneously\n# 4. Check if reward was claimed multiple times\n```\n\n### Step 5: Test Referral and Reward System Abuse\n\nFind ways to exploit promotional features and reward mechanisms.\n\n```bash\n# Self-referral: refer your own email\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"referral_email\": \"myown@email.com\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Freferrals\u002Finvite\"\n\n# Referral code reuse across multiple accounts\n# Create multiple accounts and use same referral code\n\n# Coupon stacking: apply multiple discount codes\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"coupon_codes\": [\"SAVE10\", \"WELCOME20\", \"VIP50\"]}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fapply-coupons\"\n\n# Abuse free trial: re-register with same details\n# Test if email+1@domain.com or email@domain.com bypass duplicate detection\n\n# Gift card \u002F credit manipulation\n# Buy gift card with gift card balance (circular)\n# Apply gift card with value > purchase price (get change as credit)\n\n# Test reward point manipulation\n# Earn points on order → Cancel order → Keep points\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Forders\u002F12345\u002Fcancel\"\n# Check if reward points from order 12345 were revoked\n```\n\n### Step 6: Test Role and Permission Logic\n\nAssess authorization logic for privilege escalation through business processes.\n\n```bash\n# Role escalation via registration parameter\ncurl -s -X POST \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"test@test.com\",\"password\":\"Test1234!\",\"role\":\"admin\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fauth\u002Fregister\"\n\n# Organization tenant boundary testing\n# User in Org A tries to access Org B resources via business workflows\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN_ORG_A\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"org_id\": \"org_b_id\", \"action\": \"view_reports\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Freports\"\n\n# Test for privilege retention after role downgrade\n# Admin → Regular user: can they still access admin functions?\n# Employee → Terminated: can they still access company resources?\n\n# Test invitation\u002Fdelegation abuse\n# Invite user with higher privileges than inviter has\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $REGULAR_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"new@test.com\",\"role\":\"admin\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fusers\u002Finvite\"\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **Business Logic Flaw** | A vulnerability in the application's workflow or rules that allows unintended actions |\n| **Price Manipulation** | Modifying price, quantity, or total values in client-side requests |\n| **Workflow Bypass** | Skipping required steps in a multi-step business process |\n| **Race Condition** | Exploiting concurrent request processing to violate business constraints |\n| **Privilege Escalation** | Gaining higher permissions through business process manipulation |\n| **Negative Testing** | Testing with unexpected values (negative, zero, null, extreme) |\n| **State Manipulation** | Changing application state in an order not intended by the business logic |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| **Burp Suite Professional** | Request interception, modification, and sequence testing |\n| **Burp Turbo Intruder** | High-speed request sending for race condition testing |\n| **Burp Sequencer** | Token randomness analysis for predictable reference testing |\n| **OWASP ZAP** | Open-source alternative for proxy-based testing |\n| **Postman** | Workflow testing with collection runners and environment variables |\n| **Custom scripts** | Python\u002Fbash scripts for automated business logic testing |\n\n## Common Scenarios\n\n### Scenario 1: Coupon Code Stacking\nAn e-commerce site allows applying multiple coupon codes. By stacking \"WELCOME10\", \"SAVE20\", and \"VIP30\", the total discount exceeds the product price, resulting in a negative balance or free order.\n\n### Scenario 2: Race Condition on Fund Transfer\nA banking application checks balance before transfer but does not lock the account. Sending two simultaneous $1000 transfers from a $1000 balance results in both succeeding, creating money from nothing.\n\n### Scenario 3: Checkout Price Override\nThe checkout flow sends the total amount in the POST body. Intercepting and changing the total from $499.99 to $0.01 results in a successful order at the manipulated price.\n\n### Scenario 4: Password Reset Token Reuse\nThe password reset flow generates a one-time token but does not invalidate it after use. The same token can be used repeatedly to reset the password.\n\n## Output Format\n\n```\n## Business Logic Vulnerability Finding\n\n**Vulnerability**: Price Manipulation in Checkout Flow\n**Severity**: Critical (CVSS 9.1)\n**Location**: POST \u002Fapi\u002Fcheckout - `total` parameter\n**OWASP Category**: A04:2021 - Insecure Design\n\n### Reproduction Steps\n1. Add item to cart (price: $499.99)\n2. Proceed to checkout\n3. Intercept POST \u002Fapi\u002Fcheckout request in Burp\n4. Modify \"total\" from 499.99 to 0.01\n5. Forward the request; order completes at $0.01\n\n### Business Rules Violated\n| Rule | Expected | Actual |\n|------|----------|--------|\n| Server-side price calculation | Total computed server-side | Client-submitted total accepted |\n| Coupon single use | One coupon per order | Same coupon applied 5 times |\n| Negative quantity check | Quantity >= 1 | Quantity -1 accepted (credit issued) |\n| Race condition on transfer | Balance checked atomically | Dual transfer exceeded balance |\n\n### Impact\n- Financial loss: orders processed at attacker-controlled prices\n- Inventory loss: products shipped for $0.01\n- Reward abuse: unlimited referral credits via self-referral\n- Double-spending via race condition on transfers\n\n### Recommendation\n1. Perform all price calculations server-side; never trust client-submitted totals\n2. Implement server-side validation for quantity (positive integers only)\n3. Use database-level locks or atomic transactions for financial operations\n4. Implement idempotency keys to prevent duplicate transaction processing\n5. Rate-limit and log coupon applications, referral submissions, and transfers\n```\n","# Testing for Business Logic Vulnerabilities\n\n## When to Use\n\n- During authorized penetration tests when automated scanners have found few technical vulnerabilities\n- When assessing e-commerce platforms for pricing, cart, and payment flow manipulations\n- For testing multi-step workflows (registration, checkout, approval processes) for bypass opportunities\n- When evaluating rate-limited features like vouchers, coupons, referrals, and rewards systems\n- During security assessments of financial applications, voting systems, or any application with critical business rules\n\n## Prerequisites\n\n- **Authorization**: Written penetration testing agreement covering business logic testing\n- **Burp Suite Professional**: For intercepting and modifying multi-step request flows\n- **Application understanding**: Thorough knowledge of the application's intended business workflows\n- **Multiple test accounts**: Accounts at different privilege levels and states\n- **Browser DevTools**: For examining client-side validation logic\n- **Documentation**: Business requirements or user stories describing expected behavior\n\n## Workflow\n\n### Step 1: Map Business Workflows and Rules\n\nDocument all critical business processes and their expected constraints.\n\n```\n# Critical business flows to map:\n# 1. Registration\u002FOnboarding flow\n#    - Email verification requirements\n#    - Account approval process\n#    - Role assignment logic\n\n# 2. E-commerce\u002FPurchase flow\n#    - Product selection → Cart → Checkout → Payment → Confirmation\n#    - Price calculation logic\n#    - Discount\u002Fcoupon application\n#    - Quantity limits\n#    - Shipping cost calculation\n\n# 3. Authentication\u002FAuthorization flow\n#    - Login → MFA → Dashboard\n#    - Password reset → Token → New password\n#    - Role escalation\u002Fapproval\n\n# 4. Financial transactions\n#    - Balance check → Transfer → Confirmation\n#    - Withdrawal limits\n#    - Currency conversion\n\n# Document expected constraints:\n# - Minimum order amounts\n# - Maximum quantity per item\n# - Coupon usage limits (one per user)\n# - Referral reward caps\n# - Withdrawal daily limits\n# - Account verification requirements before certain actions\n```\n\n### Step 2: Test Price and Quantity Manipulation\n\nIntercept and modify price, quantity, and total values in requests.\n\n```bash\n# Test negative quantity\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": -1, \"price\": 99.99}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test zero price\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 1, \"price\": 0}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test extremely large quantity\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 999999999}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test decimal\u002Ffloat manipulation\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 0.001, \"price\": 0.01}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Test integer overflow\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\": 1, \"quantity\": 2147483647}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fadd\"\n\n# Modify total amount directly in checkout request\n# Intercept in Burp and change total from 299.99 to 0.01\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"cart_id\": \"abc123\", \"total\": 0.01, \"payment_method\": \"card\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcheckout\"\n```\n\n### Step 3: Test Workflow Step Bypass\n\nAttempt to skip required steps in multi-step processes.\n\n```bash\n# Skip email verification\n# Instead of: Register → Verify email → Access dashboard\n# Try: Register → Access dashboard directly\ncurl -s -H \"Authorization: Bearer $UNVERIFIED_TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fdashboard\"\n\n# Skip payment step\n# Instead of: Cart → Shipping → Payment → Confirmation\n# Try: Cart → Confirmation (skip payment)\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"cart_id\": \"abc123\", \"shipping_address\": \"123 Main St\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Forders\u002Fconfirm\"\n\n# Skip MFA step\n# Instead of: Login → MFA → Dashboard\n# Try: Login → Dashboard (skip MFA)\n# After successful password auth, directly access protected resources\n\n# Skip approval process\n# Instead of: Submit request → Manager approval → Access granted\n# Try: Submit request → Access granted (skip approval)\n\n# Repeat a step that should be one-time\n# Apply same coupon code multiple times\nfor i in $(seq 1 5); do\n  curl -s -X POST \\\n    -H \"Authorization: Bearer $TOKEN\" \\\n    -H \"Content-Type: application\u002Fjson\" \\\n    -d '{\"coupon_code\": \"DISCOUNT50\"}' \\\n    \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fapply-coupon\"\n  echo \"Attempt $i\"\ndone\n```\n\n### Step 4: Test Race Conditions in Business Logic\n\nExploit timing windows in concurrent request processing.\n\n```bash\n# Race condition on coupon application\n# Send multiple identical requests simultaneously\nfor i in $(seq 1 10); do\n  curl -s -X POST \\\n    -H \"Authorization: Bearer $TOKEN\" \\\n    -H \"Content-Type: application\u002Fjson\" \\\n    -d '{\"coupon_code\": \"ONETIME50\"}' \\\n    \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fapply-coupon\" &\ndone\nwait\n\n# Race condition on balance transfer\n# If user has $100, try to transfer $100 to two accounts simultaneously\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\": \"user_b\", \"amount\": 100}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Ftransfer\" &\n\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\": \"user_c\", \"amount\": 100}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Ftransfer\" &\nwait\n\n# Race condition on reward claiming\n# Using Burp Turbo Intruder for precise timing:\n# 1. Send request to Turbo Intruder\n# 2. Use race condition script template\n# 3. Send 20+ requests simultaneously\n# 4. Check if reward was claimed multiple times\n```\n\n### Step 5: Test Referral and Reward System Abuse\n\nFind ways to exploit promotional features and reward mechanisms.\n\n```bash\n# Self-referral: refer your own email\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"referral_email\": \"myown@email.com\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Freferrals\u002Finvite\"\n\n# Referral code reuse across multiple accounts\n# Create multiple accounts and use same referral code\n\n# Coupon stacking: apply multiple discount codes\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"coupon_codes\": [\"SAVE10\", \"WELCOME20\", \"VIP50\"]}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fcart\u002Fapply-coupons\"\n\n# Abuse free trial: re-register with same details\n# Test if email+1@domain.com or email@domain.com bypass duplicate detection\n\n# Gift card \u002F credit manipulation\n# Buy gift card with gift card balance (circular)\n# Apply gift card with value > purchase price (get change as credit)\n\n# Test reward point manipulation\n# Earn points on order → Cancel order → Keep points\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Forders\u002F12345\u002Fcancel\"\n# Check if reward points from order 12345 were revoked\n```\n\n### Step 6: Test Role and Permission Logic\n\nAssess authorization logic for privilege escalation through business processes.\n\n```bash\n# Role escalation via registration parameter\ncurl -s -X POST \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"test@test.com\",\"password\":\"Test1234!\",\"role\":\"admin\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fauth\u002Fregister\"\n\n# Organization tenant boundary testing\n# User in Org A tries to access Org B resources via business workflows\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $TOKEN_ORG_A\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"org_id\": \"org_b_id\", \"action\": \"view_reports\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Freports\"\n\n# Test for privilege retention after role downgrade\n# Admin → Regular user: can they still access admin functions?\n# Employee → Terminated: can they still access company resources?\n\n# Test invitation\u002Fdelegation abuse\n# Invite user with higher privileges than inviter has\ncurl -s -X POST \\\n  -H \"Authorization: Bearer $REGULAR_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\":\"new@test.com\",\"role\":\"admin\"}' \\\n  \"https:\u002F\u002Ftarget.example.com\u002Fapi\u002Fusers\u002Finvite\"\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| **Business Logic Flaw** | A vulnerability in the application's workflow or rules that allows unintended actions |\n| **Price Manipulation** | Modifying price, quantity, or total values in client-side requests |\n| **Workflow Bypass** | Skipping required steps in a multi-step business process |\n| **Race Condition** | Exploiting concurrent request processing to violate business constraints |\n| **Privilege Escalation** | Gaining higher permissions through business process manipulation |\n| **Negative Testing** | Testing with unexpected values (negative, zero, null, extreme) |\n| **State Manipulation** | Changing application state in an order not intended by the business logic |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| **Burp Suite Professional** | Request interception, modification, and sequence testing |\n| **Burp Turbo Intruder** | High-speed request sending for race condition testing |\n| **Burp Sequencer** | Token randomness analysis for predictable reference testing |\n| **OWASP ZAP** | Open-source alternative for proxy-based testing |\n| **Postman** | Workflow testing with collection runners and environment variables |\n| **Custom scripts** | Python\u002Fbash scripts for automated business logic testing |\n\n## Common Scenarios\n\n### Scenario 1: Coupon Code Stacking\nAn e-commerce site allows applying multiple coupon codes. By stacking \"WELCOME10\", \"SAVE20\", and \"VIP30\", the total discount exceeds the product price, resulting in a negative balance or free order.\n\n### Scenario 2: Race Condition on Fund Transfer\nA banking application checks balance before transfer but does not lock the account. Sending two simultaneous $1000 transfers from a $1000 balance results in both succeeding, creating money from nothing.\n\n### Scenario 3: Checkout Price Override\nThe checkout flow sends the total amount in the POST body. Intercepting and changing the total from $499.99 to $0.01 results in a successful order at the manipulated price.\n\n### Scenario 4: Password Reset Token Reuse\nThe password reset flow generates a one-time token but does not invalidate it after use. The same token can be used repeatedly to reset the password.\n\n## Output Format\n\n```\n## Business Logic Vulnerability Finding\n\n**Vulnerability**: Price Manipulation in Checkout Flow\n**Severity**: Critical (CVSS 9.1)\n**Location**: POST \u002Fapi\u002Fcheckout - `total` parameter\n**OWASP Category**: A04:2021 - Insecure Design\n\n### Reproduction Steps\n1. Add item to cart (price: $499.99)\n2. Proceed to checkout\n3. Intercept POST \u002Fapi\u002Fcheckout request in Burp\n4. Modify \"total\" from 499.99 to 0.01\n5. Forward the request; order completes at $0.01\n\n### Business Rules Violated\n| Rule | Expected | Actual |\n|------|----------|--------|\n| Server-side price calculation | Total computed server-side | Client-submitted total accepted |\n| Coupon single use | One coupon per order | Same coupon applied 5 times |\n| Negative quantity check | Quantity >= 1 | Quantity -1 accepted (credit issued) |\n| Race condition on transfer | Balance checked atomically | Dual transfer exceeded balance |\n\n### Impact\n- Financial loss: orders processed at attacker-controlled prices\n- Inventory loss: products shipped for $0.01\n- Reward abuse: unlimited referral credits via self-referral\n- Double-spending via race condition on transfers\n\n### Recommendation\n1. Perform all price calculations server-side; never trust client-submitted totals\n2. Implement server-side validation for quantity (positive integers only)\n3. Use database-level locks or atomic transactions for financial operations\n4. Implement idempotency keys to prevent duplicate transaction processing\n5. Rate-limit and log coupon applications, referral submissions, and transfers\n```\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"mitre_attack":41},[26,27,28,29,30,31],"penetration-testing","business-logic","owasp","web-security","burpsuite","manual-testing","mahipal","cybersecurity","1.0",[36,37,38,39],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[42,43,44,45,46],"T1190","T1059.007","T1505.003","T1083","T1068","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Ftesting-for-business-logic-vulnerabilities","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add NeelakshSaxena\u002FVayu --skill testing-for-business-logic-vulnerabilities",{"tool":60,"command":61},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill testing-for-business-logic-vulnerabilities",{"tool":63,"command":64},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill testing-for-business-logic-vulnerabilities","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-business-logic-vulnerabilities\u002FSKILL.md",true,[68,72,78],{"path":69,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fapi-reference.md","REFERENCE","参考文档",1847,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-business-logic-vulnerabilities\u002Freferences\u002Fapi-reference.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fagent.py","SCRIPT","脚本",9219,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-for-business-logic-vulnerabilities\u002Fscripts\u002Fagent.py",[85,92,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]