# CVE-2019-1003021: Jenkins OpenId Connect Authentication Plugin showed plain text client secret in configuration form

> Attackers with browser access can retrieve the configured client secret from the Jenkins OpenId Connect Authentication Plugin configuration page.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Feb 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3858-58w9-wpcg

## What is CVE-2019-1003021?

CVE-2019-1003021 is a medium-severity vulnerability in Jenkins OpenId Connect Authentication Plugin, published on 6 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An exposure of sensitive information vulnerability exists in Jenkins OpenId Connect Authentication Plugin 1.4 and earlier in OicSecurityRealm/config.jelly that allows attackers able to view a Jenkins administrator's web browser output, or control the browser (e.g. malicious extension) to retrieve the configured client secret.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-1003021?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:oic-auth. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:oic-auth` | Maven | All versions | 1.5 |
| `org.jenkins-ci.plugins:oic-auth` | Maven | All versions | 1.5 |

Products: Jenkins Openid Connect Authentication.

## How do I fix CVE-2019-1003021?

Upgrade org.jenkins-ci.plugins:oic-auth to 1.5 or later.

## Is CVE-2019-1003021 being exploited?

There is no known exploitation of CVE-2019-1003021 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins OpenId Connect Authentication Plugin

- [CVE-2025-24399](https://insights.sbomify.com/CVE-2025-24399/): Improper handling of case sensitivity in Jenkins OpenId Connect Authentication Plugin (high 8.8)
- [CVE-2024-52553](https://insights.sbomify.com/CVE-2024-52553/): Session fixation vulnerability in Jenkins OpenId Connect Authentication Plugin (high 8.8)
- [CVE-2023-24424](https://insights.sbomify.com/CVE-2023-24424/): Session fixation vulnerability in Jenkins OpenId Connect Authentication Plugin (high 8.8)
- [CVE-2024-47806](https://insights.sbomify.com/CVE-2024-47806/): Jenkins OpenId Connect Authentication Plugin lacks audience claim validation (high 8.1)
- [CVE-2024-47807](https://insights.sbomify.com/CVE-2024-47807/): Jenkins OpenId Connect Authentication Plugin lacks issuer claim validation (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1003021 and fix it if it is affected.

What it is: CVE-2019-1003021 is a medium-severity vulnerability in Jenkins OpenId Connect Authentication Plugin, published on 6 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1003021 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:oic-auth (Maven): affected all versions; fixed in 1.5
- org.jenkins-ci.plugins:oic-auth (Maven): affected all versions; fixed in 1.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1003021/ (Markdown: https://insights.sbomify.com/CVE-2019-1003021/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1003021
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1003021
- OSV: https://osv.dev/vulnerability/CVE-2019-1003021

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1003021/
Summaries are generated and may contain mistakes; the official description above is the record.