Improper Access Control via Secret Type Management API in WSO2 Identity Server
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.0.0.261, 6.1.0.262, 7.1.0.46, 1.2.3.7, 1.2.23.11, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 Identity Server
From 6.0.0 · fixed in 6.0.0.261; From 6.1.0 · fixed in 6.1.0.262; From 7.1.0 · fixed in 7.1.0.46
- org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.secret.management.common
From 1.2.3 · fixed in 1.2.3.7; From 1.2.23 · fixed in 1.2.23.11; From 1.3.83 · fixed in 1.3.83.16
- org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.secret.management.v1
From 1.2.3 · fixed in 1.2.3.7; From 1.2.23 · fixed in 1.2.23.11; From 1.3.83 · fixed in 1.3.83.16