CoreWCF: SAML SubjectConfirmation methods and holder-of-key proof keys are not enforced
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.4epss 0.2%
exploitation probability
0.2%top 92% of all CVEs
observed exploitation
nono source reports it
CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. Prior to 1.8.1 and 1.9.1, CoreWCF SAML token validation does not enforce SubjectConfirmation method URIs or holder-of-key proof keys in SamlSecurityTokenHandler, allowing holder-of-key downgrade or custom confirmation method assertions to authenticate a subject without proving authority over the assertion. This issue is fixed in versions 1.8.1 and 1.9.1.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
CoreWCF · CoreWCFReferences
https://github.com/CoreWCF/CoreWCF/commit/6a99df3242f54acd6f89edfd6050430b72d0c685https://github.com/CoreWCF/CoreWCF/commit/86dd3232b6b8aaf32281be9e8d798afad6145d58https://github.com/CoreWCF/CoreWCF/commit/9eb9b46d1c2af06fb71f656a02f4d5b4649c1f03https://github.com/CoreWCF/CoreWCF/releases/tag/v1.8.1https://github.com/CoreWCF/CoreWCF/releases/tag/v1.9.1https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-48pq-2xq3-c2m4