LiveActive security incident?Get immediate response
CVE Record

CVE-2024-1248: Role Overwriting via Silent JIT Provisioning in Multiple WSO2 Products Enables Privilege Escalation

The silent Just-In-Time (JIT) provisioning feature in federated authentication implementations fails to properly segregate user roles during account creation when a federated user shares a username with a local user. This allows the provisioning process to overwrite existing roles of local users with roles assigned to the federated user. Exploitation requires a federated identity provider (IDP) with silent JIT provisioning enabled and an attacker's knowledge of a local user's username. When these conditions are met, a malicious individual can leverage the JIT provisioning process to modify the roles of local users. The overwritten roles are limited to those defined within the federated IDP, typically granting minimal access rights unless explicitly configured otherwise by the federated IDP administrator.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue can let a federated login process overwrite a matching local user's roles in affected WSO2 products. Business impact depends heavily on identity-provider configuration. The published CVSS score is medium, and the source bundle says overwritten roles are usually minimal unless the federated IDP is configured to grant more.

Executive priority

Treat as a targeted identity-configuration risk, not an internet-wide emergency. Prioritize review for WSO2 identity or API environments using federated login and silent JIT provisioning, especially where IDP role mappings can grant meaningful access.

Technical view

Affected WSO2 products using federated authentication with silent JIT provisioning may fail to segregate roles when a federated user shares a username with a local user. An unauthenticated attacker needs knowledge of a local username and a configured federated IDP. Impact is limited integrity and availability per CVSS 4.8.

Likely exposure

Exposure is limited to listed WSO2 products and versions where federated authentication uses silent JIT provisioning. Environments without silent JIT provisioning, without federated IDPs, or without username collisions are less likely to be practically exposed based on the provided description.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. Exploitation requires a federated IDP with silent JIT provisioning enabled and knowledge of a local username. Role changes are constrained to roles available from the federated IDP configuration.

Researcher notes

The key control point is the interaction between local usernames, federated usernames, silent JIT provisioning, and IDP role mapping. The bundle does not provide exploit proof, patch version details, or evidence of exploitation, so validation should focus on configuration and account-collision conditions.

Mitigation direction

  • Review WSO2-2024-3179 and apply vendor-provided updates or configuration guidance.
  • Disable or restrict silent JIT provisioning where it is not required.
  • Limit federated IDP role assignments to the minimum required roles.
  • Reduce username collision risk between federated users and sensitive local accounts.

Validation and detection

  • Inventory affected WSO2 products and versions listed in the advisory.
  • Check whether federated authentication and silent JIT provisioning are enabled.
  • Review federated IDP role mappings for privileged or operationally sensitive roles.
  • Look for local usernames that could collide with federated identities.
  • Audit recent role changes for unexpected overwrites on local accounts.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-298: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-1248 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L2.22.5WSO2

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2024-1248Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WSO2WSO2 API Manager0, 3.0.0, 3.1.0, 3.2.0, 4.0.0, 4.1.0unaffected
WSO2WSO2 Identity Server0, 5.8.0, 5.9.0, 5.10.0, 5.11.0unaffected
WSO2WSO2 Identity Server as Key Manager0, 5.9.0, 5.10.0unaffected
WSO2WSO2 Open Banking AM0, 2.0.0unaffected
WSO2WSO2 Open Banking IAM0, 2.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-298 · source CWE mapping

Improper Validation of Certificate Expiration

Improper Validation of Certificate Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.