dbcve.org
Wso2 OauthApplication · Jenkins

CVE-2023-30528

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-12
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins WSO2 Oauth Plugin 1.0 and earlier does not mask the WSO2 Oauth client secret on the global configuration form, increasing the potential for attackers to observe and capture it.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WSO2 Oauth Plugin for Jenkins versions 1.0 and earlier displays the OAuth client secret in plain text on the global configuration form instead of masking it as a password field, allowing anyone with access to the configuration page to read the sensitive credential.

MitigationRestrict administrative access to Jenkins global configuration and update the plugin to a version that masks the client secret field.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wso2 OauthApplication
Affected:<= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WSO2 OAuth plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'wso2' or 'WSO2 Oauth' in the plugin list. Note the installed version.
    Affected if Plugin version is 1.0 or earlier (or version is not listed/available)
  2. Check if WSO2 OAuth is configured
    Navigate to Manage Jenkins > Configure Global Security > Access Control > Security Realm section, or look for WSO2 OAuth configuration in Manage Jenkins > Configure System. Verify if WSO2 OAuth is enabled and configured with a client ID and client secret.
    Affected if WSO2 OAuth is enabled and a client secret has been configured
  3. Inspect client secret field visibility
    On the global configuration page where WSO2 OAuth is configured, locate the client secret field. Observe whether the entered value is displayed as plain text (readable characters) or masked as dots/asterisks (password field).
    Affected if The client secret field shows the actual secret value in plain text rather than being masked as a password field

A user is affected if they have the WSO2 OAuth plugin version 1.0 or earlier installed AND have WSO2 OAuth configured with a client secret that is displayed as unmasked plain text on the configuration page.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Restrict administrative access to Jenkins global configuration and update the plugin to a version that masks the client secret field.

Fix this in Wso2 Oauth Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30528 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30528 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data