--- name: testing-mobile-api-authentication description: 'Tests authentication and authorization mechanisms in mobile application APIs to identify broken authentication, insecure token management, session fixation, privilege escalation, and IDOR vulnerabilities. Use when performing API security assessments against mobile app backends, testing JWT implementations, evaluating OAuth flows, or assessing session management. Activates for requests involving mobile API auth testing, token security assessment, OAuth mobile flow testing, or API authorization bypass. ' domain: cybersecurity subdomain: mobile-security author: mahipal tags: - mobile-security - android - ios - api-security - authentication - penetration-testing version: 1.0.0 license: Apache-2.0 nist_csf: - PR.PS-01 - PR.AA-05 - ID.RA-01 - DE.CM-09 mitre_attack: - T1059 - T1056 - T1036 - T1078 - T1068 --- # Testing Mobile API Authentication ## When to Use Use this skill when: - Assessing mobile app backend API authentication during penetration tests - Testing JWT token implementation for common vulnerabilities (none algorithm, weak signing) - Evaluating OAuth 2.0 / OIDC flows in mobile applications for redirect, PKCE, and scope issues - Testing for broken object-level authorization (BOLA/IDOR) in API endpoints **Do not use** this skill against production APIs without explicit authorization and rate-limiting awareness. ## Prerequisites - Burp Suite or mitmproxy configured as mobile device proxy - SSL pinning bypassed on target application (if implemented) - Valid test account credentials for the target application - Postman or curl for API request crafting - jwt.io or PyJWT for JWT analysis and manipulation ## Workflow ### Step 1: Map Authentication Endpoints Intercept mobile app traffic to identify authentication-related endpoints: ``` POST /api/v1/auth/login - Initial authentication POST /api/v1/auth/register - Account registration POST /api/v1/auth/refresh - Token refresh POST /api/v1/auth/logout - Session termination POST /api/v1/auth/forgot-password - Password reset POST /api/v1/auth/verify-otp - OTP verification GET /api/v1/auth/me - Authenticated user profile ``` ### Step 2: Analyze Token Format and Security **JWT Analysis:** ```bash # Decode JWT without verification echo "eyJhbGciOiJIUzI1NiIs..." | cut -d. -f2 | base64 -d 2>/dev/null # Check for common JWT vulnerabilities: # 1. None algorithm attack # Change header to: {"alg":"none","typ":"JWT"} # Remove signature: header.payload. # 2. Algorithm confusion (RS256 to HS256) # If server uses RS256, try HS256 with public key as secret # 3. Weak signing key # Use hashcat or jwt-cracker to brute-force HMAC secret hashcat -m 16500 jwt.txt wordlist.txt # 4. Expiration bypass # Modify "exp" claim to future timestamp ``` **Opaque Token Analysis:** ``` - Test token length and entropy - Check if tokens are sequential/predictable - Test token reuse after logout - Verify token invalidation on password change ``` ### Step 3: Test Authentication Bypass ```bash # Test missing authentication curl -X GET https://api.target.com/api/v1/users/profile # Test with empty/null token curl -X GET https://api.target.com/api/v1/users/profile \ -H "Authorization: Bearer " curl -X GET https://api.target.com/api/v1/users/profile \ -H "Authorization: Bearer null" # Test with expired token (should fail) curl -X GET https://api.target.com/api/v1/users/profile \ -H "Authorization: Bearer " # Test token from different user curl -X GET https://api.target.com/api/v1/users/123/profile \ -H "Authorization: Bearer " ``` ### Step 4: Test IDOR / Broken Object-Level Authorization ```bash # Change user ID in request path curl -X GET https://api.target.com/api/v1/users/123/orders \ -H "Authorization: Bearer " # Change object ID in request body curl -X PUT https://api.target.com/api/v1/orders/789 \ -H "Authorization: Bearer " \ -d '{"status": "cancelled"}' # Test horizontal privilege escalation # Access admin endpoints with regular user token curl -X GET https://api.target.com/api/v1/admin/users \ -H "Authorization: Bearer " ``` ### Step 5: Test Session Management ```bash # Test concurrent sessions # Login from multiple devices simultaneously - should both remain valid? # Test session invalidation after logout TOKEN=$(curl -s -X POST https://api.target.com/api/v1/auth/login \ -d '{"email":"test@test.com","password":"pass"}' | jq -r '.token') # Logout curl -X POST https://api.target.com/api/v1/auth/logout \ -H "Authorization: Bearer $TOKEN" # Try using the same token (should fail) curl -X GET https://api.target.com/api/v1/users/me \ -H "Authorization: Bearer $TOKEN" # Test session invalidation after password change # Token obtained before password change should be invalidated ``` ### Step 6: Test OAuth 2.0 / OIDC Mobile Flows ```bash # Test for authorization code interception # Check if PKCE (Proof Key for Code Exchange) is enforced # Test with missing code_verifier parameter # Test redirect URI manipulation # Try custom scheme hijacking: myapp://callback # Test with modified redirect_uri parameter # Test scope escalation # Request higher privileges than granted ``` ## Key Concepts | Term | Definition | |------|-----------| | **BOLA/IDOR** | Broken Object Level Authorization - accessing resources by changing identifiers without server-side authorization checks | | **JWT** | JSON Web Token - self-contained authentication token with header, payload, and signature components | | **PKCE** | Proof Key for Code Exchange - OAuth 2.0 extension preventing authorization code interception in mobile apps | | **Token Refresh** | Mechanism for obtaining new access tokens using long-lived refresh tokens without re-authentication | | **Session Fixation** | Attack where adversary sets a known session ID before victim authenticates, then hijacks the session | ## Tools & Systems - **Burp Suite**: HTTP proxy for intercepting and modifying authentication requests - **jwt_tool**: Python tool for testing JWT vulnerabilities (none algorithm, key confusion, claim manipulation) - **Postman**: API testing client for crafting authentication requests - **hashcat**: Password/JWT secret cracking tool for testing HMAC signing key strength - **Autorize**: Burp Suite extension for automated authorization testing ## Common Pitfalls - **Rate limiting masks issues**: API may rate-limit test requests. Use delays between requests and test from the tester's authorized perspective first. - **Token in URL**: Some mobile APIs pass tokens in URL query parameters, exposing them in server logs and browser history. Flag as finding even if authorization works correctly. - **Refresh token rotation**: Some APIs rotate refresh tokens on each use. If your test invalidates the refresh token, you may lock out your test account. - **Mobile-specific OAuth**: Mobile apps use custom URI schemes for OAuth redirects, which can be intercepted by malicious apps registered for the same scheme. --- Source attribution: mukul975 Original project: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/testing-mobile-api-authentication/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: mukul975 Original project: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/testing-mobile-api-authentication/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Mobile Developer, QA / Test Engineer, Security Engineer Specialties: API, Mobile, Testing Tools: Pyjwt, Burp Suite, Curl, Mitmproxy, Postman, Jwt.Io Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 41a67ba95bc2508d236d99dd056e96fdec843abec9efa4602cb9c8dfe20d3fc8