Traffic Manager vulnerabilities
17 known vulnerabilities in Traffic Manager from WSO2. 17 are rated high or critical, and 1 has been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 8.4 High severity
WSO2 Open Banking AM: Improper Neutralization of Special Elements used in an OS Command
The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enabl
- 10.0 Critical severity
WSO2 Multiple Products Path Traversal Exploited
The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized acces
- 9.8 Critical severity
WSO2 API Manager: Improper Privilege Management
Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs. Exploitation of this vulnerability allows a low-privileged user to invoke the Admin REST APIs of WSO2 products, potentiall
- 9.4 Critical severity
WSO2 Identity Server: Protection Mechanism Failure
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 configured. This allows an attacker to bypass
- 7.5 High severity
WSO2 Enterprise Integrator: Protection Mechanism Failure
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authenti
- 8.6 High severity
WSO2 Universal Gateway: Improper Neutralization
The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a
- 8.8 High severity
WSO2 API Control Plane: Improper Preservation of Permissions
The software fails to enforce role-based access controls for certain Gateway API invocations. Users with the 'Internal/Everyone' role can invoke these APIs, bypassing intended permission checks. This same vulnerability also affects Internal Service APIs, poten
- 7.5 High severity
WSO2 API Manager: Improper Neutralization of Special Elements in Output Used by a Downstream Component
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. By exploiting this vulnerability, a malicious actor can inj
- 7.2 High severity
WSO2 API Manager: Unrestricted Upload of File with Dangerous Type
A malicious actor with administrative privileges can upload an arbitrary file to a user-controlled location within the deployment via a system REST API. Successful uploads may lead to remote code execution. By leveraging the vulnerability, a malicious actor ma
- 9.8 Critical severity
WSO2 API Manager: Missing Authentication for Critical Functionality
A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default con
- 8.8 High severity
WSO2 Open Banking AM: Cross-Site Request Forgery
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 Carbon console. Although the SameSite=Lax c
- 7.2 High severity
WSO2 Micro Integrator: Improper Control of Generation of Code
An arbitrary code execution vulnerability exists in multiple WSO2 products due to insufficient restrictions in the GraalJS and NashornJS Script Mediator engines. Authenticated users with elevated privileges can execute arbitrary code within the integration run
- 7.2 High severity
WSO2 API Manager: Unrestricted Upload of File with Dangerous Type
An arbitrary file upload vulnerability exists in multiple WSO2 products due to insufficient validation of uploaded content and destination in SOAP admin services. A malicious actor with administrative privileges can upload a specially crafted file to a user-co
- 9.1 Critical severity
WSO2 Enterprise Integrator: Improper Restriction of XML External Entity Reference
An XML External Entity (XXE) vulnerability exists in multiple WSO2 products due to improper configuration of the XML parser. The application parses user-supplied XML without applying sufficient restrictions, allowing resolution of external entities. A successf
- 7.2 High severity
WSO2 Identity Server: Unrestricted Upload of File with Dangerous Type
An arbitrary file upload vulnerability exists in multiple WSO2 products due to improper input validation in the CarbonAppUploader admin service endpoint. An authenticated attacker with appropriate privileges can upload a malicious file to a user-controlled loc
- 9.8 Critical severity
WSO2 API Manager: Incorrect Authorization
Due to an insufficient access control implementation in multiple WSO2 Products, authentication and authorization checks for certain REST APIs can be bypassed, allowing them to be invoked without proper validation. Successful exploitation of this vulnerability
- 7.2 High severity
WSO2 API Manager: Improper Control of Generation of Code
An authenticated remote code execution (RCE) vulnerability exists in multiple WSO2 products due to improper input validation in the event processor admin service. A user with administrative access to the SOAP admin services can exploit this flaw by deploying a