CyberSecBulletin
CVE-2024-6914NVD status: Analyzed

WSO2 API Manager: Incorrect Authorization

Published Updated By the CyberSecBulletin desk

CVE-2024-6914 is a critical-severity incorrect authorization vulnerability in WSO2 API Manager from WSO2, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 2.2.0.55, 2.5.0.82, 2.6.0.141 as the first without the flaw, so updating WSO2 API Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.75% chance of exploitation within 30 days, higher than 56% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update WSO2 API Manager to 2.2.0.55 or 2.5.0.82 or 2.6.0.141 or 3.0.0.161, whichever matches your release line, or a later version.
  2. Update WSO2 Governance Registry to 5.4.0.14 or a later version.
  3. Update WSO2 Identity Server to 5.3.0.31 or 5.4.0.30 or 5.4.1.35 or 5.5.0.48, whichever matches your release line, or a later version.
  4. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 API Manager2.2.0 up to, but not including, 2.2.0.55; 2.5.0 up to, but not including, 2.5.0.82; 2.6.0 up to, but not including, 2.6.0.141; 3.0.0 up to, but not including, 3.0.0.161; 3.1.0 up to, but not including, 3.1.0.292; 3.2.0 up to, but not including, 3.2.0.382; 3.2.1 up to, but not including, 3.2.1.14; 4.0.0 up to, but not including, 4.0.0.304; and 3 more ranges2.2.0.55, 2.5.0.82, 2.6.0.141, 3.0.0.161, 3.1.0.292, 3.2.0.382
WSO2WSO2 Governance Registry5.4.0 up to, but not including, 5.4.0.145.4.0.14
WSO2WSO2 Identity Server5.3.0 up to, but not including, 5.3.0.31; 5.4.0 up to, but not including, 5.4.0.30; 5.4.1 up to, but not including, 5.4.1.35; 5.5.0 up to, but not including, 5.5.0.48; 5.6.0 up to, but not including, 5.6.0.56; 5.7.0 up to, but not including, 5.7.0.122; 5.8.0 up to, but not including, 5.8.0.104; 5.9.0 up to, but not including, 5.9.0.155; and 5 more ranges5.3.0.31, 5.4.0.30, 5.4.1.35, 5.5.0.48, 5.6.0.56, 5.7.0.122
WSO2WSO2 Identity Server as Key Manager5.3.0 up to, but not including, 5.3.0.36; 5.5.0 up to, but not including, 5.5.0.49; 5.6.0 up to, but not including, 5.6.0.70; 5.7.0 up to, but not including, 5.7.0.121; 5.9.0 up to, but not including, 5.9.0.162; 5.10.0 up to, but not including, 5.10.0.3115.3.0.36, 5.5.0.49, 5.6.0.70, 5.7.0.121, 5.9.0.162, 5.10.0.311
WSO2WSO2 IoT3.3.0 up to, but not including, 3.3.0.59; 3.3.1 up to, but not including, 3.3.1.613.3.0.59, 3.3.1.61
WSO2WSO2 Open Banking AM1.3.0 up to, but not including, 1.3.0.130; 1.4.0 up to, but not including, 1.4.0.133; 1.5.0 up to, but not including, 1.5.0.135; 2.0.0 up to, but not including, 2.0.0.3411.3.0.130, 1.4.0.133, 1.5.0.135, 2.0.0.341
WSO2WSO2 Open banking KM1.3.0 up to, but not including, 1.3.0.113; 1.4.0 up to, but not including, 1.4.0.129; 1.5.0 up to, but not including, 1.5.0.1191.3.0.113, 1.4.0.129, 1.5.0.119
WSO2WSO2 Open Banking IAM2.0.0 up to, but not including, 2.0.0.3622.0.0.362
WSO2WSO2 Carbon Identity Management5.7.5 up to, but not including, 5.7.5.9; 5.10.86 up to, but not including, 5.10.86.4; 5.10.112 up to, but not including, 5.10.112.14; 5.11.148 up to, but not including, 5.11.148.13; 5.11.256 up to, but not including, 5.11.256.15; 5.12.153 up to, but not including, 5.12.153.58; 5.12.387 up to, but not including, 5.12.387.41; 5.14.97 up to, but not including, 5.14.97.75; and 9 more ranges5.7.5.9, 5.10.86.4, 5.10.112.14, 5.11.148.13, 5.11.256.15, 5.12.153.58
WSO2API Manager2.2.0; 2.5.0; 2.6.0; 3.0.0; 3.1.0; 3.2.0; 3.2.1; 4.0.0; and 3 more rangesNot stated
WSO2Identity Server5.3.0; 5.4.0; 5.4.1; 5.5.0; 5.6.0; 5.7.0; 5.8.0; 5.9.0; and 5 more rangesNot stated
WSO2Identity Server As Key Manager5.3.0; 5.5.0; 5.6.0; 5.7.0; 5.9.0; 5.10.0Not stated
WSO2Open Banking Am1.3.0; 1.4.0; 1.5.0; 2.0.0Not stated
WSO2Open Banking Iam2.0.0Not stated
WSO2Open Banking Km1.3.0; 1.4.0; 1.5.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Official description

An incorrect authorization vulnerability exists in multiple WSO2 products due to a business logic flaw in the account recovery-related SOAP admin service. A malicious actor can exploit this vulnerability to reset the password of any user account, leading to a complete account takeover, including accounts with elevated privileges. This vulnerability is exploitable only through the account recovery SOAP admin services exposed via the "/services" context path in affected products. The impact may be reduced if access to these endpoints has been restricted based on the "Security Guidelines for Production Deployment" by disabling exposure to untrusted networks.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in WSO2 API Manager

All WSO2 API Manager vulnerabilities

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.