Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2021-4314 | First vendor Publication | 2023-01-18 |
| Vendor | Cve | Last vendor Modification | 2023-01-26 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | |||
|---|---|---|---|
| Overall CVSS Score | 5.3 | ||
| Base Score | 5.3 | Environmental Score | 5.3 |
| impact SubScore | 1.4 | Temporal Score | 5.3 |
| Exploitabality Sub Score | 3.9 | ||
| Attack Vector | Network | Attack Complexity | Low |
| Privileges Required | None | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | Low | Availability Impact | None |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| It is possible to manipulate the JWT token without the knowledge of the JWT secret and authenticate without valid JWT token as any user. This is happening only in the situation when zOSMF doesn’t have the APAR PH12143 applied. This issue affects: 1.16 versions to 1.19. What happens is that the services using the ZAAS client or the API ML API to query will be deceived into believing the information in the JWT token is valid when it isn’t. It’s possible to use this to persuade the southbound service that different user is authenticated. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4314 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-287 | Improper Authentication |
Sources (Detail)
| Source | Url |
|---|---|
| MISC | https://github.com/zowe/api-layer/ |
Alert History
| Date | Informations |
|---|---|
| 2023-01-26 21:27:21 |
|
| 2023-01-19 00:27:16 |
|
