dbcve.org
Api ManagerApplication · Wso2

CVE-2023-6837

HIGH · 8.2 CVSS v3.1 Published 2023-12-15
Fix available
A fix is available. Upgrade to 2.5.0.32 / 2.6.0.52 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple WSO2 products contain a user impersonation vulnerability in the JIT provisioning flow. When an IDP is configured with federated authentication and JIT provisioning using the 'Prompt for username, password and consent' option, and a service provider uses 'Assert identity using mapped local subject identifier', an attacker with a fresh federated IDP account and knowledge of a local username can impersonate that user by hijacking the JIT provisioning process.

MitigationDisable JIT provisioning on affected IDPs, or change the JIT provisioning option away from 'Prompt for username, password and consent', or disable 'Assert identity using mapped local subject identifier' on service providers. Review federated authentication configurations to ensure at least one required precondition is removed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api ManagerApplication
Affected:>= 2.5.0, < 2.5.0.32>= 2.6.0, < 2.6.0.52>= 3.0.0, < 3.0.0.50>= 3.1.0, < 3.1.0.72>= 3.2.0, < 3.2.0.86>= 4.0.0, < 4.0.0.35
Identity ServerApplication
Affected:>= 5.6.0, < 5.6.0.16>= 5.7.0, < 5.7.0.35>= 5.8.0, < 5.8.0.26>= 5.9.0, < 5.9.0.38>= 5.10.0, < 5.10.0.78>= 5.11.0, < 5.11.0.69
Identity Server As Key ManagerApplication
Affected:>= 5.6.0, < 5.6.0.17>= 5.7.0, < 5.7.0.39>= 5.9.0, < 5.9.0.45>= 5.10.0, < 5.10.0.80
Carbon Identity Application Authentication EndpointApplication
Affected:< 5.11.256.3>= 5.11.257.0, < 5.12.153.19>= 5.12.154.0, < 5.20.254
Carbon Identity Application Authentication FrameworkApplication
Affected:< 5.11.256.3>= 5.11.257.0, < 5.12.153.21>= 5.12.154.0, < 5.12.387.7>= 5.12.388.0, < 5.14.97.22>= 5.14.98.0, < 5.17.5.106>= 5.17.6.0, < 5.18.187.76>= 5.18.188.0, < 5.20.254

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WSO2 product and version
    Check the product version from the WSO2 installation. For WSO2 Identity Server, this is typically found in the product's about page or in the <product>/repository/conf/info/registry.xml or by examining the product banner at startup. For API Manager, check the <AM_HOME>/repository/conf/pom.xml or the management console.
    Affected if The installed version falls within any of the affected version ranges listed for the product.
  2. Review Identity Provider configurations for federated authentication
    Access the WSO2 management console, navigate to Identity Providers section, and list all configured Identity Providers. Check each IDP to determine if federated authentication is enabled.
    Affected if Any Identity Provider is configured with federated authentication.
  3. Check if any federated IDP has JIT provisioning enabled
    In the Identity Provider configuration, examine the Just-In-Time Provisioning settings for each federated IDP. Verify if JIT provisioning is enabled and identify which option is selected.
    Affected if JIT provisioning is enabled on a federated IDP using the 'Prompt for username, password and consent' option.
  4. Review Service Provider configurations for mapped local subject
    Access the WSO2 management console, navigate to Service Providers section, and review the local and outbound authentication configuration for each SP. Check if 'Assert identity using mapped local subject identifier' is enabled.
    Affected if Any Service Provider is configured with 'Assert identity using mapped local subject identifier' enabled.

A user is affected if the installed WSO2 product version is within the affected ranges AND an IDP is configured with federated authentication AND JIT provisioning is set to 'Prompt for username, password and consent' AND a service provider uses 'Assert identity using mapped local subject identifier'.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.0.32 / 2.6.0.52 / 3.0.0.50 or later
Fixed in 2.5.0.322.6.0.523.0.0.50
Interim mitigation

Disable JIT provisioning on affected IDPs, or change the JIT provisioning option away from 'Prompt for username, password and consent', or disable 'Assert identity using mapped local subject identifier' on service providers. Review federated authentication configurations to ensure at least one required precondition is removed.

Recommended fix High confidence

Upgrade to the latest fixed version in your release branch: Api Manager 2.5.0.32/2.6.0.52/3.0.0.50/3.1.0.72; Identity Server 5.6.0.16/5.7.0.35/5.8.0.26/5.9.0.38; Identity Server As Key Manager 5.6.0.17/5.7.0.39/5.9.0.45/5.10.0.80; Carbon Identity Application Authentication Endpoint 5.11.256.3/5.12.1

  1. 1. Identify the specific WSO2 product (Api Manager, Identity Server, Identity Server As Key Manager, Carbon Identity Application Authentication Endpoint, or Carbon Identity Application Authentication Framework) running in your environment.
  2. 2. Determine the current installed version using the product's administration console or command-line tools.
  3. 3. Based on the product and current version, upgrade to the corresponding fixed version: For Api Manager upgrade to 2.5.0.32 (for 2.5.x), 2.6.0.52 (for 2.6.x), 3.0.0.50 (for 3.0.x), or 3.1.0.72 (for 3.1.x). For Identity Server upgrade to 5.6.0.16 (for 5.6.x), 5.7.0.35 (for 5.7.x), 5.8.0.26 (for 5.8.x), or 5.9.0.38 (for 5.9.x). For Identity Server As Key Manager upgrade to 5.6.0.17 (for 5.6.x), 5.7
  4. 4. After upgrade, verify the JIT provisioning configuration in affected Identity Providers to ensure security settings are appropriate.
  5. 5. Test the federated authentication flow to confirm normal operation after the upgrade.
Caveat Standard upgrade considerations apply - review release notes for your specific version jump for any behavioral changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6837 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6837 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data