User impersonation via first-signature validation
Published Feb 18, 2025 · Updated Feb 18, 2025
Improper authentication in SPID.AspNetCore.Authentication before 3.4.0 allows remote attackers to impersonate SPID or CIE users. VerifySignature in XmlHelpers.cs loads only the first XML signature and never confirms that its reference covers the root SAML response. A signed XML element from public IdP metadata therefore lets an unauthenticated attacker alter the assertion accepted for a service-provider session.
Summary
What happened
Improper authentication in SPID.AspNetCore.Authentication before 3.4.0 allows remote attackers to impersonate SPID or CIE users. VerifySignature in XmlHelpers.cs loads only the first XML signature and never confirms that its reference covers the root SAML response. A signed XML element from public IdP metadata therefore lets an unauthenticated attacker alter the assertion accepted for a service-provider session.
The record
- CVE
- CVE-2025-24894
- Published
- Feb 18, 2025
- Updated
- Feb 18, 2025
- Vendor
- Developers Italia
- Product
- SPID.AspNetCore.Authentication
- Classifications
- CWE-287, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Feb 18, 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=< 3.4.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
- Upstream SAML signature-wrapping proof of conceptfunctional · demonstrated
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