Critical Jenkins CVEs
19 CVEs, 4 exploited, 7 protected by Waratek
Overview 19 matches · 7 protected · 4 exploited · 3 CISA KEV · 5 public PoC · 5 EPSS ≥ 0.5
Protected by Waratek
7
36.8%
Rule in development
0
0.0%
Mitigation candidate
1
5.3%
No exploit published
11
57.9%
blocked by ARMR today
7
36.8%
partly blocked
0
0.0%
not blocked
12
63.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
4
21.1%
Working exploit published
1
5.3%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
14
73.7%
split by
peak 10 / year
20151
Protected by Waratek1
Critical1
blocked by ARMR today1
Working exploit published1
20162
Protected by Waratek1
No exploit published1
Critical2
blocked by ARMR today1
not blocked1
No public exploit2
20172
Mitigation candidate1
No exploit published1
Critical2
not blocked2
Exploited1
No public exploit1
20182
Protected by Waratek2
Critical2
blocked by ARMR today2
Exploited2
20190
20200
202110
Protected by Waratek2
No exploit published8
Critical10
blocked by ARMR today2
not blocked8
No public exploit10
20220
20231
No exploit published1
Critical1
not blocked1
No public exploit1
20241
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
2015201620172018201920202021202220232024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-23897 | Critical | 2024-01-24 | Protected by Waratek | Exploited | Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character followed by a file path in an argument with the file's contents, allowing unauthenticated attackers to read arbitrary files on the Jenkins controller file system. |
| CVE-2023-27898 | Critical | 2023-03-10 | No exploit published | No public exploit | Jenkins 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not escape the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins instances. |
| CVE-2021-21697 | Critical | 2021-11-04 | No exploit published | No public exploit | Jenkins 2.318 and earlier, LTS 2.303.2 and earlier allows any agent to read and write the contents of any build directory stored in Jenkins with very few restrictions. |
| CVE-2021-21696 | Critical | 2021-11-04 | No exploit published | No public exploit | Jenkins 2.318 and earlier, LTS 2.303.2 and earlier does not limit agent read/write access to the libs/ directory inside build directories when using the FilePath APIs, allowing attackers in control of agent processes to replace the code of a trusted library with a modified variant. This results in unsandboxed code execution in the Jenkins controller process. |
| CVE-2021-21694 | Critical | 2021-11-04 | No exploit published | No public exploit | FilePath#toURI, FilePath#hasSymlink, FilePath#absolutize, FilePath#isDescendant, and FilePath#get*DiskSpace do not check any permissions in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. |
| CVE-2021-21693 | Critical | 2021-11-04 | No exploit published | No public exploit | When creating temporary files, agent-to-controller access to create those files is only checked after they've been created in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. |
| CVE-2021-21692 | Critical | 2021-11-04 | Protected by Waratek | No public exploit | FilePath#renameTo and FilePath#moveAllChildrenTo in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier only check 'read' agent-to-controller access permission on the source path, instead of 'delete'. |
| CVE-2021-21691 | Critical | 2021-11-04 | No exploit published | No public exploit | Creating symbolic links is possible without the 'symlink' agent-to-controller access control permission in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. |
| CVE-2021-21690 | Critical | 2021-11-04 | Protected by Waratek | No public exploit | Agent processes are able to completely bypass file path filtering by wrapping the file operation in an agent file path in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. |
| CVE-2021-21689 | Critical | 2021-11-04 | No exploit published | No public exploit | FilePath#unzip and FilePath#untar were not subject to any agent-to-controller access control in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. |
| CVE-2021-21687 | Critical | 2021-11-04 | No exploit published | No public exploit | Jenkins 2.318 and earlier, LTS 2.303.2 and earlier does not check agent-to-controller access to create symbolic links when unarchiving a symbolic link in FilePath#untar. |
| CVE-2021-21685 | Critical | 2021-11-04 | No exploit published | No public exploit | Jenkins 2.318 and earlier, LTS 2.303.2 and earlier does not check agent-to-controller access to create parent directories in FilePath#mkdirs. |
| CVE-2018-1000861 | Critical | 2018-12-10 | Protected by Waratek | Exploited | A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/core/src/main/java/org/kohsuke/stapler/MetaClass.java that allows attackers to invoke some methods on Java objects by accessing crafted URLs that were not intended to be invoked this way. |
| CVE-2017-1000353 | Critical | 2018-01-29 | Protected by Waratek | Exploited | Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution. An unauthenticated remote code execution vulnerability allowed attackers to transfer a serialized Java `SignedObject` object to the Jenkins CLI, that would be deserialized using a new `ObjectInputStream`, bypassing the existing blacklist-based protection mechanism. We're fixing this issue by adding `SignedObject` to the blacklist. We're also backporting the new HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based (i.e. Java serialization) CLI protocol, disabling it by default. |
| CVE-2017-1000362 | Critical | 2017-07-17 | No exploit published | No public exploit | The re-key admin monitor was introduced in Jenkins 1.498 and re-encrypted all secrets in JENKINS_HOME with a new key. It also created a backup directory with all old secrets, and the key used to encrypt them. These backups were world-readable and not removed afterwards. Jenkins now deletes the backup directory, if present. Upgrading from before 1.498 will no longer create a backup directory. Administrators relying on file access permissions in their manually created backups are advised to check them for the directory $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups, and delete it if present. |
| CVE-2016-9299 | Critical | 2017-01-12 | Mitigation candidate | Exploited | The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a crafted serialized Java object, which triggers an LDAP query to a third-party server. |
| CVE-2016-0791 | Critical | 2016-04-07 | No exploit published | No public exploit | Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify CSRF tokens, which makes it easier for remote attackers to bypass a CSRF protection mechanism via a brute-force approach. |
| CVE-2016-0788 | Critical | 2016-04-07 | Protected by Waratek | No public exploit | The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by opening a JRMP listener. |
| CVE-2015-8103 | Critical | 2015-11-25 | Protected by Waratek | Working exploit published | The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary code via a crafted serialized Java object, related to a problematic webapps/ROOT/WEB-INF/lib/commons-collections-*.jar file and the "Groovy variant in 'ysoserial'". |