|
| |
| Unisys ID: |
UIS-2022-1 |
| Status: |
Published |
| CVE-ID: |
CVE-2022-32555 |
| Affected Product: |
Data Exchange |
| Affected Version: |
6.0.IC1, 7.0 and earlier versions |
| Impact: |
HIGH |
| CVSS v3.1 Base Score: |
8.8 |
| CVSS v3.1 Vector: |
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
v3 Calculator |
| CVSS v2.0 Base Score: |
6.4 |
| CVSS v2.0 Vector: |
AV:N/AC:L/Au:S/C:P/I:P/A:P
v2 Calculator |
| CVSS Temporal Score: |
5.7 |
| Common Weakness Enumeration (CWE):  |
352 |
| Common Platform Enumeration (CPE):  |
cpe:2.3:a:unisys:data_exchange:7.0.24:*:*:*:*:*:*:* |
| Source: |
Client Reported |
| Keyword(s): |
CSRF, DEMS |
| Vulnerability Description: |
| Data Exchange Management Studio doesn't have an Anti-CSRF token to authenticate the POST request, which could be used for a cross-site request forgery attack. |
| System Configuration: |
| Data Exchange 6.0.IC1 (6.0.42), 7.0 and earlier versions |
| Impact of Exploiting Vulnerability: |
| If the vulnerability is triggered (which requires an additional vector), the attacker may be able to modify the user/role/environment. The likelihood of compromise can be decreased significantly by having only required users have access to the DEMS application within the client environment. |
| Remediation Description: |
| Data Exchange 7.0.IC1 (7.0.27) have the samesite(strict) attribute and the anti-CSRF tokens added for the POST request to DEMS. |
| Workaround Information: |
| Not available. |
| References: |
| PLE 19332845 |
| Additional Vendor Comment: |
|