WSO2 API Manager/Identity Server/IS as Key Manager JIT Provisioning improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in WSO2 API Manager, Identity Server and IS as Key Manager. This affects an unknown part of the component JIT Provisioning. Such manipulation leads to improper authentication. This vulnerability is uniquely identified as CVE-2023-6837. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in WSO2 API Manager, Identity Server and IS as Key Manager (Automation Software) (unknown version) and classified as critical. Affected by this issue is an unknown code block of the component JIT Provisioning. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Multiple WSO2 products have been identified as vulnerable to perform user impersonatoin using JIT provisioning. In order for this vulnerability to have any impact on your deployment, following conditions must be met: * An IDP configured for federated authentication and JIT provisioning enabled with the "Prompt for username, password and consent" option. * A service provider that uses the above IDP for federated authentication and has the "Assert identity using mapped local subject identifier" flag enabled. Attacker should have: * A fresh valid user account in the federated IDP that has not been used earlier. * Knowledge of the username of a valid user in the local IDP. When all preconditions are met, a malicious actor could use JIT provisioning flow to perform user impersonation.
The weakness was disclosed 12/15/2023. The advisory is available at security.docs.wso2.com. This vulnerability is handled as CVE-2023-6837 since 12/15/2023. The technical details are unknown and an exploit is not available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-3194). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.2
NVD Vector: 🔍
CNA Base Score: 8.5
CNA Vector (WSO2): 🔍
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: Improper authenticationCWE: CWE-287
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: 🔍
Timeline
12/15/2023 🔍12/15/2023 🔍
12/15/2023 🔍
06/05/2025 🔍
Sources
Advisory: security.docs.wso2.comStatus: Confirmed
CVE: CVE-2023-6837 (🔍)
GCVE (CVE): GCVE-0-2023-6837
GCVE (VulDB): GCVE-100-248162
EUVD: 🔍
Entry
Created: 12/15/2023 12:25Updated: 06/05/2025 18:02
Changes: 12/15/2023 12:25 (48), 01/11/2024 12:37 (12), 06/05/2025 16:00 (16), 06/05/2025 18:02 (1)
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.