CVE-2018-1000169 Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
Medium 5.3
Published
Updated
Check this codebase for CVE-2018-1000169 and fix it if it is affected.
What it is: CVE-2018-1000169 is a medium-severity vulnerability in Jenkins Jenkins, published on 13 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000169 in the wild and no public exploit code.
Affected packages and fixed versions:
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.107.2
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 2.107.2
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.108; fixed in 2.116
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.108; fixed in 2.116
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-2018-1000169/ (Markdown: https://insights.sbomify.com/CVE-2018-1000169/index.md)
Unauthorized attackers can confirm the existence of specific agents or views in Jenkins by sending crafted CLI commands, leaking internal configuration details.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2018-1000169?
CVE-2018-1000169 is a medium-severity vulnerability in Jenkins Jenkins, published on 13 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An exposure of sensitive information vulnerability exists in Jenkins 2.115 and older, LTS 2.107.1 and older, in CLICommand.java and ViewOptionHandler.java that allows unauthorized attackers to confirm the existence of agents or views with an attacker-specified name by sending a CLI command to Jenkins.
Weakness: CWE-200
Which versions are affected by CVE-2018-1000169?
4 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.jenkins-ci.main:jenkins-core Maven | All versions | 2.107.2 |
org.jenkins-ci.main:jenkins-core Maven | All versions | 2.107.2 |
org.jenkins-ci.main:jenkins-core Maven | From 2.108 | 2.116 |
org.jenkins-ci.main:jenkins-core Maven | From 2.108 | 2.116 |
Linux distribution packages (36)
ansible-asb-modules Red Hat:openshift:3.10::el7 | All versions | 0:0.2.1-1.el7 |
ansible-kubernetes-modules Red Hat:openshift:3.10::el7 | All versions | 0:0.4.0-8.el7 |
ansible-service-broker Red Hat:openshift:3.10::el7 | All versions | 0:1.2.17-1.el7 |
ansible-service-broker-container-scripts Red Hat:openshift:3.10::el7 | All versions | 0:1.2.17-1.el7 |
ansible-service-broker-devel Red Hat:openshift:3.10::el7 | All versions | 0:1.2.17-1.el7 |
ansible-service-broker-selinux Red Hat:openshift:3.10::el7 | All versions | 0:1.2.17-1.el7 |
apb Red Hat:openshift:3.10::el7 | All versions | 0:1.2.14-1.el7 |
apb-base-scripts Red Hat:openshift:3.10::el7 | All versions | 0:1.2.7-1.el7 |
apb-container-scripts Red Hat:openshift:3.10::el7 | All versions | 0:1.2.14-1.el7 |
atomic-enterprise-service-catalog Red Hat:openshift:3.10::el7 | All versions | 1:3.10.14-1.git.1444.3b95d24.el7 |
atomic-enterprise-service-catalog-svcat Red Hat:openshift:3.10::el7 | All versions | 1:3.10.14-1.git.1444.3b95d24.el7 |
atomic-openshift Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-clients Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-clients-redistributable Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-cluster-autoscaler Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.5d093fd.el7 |
atomic-openshift-descheduler Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.299.3f3c30b.el7 |
atomic-openshift-docker-excluder Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-dockerregistry Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.387.07a726e.el7 |
atomic-openshift-excluder Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-hyperkube Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-hypershift Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-master Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-metrics-server Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.49.382fff9.el7 |
atomic-openshift-node Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-node-problem-detector Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.198.04596af.el7 |
atomic-openshift-pod Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-sdn-ovs Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-template-service-broker Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-tests Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.0.ba8ae6d.el7 |
atomic-openshift-web-console Red Hat:openshift:3.10::el7 | All versions | 0:3.10.14-1.git.334.3197fdf.el7 |
cockpit Red Hat:openshift:3.10::el7 | All versions | 0:155-1.el7 |
cockpit-debuginfo Red Hat:openshift:3.10::el7 | All versions | 0:155-1.el7 |
cockpit-kubernetes Red Hat:openshift:3.10::el7 | All versions | 0:155-1.el7 |
cri-o Red Hat:openshift:3.10::el7 | All versions | 0:1.10.5-1.rhaos3.10.git4c81456.el7 |
cri-tools Red Hat:openshift:3.10::el7 | All versions | 0:1.0.0-5.rhaos3.10.git2e22a75.el7 |
cri-tools-debuginfo Red Hat:openshift:3.10::el7 | All versions | 0:1.0.0-5.rhaos3.10.git2e22a75.el7 |
Products include Jenkins Jenkins.
How do I fix CVE-2018-1000169?
Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.107.2 or 2.116.
Is CVE-2018-1000169 being exploited?
There is no known exploitation of CVE-2018-1000169 in the wild and no public exploit code.
Other vulnerabilities in Jenkins Jenkins
- CVE-2024-23897 Jenkins Command Line Interface (CLI) Path Traversal
- CVE-2018-1000861 Jenkins Stapler Web Framework Deserialization of Untrusted Data
- CVE-2017-1000353 Jenkins Remote Code Execution
- CVE-2015-5317 Jenkins User Interface (UI) Information Disclosure
- CVE-2021-21690 Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins
Sources
Also known as GHSA-cpw3-x7gf-p872, RHBA-2018:1816.