CVE-2023-43494: Jenkins 2.50 through 2.423 (both inclusive), LTS 2.60.1 through 2.414.1 (both inclusive) does not exclude sensitive build variables (e.g., password parameter values) from the search in the build...
Medium CVSS 4.3
- CVE id
- CVE-2023-43494
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Jenkins Runtimes and servers |
>= 2.50, < 2.424 | 2.424 |
| Jenkins LTS Runtimes and servers |
>= 2.60.1, < 2.414.2 | 2.414.2 |
How to fix it
Jenkins (Runtimes and servers)
Upgrade Jenkins to 2.424 or later.
curl -sI $JENKINS_URL | grep X-Jenkins
- Upgrade Jenkins to the patched weekly release (the jenkins/jenkins image tag or your packages) and restart it.
Jenkins LTS (Runtimes and servers)
Upgrade Jenkins LTS to 2.414.2 or later.
curl -sI $JENKINS_URL | grep X-Jenkins
- Upgrade Jenkins to the patched LTS release (the jenkins/jenkins:lts image tag or your packages) and restart it.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
Jenkins 2.50 through 2.423 (both inclusive), LTS 2.60.1 through 2.414.1 (both inclusive) does not exclude sensitive build variables (e.g., password parameter values) from the search in the build history widget, allowing attackers with Item/Read permission to obtain values of sensitive variables used in builds by iteratively testing different characters until the correct sequence is discovered.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.