Skip to content

Multiple WSO2 products vulnerable to perform user impersonatoin using JIT provisioning

High severity GitHub Reviewed Published Dec 15, 2023 to the GitHub Advisory Database • Updated May 17, 2024

Package

maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework (Maven)

Affected versions

< 5.20.254

Patched versions

5.20.254
maven org.wso2.identity.apps:authentication-portal (Maven)
< 1.6.179.1
1.6.179.1

Description

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.

References

Published by the National Vulnerability Database Dec 15, 2023
Published to the GitHub Advisory Database Dec 15, 2023
Reviewed Jan 5, 2024
Last updated May 17, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(54th percentile)

Weaknesses

No CWEs

CVE ID

CVE-2023-6837

GHSA ID

GHSA-f6jm-9pr8-9c3w

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.