Total
6 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2024-42337 | 1 Cyberark | 1 Identity | 2024-08-30 | N/A | 6.5 MEDIUM |
CyberArk - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor | |||||
CVE-2024-42338 | 1 Cyberark | 1 Identity | 2024-08-30 | N/A | 4.3 MEDIUM |
CyberArk - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor | |||||
CVE-2024-42340 | 1 Cyberark | 1 Identity | 2024-08-30 | N/A | 4.3 MEDIUM |
CyberArk - CWE-602: Client-Side Enforcement of Server-Side Security | |||||
CVE-2024-42339 | 1 Cyberark | 1 Identity | 2024-08-30 | N/A | 4.3 MEDIUM |
CyberArk - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor | |||||
CVE-2022-22700 | 1 Cyberark | 1 Identity | 2024-02-28 | 5.0 MEDIUM | 5.3 MEDIUM |
CyberArk Identity versions up to and including 22.1 in the 'StartAuthentication' resource, exposes the response header 'X-CFY-TX-TM'. In certain configurations, that response header contains different, predictable value ranges which can be used to determine whether a user exists in the tenant. | |||||
CVE-2021-37151 | 1 Cyberark | 1 Identity | 2024-02-28 | 5.0 MEDIUM | 5.3 MEDIUM |
CyberArk Identity 21.5.131, when handling an invalid authentication attempt, sometimes reveals whether the username is valid. In certain authentication policy configurations with MFA, the API response length can be used to differentiate between a valid user and an invalid one (aka Username Enumeration). Response differentiation enables attackers to enumerate usernames of valid application users. Attackers can use this information to leverage brute-force and dictionary attacks in order to discover valid account information such as passwords. |