CVE-2024-1524

A local user can be impersonated when using federated authentication with Silent JIT Provisioning.

HIGH
8.1
CVSS Score
Published: February 24, 2026 at 08:51 AM UTC
Updated: June 17, 2026 at 07:04 AM UTC
2 products affected across 1 vendorAPI ManagerIdentity Server

Using WSO2 API Manager by WSO2?

Get instant alerts when new vulnerabilities affect WSO2 API Manager - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

When the "Silent Just-In-Time Provisioning" feature is enabled for a federated identity provider (IDP) there is a risk that a local user store user's information may be replaced during the account provisioning process in cases where federated users share the same username as local users. There will be no impact on your deployment if any of the preconditions mentioned below are not met. Only when all the preconditions mentioned below are fulfilled could a malicious actor associate a targeted local user account with a federated IDP user account that they control. The Deployment should have: -An IDP configured for federated authentication with Silent JIT provisioning enabled. The malicious actor 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. -An account at the federated IDP matching the targeted local username.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2.0 ≤ v < 4.2.0.1084.2.0
Affected range stops below 4.2.0.108, so it looks safe — our inference, not a vendor statement
6.0.0 ≤ v < 6.0.0.1716.1.0 ≤ v < 6.1.0.1286.0.06.1.0
Affected range stops below 6.0.0.171, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.0.128, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-290

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card