Arbitrary-user authentication via unsigned assertion selection
Published May 19, 2025 · Updated May 20, 2025
Improper SAML signature verification in samlify before 2.10.0 allows remote attackers to authenticate as any user with a crafted response. The verifySignature routine validates one signed XML reference but previously returned an assertion selected separately from the original document, allowing wrapped unsigned content to be trusted. Exploitation requires a signed XML document from the identity provider and grants unauthorized access as any represented user.
Summary
What happened
Improper SAML signature verification in samlify before 2.10.0 allows remote attackers to authenticate as any user with a crafted response. The verifySignature routine validates one signed XML reference but previously returned an assertion selected separately from the original document, allowing wrapped unsigned content to be trusted. Exploitation requires a signed XML document from the identity provider and grants unauthorized access as any represented user.
The record
- CVE
- CVE-2025-47949
- Published
- May 19, 2025
- Updated
- May 20, 2025
- Vendor
- Tony Ngan
- Product
- samlify
- Classifications
- CWE-347, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo