PingID Desktop up to 2.8 on Windows Username multiple resources with duplicate identifier
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in PingID Desktop up to 2.8 on Windows. Affected by this vulnerability is an unknown functionality of the component Username Handler. This manipulation causes use of multiple resources with duplicate identifier. This vulnerability is registered as CVE-2022-23721. The attack needs to be launched locally. No exploit is available. You should upgrade the affected component.
Details
A vulnerability has been found in PingID Desktop up to 2.8 on Windows and classified as problematic. Affected by this vulnerability is some unknown functionality of the component Username Handler. The manipulation with an unknown input leads to a use of multiple resources with duplicate identifier vulnerability. The CWE definition for the vulnerability is CWE-694. The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required. As an impact it is known to affect availability. The summary by CVE is:
PingID integration for Windows login prior to 2.9 does not handle duplicate usernames, which can lead to a username collision when two people with the same username are provisioned onto the same machine at different times.
The weakness was published 04/25/2023. The advisory is shared at docs.pingidentity.com. This vulnerability is known as CVE-2022-23721 since 01/19/2022. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.9 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-28657). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
NVD Vector: 🔍
CNA Base Score: 3.8
CNA Vector (Ping Identity Corporation): 🔍
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: 🔍
Exploiting
Class: Use of multiple resources with duplicate identifierCWE: CWE-694
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: Desktop 2.9
Timeline
01/19/2022 🔍04/25/2023 🔍
04/25/2023 🔍
04/30/2026 🔍
Sources
Advisory: docs.pingidentity.comStatus: Confirmed
CVE: CVE-2022-23721 (🔍)
GCVE (CVE): GCVE-0-2022-23721
GCVE (VulDB): GCVE-100-227425
EUVD: 🔍
Entry
Created: 04/25/2023 21:47Updated: 04/30/2026 07:40
Changes: 04/25/2023 21:47 (50), 05/20/2023 09:12 (10), 04/30/2026 07:40 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.