Improper Access Control via Secret Type Management API in WSO2 Identity Server
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Carbon Identity API Server Secret Management Common 1.2.23.11, Carbon Identity API Server Secret Management Common 1.2.3.7, Carbon Identity API Server Secret Management Common 1.3.83.16 and 6 more.
The Secret Type Management REST API does not correctly isolate access controls when deleting a secret type. The on-delete cascade logic, when triggered, fails to enforce organizational boundaries, leading to the removal of secrets associated with that type across all organizations. Exploitation of this vulnerability can result in the unintended deletion of secrets across the entire deployment, potentially causing configuration failures, service interruptions, and a denial-of-service condition. This vulnerability requires delete permissions for the Secret Type Management REST API, which are by default only granted to administrators.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | Carbon Identity API Server Secret Management Common | >=1.2.23 <1.2.23.11, >=1.2.3 <1.2.3.7, >=1.3.83 <1.3.83.16 | 1.2.23.11, 1.2.3.7, 1.3.83.16 |
| WSO2 | Carbon Identity API Server Secret Management V1 | >=1.2.23 <1.2.23.11, >=1.2.3 <1.2.3.7, >=1.3.83 <1.3.83.16 | 1.2.23.11, 1.2.3.7, 1.3.83.16 |
| WSO2 | Identity Server | >=6.0.0 <6.0.0.261, >=6.1.0 <6.1.0.262, >=7.1.0 <7.1.0.46 | 6.0.0.261, 6.1.0.262, 7.1.0.46 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket