CoreWCF: SamlSerializer skips SignatureValue verification when SAML signing token is not an X.509 certificate
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CoreWCF | CoreWCF | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Corewcf | Corewcf |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rpj7-hr7h-w6p9 | CoreWCF: SamlSerializer skips SignatureValue verification when SAML signing token is not an X.509 certificate |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.203% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Corewcf
Corewcf corewcf |
|
| Vendors & Products |
Corewcf
Corewcf corewcf |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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, SamlSerializer skips final SignatureValue verification when a CoreWCF service validates SAML tokens using a non-X.509 signing token, allowing an attacker to reference a non-X.509 SecurityToken key identifier and bypass assertion signature verification. This issue is fixed in versions 1.8.1 and 1.9.1. | |
| Title | CoreWCF: SamlSerializer skips SignatureValue verification when SAML signing token is not an X.509 certificate | |
| Weaknesses | CWE-345 CWE-347 |
|
| References |
|
|
| Metrics |
cvssV3_1
|