Multiple WSO2 products vulnerable to perform user impersonatoin using JIT provisioning
CVE-2023-6837GHSA-f6jm-9pr8-9c3w
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.wso2.identity.apps:authentication-portal 1.6.179.1; org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework 5.20.254), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.wso2.identity.apps:authentication-portal
- Affected
- < 1.6.179.1
- Fixed in
- 1.6.179.1
Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework
- Affected
- < 5.20.254
- Fixed in
- 5.20.254
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f6jm-9pr8-9c3w lists affected ranges: Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework >=0 =0 <1.6.179.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- EPSS
- CVE-2023-6837: 0.46% estimated exploitation activity in the next 30 days; percentile 39.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-f6jm-9pr8-9c3w
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-6837 Advisory: Multiple WSO2 products vulnerable to perform user impersonatoin using JIT provisioning IDs: CVE-2023-6837, GHSA-f6jm-9pr8-9c3w Record: https://patchnext.com/advisories/cve-2023-6837 (revision 1, source checked 26 Oct 2026, 16:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.wso2.identity.apps:authentication-portal 1.6.179.1; org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework 5.20.254. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.wso2.identity.apps:authentication-portal: affected < 1.6.179.1; fixed in 1.6.179.1 - Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework: affected < 5.20.254; fixed in 5.20.254 ## Suggested inspection (read-only) - Maven org.wso2.identity.apps:authentication-portal: check the installed version with your package manager. - Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.wso2.identity.apps:authentication-portal, org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-f6jm-9pr8-9c3w (GitHub-reviewed advisory GHSA-f6jm-9pr8-9c3w lists affected ranges: Maven org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework >=0 =0 <1.6.179.1) Commands are suggestions: review each one before running it.
Loading voting…