How I Found a Critical OAuth Misconfiguration That Led to Ac...#2353
Open
carlospolop wants to merge 1 commit into
Open
How I Found a Critical OAuth Misconfiguration That Led to Ac...#2353carlospolop wants to merge 1 commit into
carlospolop wants to merge 1 commit into
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://medium.com/@iamshafayat/how-i-found-a-critical-oauth-misconfiguration-that-led-to-account-takeover-abfec43eaea6 Content Categories: Based on the analysis, this content was categorized under "Pentesting Web -> OAuth to Account takeover". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
The blog describes a critical OAuth 2.0 misconfiguration chain found during an authorized bug bounty assessment of a self-hosted/internal platform. No CVE is assigned. The impact was full account takeover of authenticated users by chaining exposed OAuth metadata, unauthenticated dynamic OAuth client registration, arbitrary redirect URI acceptance, weak client validation, PKCE abuse in an attacker-controlled flow, wildcard CORS, and normal OAuth consent interaction.
1. Recon...
🔧 Technical Details
OAuth metadata reconnaissance: Check
/.well-known/oauth-authorization-serverfor exposed OAuth server metadata. Useful fields includeauthorization_endpoint,token_endpoint,registration_endpoint,response_types_supported,grant_types_supported,token_endpoint_auth_methods_supported, andcode_challenge_methods_supported. A visibleregistration_endpointindicates dynamic client registration may be available, whiletoken_endpoint_auth_methods_supportedcontainingnoneindicates public-client token exchange may be accepted.Abusing open dynamic OAuth client registration: If an OAuth server exposes
POST /api/v2/oauth/registeror an equivalent dynamic registration endpoint without authentication, an attacker may create a malicious OAuth client. If arbitraryredirect_urisare ac...🤖 Agent Actions
Done.
Updated:
src/pentesting-web/oauth-to-account-takeover.mdAdded:
/.well-known/oauth-authorization-serverregistration_endpointredirect_urisas a malicious-client ATO path## ReferencesValidation:
## Referencesstill exists and banner include remains at endmdbook buildcould not be executed becausemdbookis not installed in this environmentThis PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.