CVE-2024-1524
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 · uneditedWhen 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.
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 confidenceThis is an account takeover vulnerability in federated identity systems where Silent Just-In-Time (JIT) Provisioning is enabled. When a federated user authenticates with a username matching an existing local user account, the provisioning process can overwrite the local user's stored information with data from the federated IDP, allowing the attacker to gain access to the targeted local account.
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>= 4.2.0, < 4.2.0.108>= 6.0.0, < 6.0.0.171>= 6.1.0, < 6.1.0.128CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed WSO2 product and versionAccess the WSO2 Carbon console or check the product's runtime banner. For API Manager, this is typically accessible via the admin portal. For Identity Server, check the management console. Look for the version number displayed in the UI or runtime information.Affected if The installed version falls within WSO2 API Manager >= 4.2.0 and < 4.2.0.108, or WSO2 Identity Server >= 6.0.0 and < 6.0.0.171, or >= 6.1.0 and < 6.1.0.128.
-
Confirm federated identity providers are configuredNavigate to the identity provider management section in the WSO2 Carbon/Admin console. Review the list of configured identity providers and identify any that use federated authentication protocols such as SAML, OAuth, or OIDC.Affected if Federated identity providers are configured in the environment.
-
Check if Silent JIT Provisioning is enabledIn the identity provider configuration for each federated IdP, locate the Just-In-Time (JIT) Provisioning settings. Specifically verify whether Silent JIT Provisioning (sometimes labeled as 'Enable Silent Provisioning' or similar) is turned ON for any federated identity provider.Affected if Silent JIT Provisioning is enabled for one or more federated identity providers.
-
Assess username collision riskReview the federated identity provider configuration to determine the attribute used as the username in the local user store. Check if this attribute could potentially match existing local user accounts.Affected if The federated username attribute maps to a field that could match locally existing usernames (such as email or userPrincipalName).
A user is affected if they are running a vulnerable WSO2 version, have federated identity providers configured, and have Silent JIT Provisioning enabled, which could allow account takeover via username collision with federated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.2.0.1086.0.0.1716.1.0.128
Disable Silent JIT Provisioning and implement username collision detection/validation before provisioning federated accounts, or ensure usernames used for federation differ from local user stores.
WSO2 Api Manager 4.2.0.108+ or WSO2 Identity Server 6.0.0.171+ / 6.1.0.128+
- 1. Identify the exact WSO2 product and version currently deployed (Api Manager or Identity Server)
- 2. For WSO2 Api Manager: Upgrade to version 4.2.0.108 or later
- 3. For WSO2 Identity Server 6.0.x: Upgrade to version 6.0.0.171 or later
- 4. For WSO2 Identity Server 6.1.x: Upgrade to version 6.1.0.128 or later
- 5. After upgrade, verify the Silent Just-In-Time Provisioning configuration for all federated identity providers
- 6. Review user accounts in the local user store to ensure no unauthorized changes occurred
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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