Vulnerabilities

The administrative operations within the Carbon Console do not adequately validate specific user-supplied input.

The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation.

The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported.

Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs.

The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is config…

When a proxy server is configured with `customUrl.enabled`, the component accepts user-supplied input within forwarded HTTP headers without enforcing expected validation constraints.

The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-Site Request Forgery (CSRF) attacks.

The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input.

The account locking mechanism fails to trigger when secondary user stores are inaccessible.

Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system.

The affected product accepts user-supplied input within a URL parameter without enforcing expected sanitization or encoding before rendering it within the response.

The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content.

The software accepts user-supplied input via a URL parameter without adequate output encoding before reflecting it back to the user's browser.

The software fails to enforce role-based access controls for certain Gateway API invocations.

In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient validation or sanitization, allowing these headers to be injected into HTTP responses.

A malicious actor with administrative privileges can upload an arbitrary file to a user-controlled location within the deployment via a system REST API.

A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products.

A Cross-Site Request Forgery (CSRF) vulnerability exists in multiple WSO2 products due to the use of the HTTP GET method for state-changing operations within admin services, specifically in the event processor of the Car…

A reflected cross-site scripting (XSS) vulnerability exists in the management console of multiple WSO2 products due to improper output encoding.

A reflected cross-site scripting (XSS) vulnerability exists in the authentication endpoints of multiple WSO2 products due to a lack of output encoding.

An arbitrary code execution vulnerability exists in multiple WSO2 products due to insufficient restrictions in the GraalJS and NashornJS Script Mediator engines.

An arbitrary file upload vulnerability exists in multiple WSO2 products due to insufficient validation of uploaded content and destination in SOAP admin services.

An XML External Entity (XXE) vulnerability exists in multiple WSO2 products due to improper configuration of the XML parser.

An arbitrary file upload vulnerability exists in multiple WSO2 products due to improper input validation in the CarbonAppUploader admin service endpoint.

An authentication bypass vulnerability exists in the Management Console of multiple WSO2 products.