Saml2 Authentication services for ASP.NET up to 1.0.1/2.6.x Token incorrect implementation of authentication algorithm
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Saml2 Authentication services for ASP.NET up to 1.0.1/2.6.x. Impacted is an unknown function of the component Token Handler. The manipulation results in incorrect implementation of authentication algorithm. This vulnerability is known as CVE-2020-5268. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Saml2 Authentication services for ASP.NET up to 1.0.1/2.6.x. Affected is some unknown functionality of the component Token Handler. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. CWE is classifying the issue as CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In Saml2 Authentication Services for ASP.NET before versions 2.7.0 and 1.0.2, there is a vulnerability in how tokens are validated in some cases. Saml2 tokens are usually used as bearer tokens - a caller that presents a token is assumed to be the subject of the token. There is also support in the Saml2 protocol for issuing tokens that is tied to a subject through other means, e.g. holder-of-key where possession of a private key must be proved. The Sustainsys.Saml2 library incorrectly treats all incoming tokens as bearer tokens, even though they have another subject confirmation method specified. This could be used by an attacker that could get access to Saml2 tokens with another subject confirmation method than bearer. The attacker could then use such a token to create a log in session. This vulnerability is patched in versions 1.0.2 and 2.7.0.
The weakness was published 04/21/2020 (GitHub Repository). The advisory is available at github.com. This vulnerability is traded as CVE-2020-5268 since 01/02/2020. The exploitability is told to be difficult. It is possible to launch the attack remotely. A authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
Upgrading to version 1.0.2 or 2.7.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Incorrect implementation of authentication algorithmCWE: CWE-303
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Saml2 Authentication services for ASP.NET 1.0.2/2.7.0
Patch: github.com
Timeline
01/02/2020 🔍04/21/2020 🔍
04/22/2020 🔍
05/06/2025 🔍
Sources
Advisory: e58e0a1aff2b1ead6aca080b7cdced55ee6d5241Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-5268 (🔍)
GCVE (CVE): GCVE-0-2020-5268
GCVE (VulDB): GCVE-100-154170
Entry
Created: 04/22/2020 10:13Updated: 05/06/2025 15:44
Changes: 04/22/2020 10:13 (38), 04/22/2020 10:18 (11), 10/10/2020 20:09 (1), 10/10/2020 20:12 (1), 06/01/2024 12:03 (18), 06/01/2024 12:11 (18), 05/06/2025 15:44 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.