CoreWCF: Authentication bypass in CoreWCF SAML 1.1 / 2.0 token signature validation
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-xjr9-gg9q-jx3v | CoreWCF: Authentication bypass in CoreWCF SAML 1.1 / 2.0 token signature validation |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.414% 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, CoreWCF SAML 1.1 and SAML 2.0 token validation does not correctly resolve the issuer signing key or require signed tokens when IdentityConfiguration is used with federated bindings, allowing an unauthenticated remote attacker to impersonate any principal the trusted STS could issue. This issue is fixed in versions 1.8.1 and 1.9.1. | |
| Title | CoreWCF: Authentication bypass in CoreWCF SAML 1.1 / 2.0 token signature validation | |
| Weaknesses | CWE-290 CWE-347 |
|
| References |
|
|
| Metrics |
cvssV3_1
|