Jenkins WSO2 Oauth Plugin does not mask the WSO2 Oauth client secret on the global configuration form
Jenkins WSO2 Oauth Plugin 1.0 and earlier stores the WSO2 Oauth client secret unencrypted in the global config.xml file on the Jenkins controller as part of its configuration.
This client secret can be viewed by users with access to the Jenkins controller file system.
Additionally, the global configuration form does not mask the WSO2 Oauth client secret, increasing the potential for attackers to observe and capture it.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.jenkins-ci.plugins:wso2id-oauth | <= 1.0 | no fix |
References
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N- Weakness (CWE)
CWE-312- Platform
- Java / Kotlin (Maven)
- Package
org.jenkins-ci.plugins:wso2id-oauth- Disclosed
- 12.04.2023
- Updated
- 11.10.2026 11:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-q9hm-hr89-hgm7 - CC BY 4.0
Vulnerability history: org.jenkins-ci.plugins:wso2id-oauth
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 5
- First → latest
- 04.2023 05.2025
- Without a fix
- 5
- Exploited in attacks
- 0
Severity breakdown
- High 2
- Medium 1
- Low 2
Disclosures per year
- 2023: 4
- 2024: 0
- 2025: 1
- 2026: 0
-
Jenkins WSO2 Oauth Plugin does not mask the WSO2 Oauth client secret on the global configuration form this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.