Hacking SAML - #2727
Open
carlospolop wants to merge 1 commit into
Open
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://oblique.security/blog/hacking-saml Content Categories: Based on the analysis, this content was categorized under "Pentesting Web > SAML Attacks; optionally cross-reference Generic Methodologies & Resources > AI Security > AI Assisted Fuzzing And Vulnerability Discovery". 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
Overview
The post describes an AI-assisted security review of SAML implementations that discovered full authentication bypasses, XML-signature wrapping vulnerabilities, identity-parsing differentials, information disclosure, arbitrary logout, and unauthenticated denial-of-service conditions. The core recurring failure is that XML canonicalization, signature verification, XML parsing, and application-level node selection can interpret the same document differently. A signature verifier...
🔧 Technical Details
Canonicalization-versus-parser differentials: Compare how the canonicalizer, XML-signature library, general XML parser, and application extractor interpret processing instructions, comments, text nodes, namespaces, and mixed content. A vulnerability exists when attacker-controlled XML contributes data to the canonicalized signed representation but is ignored or reconstructed differently during account lookup. For example,
<saml:NameID><?p not-an-?>admin@example.com</saml:NameID>can be verified as the signed identitynot-an-admin@example.comwhile application text extraction returnsadmin@example.com.XML comment identity manipulation: Insert comments at different positions inside identity-bearing fields such as
NameID, then compare the exact string authenticated by signature validation with the string used for user lookup. If one path concatenates text around the comme...🤖 Agent Actions
Updated
src/pentesting-web/saml-attacks/README.mdwith:AuthnRequest,AttributeQuery, andLogoutRequest.Validation completed:
git diff --checkpassed.mdbook buildwas unavailable becausemdbookis not installed.This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.