2026-09-10 · 6 min read · Rahul Chitturi
- xml
- signatures
- security
An XML signature can verify one element while application code reads a different element with the same familiar name. An attacker may move the signed node and insert an unsigned replacement where a broad XPath, first-match lookup, or serializer expects business data.
This signature-wrapping class is a node-selection failure, not proof that the cryptographic primitive broke. Successful verification matters only when the application consumes the exact node covered by the accepted reference.
Trace reference and application selection
In an isolated synthetic fixture, record how the XML signature library resolves each Reference URI, recognizes ID attributes, applies transforms, and returns verified nodes. Then trace the separate query used for authorization, identity, amount, or destination fields.
- Reject duplicate IDs before reference resolution.
- Bind namespace prefixes to exact namespace URIs.
- Avoid descendant-wide and first-element searches for signed data.
- Confirm the expected document root and signature location.
Consume only verified structure
Use a maintained XMLDSig implementation with a constrained profile: expected algorithms, reference count and targets, transform set, key trust, and schema. Obtain the application object from the verified element or verify the preselected expected element by identity.
Do not copy values from another parse tree or rerun an ambiguous XPath after verification. Preserve parser settings and namespace semantics between validation and business logic.
Use Flashman only for structural inspection
Use the XML formatter on synthetic documents to reveal nesting, diff to compare safe node layouts, hash for non-secret fixture labels, and Base64 for disposable encoded values. Flashman's client-side tools do not verify XML signatures or establish key trust.
Verify real signatures in trusted server-side code, and never paste private keys, production assertions, customer documents, or live credentials into browser tools. Test wrapping variants, duplicate IDs, namespace changes, extra signatures, unsupported transforms, and schema-invalid placement.