Jenkins CVEs
328 CVEs, 8 exploited, 39 protected by Waratek
Overview 328 matches · 39 protected · 8 exploited · 4 CISA KEV · 18 public PoC · 13 EPSS ≥ 0.5
Protected by Waratek
39
11.9%
Rule in development
0
0.0%
Mitigation candidate
13
4.0%
No exploit published
276
84.1%
blocked by ARMR today
39
11.9%
partly blocked
0
0.0%
not blocked
289
88.1%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 55 / year
20111
No exploit published1
Low1
not blocked1
No public exploit1
20122
No exploit published2
Medium2
not blocked2
No public exploit2
201311
Mitigation candidate3
No exploit published8
High1
Medium8
Low2
not blocked11
Exploited1
Working exploit published2
No public exploit8
201422
Protected by Waratek2
No exploit published20
High2
Medium17
Low3
blocked by ARMR today2
not blocked20
No public exploit22
201517
Protected by Waratek3
No exploit published14
Critical1
High2
Medium13
Low1
blocked by ARMR today3
not blocked14
Working exploit published1
No public exploit16
201616
Protected by Waratek1
Mitigation candidate1
No exploit published14
Critical2
High5
Medium9
blocked by ARMR today1
not blocked15
Working exploit published1
No public exploit15
20176
Mitigation candidate1
No exploit published5
Critical2
Medium4
not blocked6
Exploited1
No public exploit5
201855
Protected by Waratek6
Mitigation candidate1
No exploit published48
Critical2
High13
Medium38
Low2
blocked by ARMR today6
not blocked49
Exploited2
Working exploit published1
No public exploit52
201936
Protected by Waratek3
Mitigation candidate1
No exploit published32
High13
Medium23
blocked by ARMR today3
not blocked33
Working exploit published1
No public exploit35
202028
Protected by Waratek3
Mitigation candidate4
No exploit published21
High7
Medium21
blocked by ARMR today3
not blocked25
Working exploit published4
No public exploit24
202132
Protected by Waratek7
No exploit published25
Critical10
High8
Medium14
blocked by ARMR today7
not blocked25
Forecast only1
No public exploit31
202214
Protected by Waratek4
No exploit published10
High5
Medium9
blocked by ARMR today4
not blocked10
Proof of concept only1
No public exploit13
202322
Mitigation candidate1
No exploit published21
Critical1
High12
Medium9
not blocked22
Exploited1
No public exploit21
20249
Protected by Waratek2
No exploit published7
Critical1
High3
Medium5
blocked by ARMR today2
not blocked7
Exploited1
Proof of concept only1
Forecast only1
No public exploit6
202516
Mitigation candidate1
No exploit published15
High2
Medium13
Low1
not blocked16
Exploited1
No public exploit15
202641
Protected by Waratek8
No exploit published33
High18
Medium21
Low2
blocked by ARMR today8
not blocked33
Exploited1
No public exploit40
20122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-1000862 | Medium | 2018-12-10 | No exploit published | No public exploit | An information exposure vulnerability exists in Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in DirectoryBrowserSupport.java that allows attackers with the ability to control build output to browse the file system on agents running builds beyond the duration of the build using the workspace browser. |
| 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-2018-1999047 | Medium | 2018-08-23 | No exploit published | No public exploit | A improper authorization vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in UpdateCenter.java that allows attackers to cancel a Jenkins restart scheduled through the update center. |
| CVE-2018-1999046 | Medium | 2018-08-23 | No exploit published | No public exploit | A exposure of sensitive information vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in Computer.java that allows attackers With Overall/Read permission to access the connection log for any agent. |
| CVE-2018-1999045 | Medium | 2018-08-23 | No exploit published | No public exploit | A improper authentication vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in SecurityRealm.java, TokenBasedRememberMeServices2.java that allows attackers with a valid cookie to remain logged in even if that feature is disabled. |
| CVE-2018-1999044 | Medium | 2018-08-23 | No exploit published | No public exploit | A denial of service vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in CronTab.java that allows attackers with Overall/Read permission to have a request handling thread enter an infinite loop. |
| CVE-2018-1999043 | High | 2018-08-23 | No exploit published | No public exploit | A denial of service vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in BasicAuthenticationFilter.java, BasicHeaderApiTokenAuthenticator.java that allows attackers to create ephemeral in-memory user records by attempting to log in using invalid credentials. |
| CVE-2018-1999042 | Medium | 2018-08-23 | No exploit published | No public exploit | A vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in XStream2.java that allows attackers to have Jenkins resolve a domain name when deserializing an instance of java.net.URL. |
| CVE-2018-1999006 | Medium | 2018-07-23 | No exploit published | No public exploit | A exposure of sensitive information vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in Plugin.java that allows attackers to determine the date and time when a plugin HPI/JPI file was last extracted, which typically is the date of the most recent installation/upgrade. |
| CVE-2018-1999004 | Medium | 2018-07-23 | No exploit published | No public exploit | A Improper authorization vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in SlaveComputer.java that allows attackers with Overall/Read permission to initiate agent launches, and abort in-progress agent launches. |
| CVE-2018-1999003 | Medium | 2018-07-23 | No exploit published | No public exploit | A Improper authorization vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in Queue.java that allows attackers with Overall/Read permission to cancel queued builds. |
| CVE-2018-1999002 | High | 2018-07-23 | Mitigation candidate | Working exploit published | A arbitrary file read vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in the Stapler web framework's org/kohsuke/stapler/Stapler.java that allows attackers to send crafted HTTP requests returning the contents of any file on the Jenkins master file system that the Jenkins master has access to. |
| CVE-2018-1999001 | High | 2018-07-23 | No exploit published | No public exploit | A unauthorized modification of configuration vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in User.java that allows attackers to provide crafted login credentials that cause Jenkins to move the config.xml file from the Jenkins home directory. If Jenkins is started without this file present, it will revert to the legacy defaults of granting administrator access to anonymous users. |
| CVE-2018-1000607 | Medium | 2018-06-26 | No exploit published | No public exploit | A arbitrary file write vulnerability exists in Jenkins Fortify CloudScan Plugin 1.5.1 and earlier in ArchiveUtil.java that allows attackers able to control rulepack zip file contents to overwrite any file on the Jenkins master file system, only limited by the permissions of the user the Jenkins master process is running as. |
| CVE-2018-1000195 | Medium | 2018-06-05 | No exploit published | No public exploit | A server-side request forgery vulnerability exists in Jenkins 2.120 and older, LTS 2.107.2 and older in ZipExtractionInstaller.java that allows users with Overall/Read permission to have Jenkins submit a HTTP GET request to an arbitrary URL and learn whether the response is successful (200) or not. |
| CVE-2018-1000194 | High | 2018-06-05 | Protected by Waratek | No public exploit | A path traversal vulnerability exists in Jenkins 2.120 and older, LTS 2.107.2 and older in FilePath.java, SoloFilePathFilter.java that allows malicious agents to read and write arbitrary files on the Jenkins master, bypassing the agent-to-master security subsystem protection. |
| CVE-2018-1000193 | Medium | 2018-06-05 | No exploit published | No public exploit | A improper neutralization of control sequences vulnerability exists in Jenkins 2.120 and older, LTS 2.107.2 and older in HudsonPrivateSecurityRealm.java that allows users to sign up using user names containing control characters that can then appear to have the same name as other users, and cannot be deleted via the UI. |
| CVE-2018-1000192 | Medium | 2018-06-05 | No exploit published | No public exploit | A information exposure vulnerability exists in Jenkins 2.120 and older, LTS 2.107.2 and older in AboutJenkins.java, ListPluginsCommand.java that allows users with Overall/Read access to enumerate all installed plugins. |
| CVE-2017-2598 | Medium | 2018-05-23 | No exploit published | No public exploit | Jenkins before versions 2.44, 2.32.2 uses AES ECB block cipher mode without IV for encrypting secrets which makes Jenkins and the stored secrets vulnerable to unnecessary risks (SECURITY-304). |
| CVE-2017-2609 | Medium | 2018-05-22 | No exploit published | No public exploit | jenkins before versions 2.44, 2.32.2 is vulnerable to an information disclosure vulnerability in search suggestions (SECURITY-385). The autocomplete feature on the search box discloses the names of the views in its suggestions, including the ones for which the current user does not have access to. |
| CVE-2017-2607 | Medium | 2018-05-21 | No exploit published | No public exploit | jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users, or users with SCM access, could configure jobs or modify build scripts such that they print serialized console notes that perform cross-site scripting attacks on Jenkins users viewing the build logs. |
| CVE-2017-2613 | Medium | 2018-05-15 | No exploit published | No public exploit | jenkins before versions 2.44, 2.32.2 is vulnerable to a user creation CSRF using GET by admins. While this user record was only retained until restart in most cases, administrators' web browsers could be manipulated to create a large number of user records (SECURITY-406). |
| CVE-2017-2612 | Medium | 2018-05-15 | No exploit published | No public exploit | In Jenkins before versions 2.44, 2.32.2 low privilege users were able to override JDK download credentials (SECURITY-392), resulting in future builds possibly failing to download a JDK. |
| CVE-2017-2610 | Medium | 2018-05-15 | No exploit published | No public exploit | jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting in search suggestions due to improperly escaping users with less-than and greater-than characters in their names (SECURITY-388). |
| CVE-2017-2608 | High | 2018-05-15 | No exploit published | No public exploit | Jenkins before versions 2.44, 2.32.2 is vulnerable to a remote code execution vulnerability involving the deserialization of various types in javax.imageio in XStream-based APIs (SECURITY-383). |
| CVE-2017-2604 | Medium | 2018-05-15 | No exploit published | No public exploit | In Jenkins before versions 2.44, 2.32.2 low privilege users were able to act on administrative monitors due to them not being consistently protected by permission checks (SECURITY-371). |
| CVE-2017-2603 | Low | 2018-05-15 | No exploit published | No public exploit | Jenkins before versions 2.44, 2.32.2 is vulnerable to a user data leak in disconnected agents' config.xml API. This could leak sensitive data such as API tokens (SECURITY-362). |
| CVE-2017-2602 | Medium | 2018-05-15 | No exploit published | No public exploit | jenkins before versions 2.44, 2.32.2 is vulnerable to an improper blacklisting of the Pipeline metadata files in the agent-to-master security subsystem. This could allow metadata files to be written to by malicious agents (SECURITY-358). |
| CVE-2017-2600 | Medium | 2018-05-15 | No exploit published | No public exploit | In jenkins before versions 2.44, 2.32.2 node monitor data could be viewed by low privilege users via the remote API. These included system configuration and runtime information of these nodes (SECURITY-343). |
| CVE-2017-2611 | Medium | 2018-05-08 | No exploit published | No public exploit | Jenkins before versions 2.44, 2.32.2 is vulnerable to an insufficient permission check for periodic processes (SECURITY-389). The URLs /workspaceCleanup and /fingerprintCleanup did not perform permission checks, allowing users with read access to Jenkins to trigger these background processes (that are otherwise performed daily), possibly causing additional load on Jenkins master and agents. |
| CVE-2017-2606 | Medium | 2018-05-08 | No exploit published | No public exploit | Jenkins before versions 2.44, 2.32.2 is vulnerable to an information exposure in the internal API that allows access to item names that should not be visible (SECURITY-380). This only affects anonymous users (other users legitimately have access) that were able to get a list of items via an UnprotectedRootAction. |
| CVE-2018-1000169 | Medium | 2018-04-16 | No exploit published | No public exploit | 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. |
| CVE-2017-2599 | Medium | 2018-04-11 | No exploit published | No public exploit | Jenkins before versions 2.44 and 2.32.2 is vulnerable to an insufficient permission check. This allows users with permissions to create new items (e.g. jobs) to overwrite existing items they don't have access to (SECURITY-321). |
| CVE-2018-6356 | Medium | 2018-02-20 | Protected by Waratek | No public exploit | Jenkins before 2.107 and Jenkins LTS before 2.89.4 did not properly prevent specifying relative paths that escape a base directory for URLs accessing plugin resource files. This allowed users with Overall/Read permission to download files from the Jenkins master they should not have access to. On Windows, any file accessible to the Jenkins master process could be downloaded. On other operating systems, any file within the Jenkins home directory accessible to the Jenkins master process could be downloaded. |
| CVE-2018-1000068 | Medium | 2018-02-16 | No exploit published | No public exploit | An improper input validation vulnerability exists in Jenkins versions 2.106 and earlier, and LTS 2.89.3 and earlier, that allows an attacker to access plugin resource files in the META-INF and WEB-INF directories that should not be accessible, if the Jenkins home directory is on a case-insensitive file system. |
| CVE-2018-1000067 | Medium | 2018-02-16 | No exploit published | No public exploit | An improper authorization vulnerability exists in Jenkins versions 2.106 and earlier, and LTS 2.89.3 and earlier, that allows an attacker to have Jenkins submit HTTP GET requests and get limited information about the response. |
| CVE-2017-1000356 | High | 2018-01-29 | No exploit published | No public exploit | Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an issue in the Jenkins user database authentication realm: create an account if signup is enabled; or create an account if the victim is an administrator, possibly deleting the existing default admin user in the process and allowing a wide variety of impacts. |
| CVE-2017-1000355 | Medium | 2018-01-29 | No exploit published | No public exploit | Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an XStream: Java crash when trying to instantiate void/Void. |
| CVE-2017-1000354 | High | 2018-01-29 | No exploit published | No public exploit | Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to a login command which allowed impersonating any Jenkins user. The `login` command available in the remoting-based CLI stored the encrypted user name of the successfully authenticated user in a cache file used to authenticate further commands. Users with sufficient permission to create secrets in Jenkins, and download their encrypted values (e.g. with Job/Configure permission), were able to impersonate any other Jenkins user on the same instance. |
| 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-1000401 | Low | 2018-01-26 | No exploit published | No public exploit | The Jenkins 2.73.1 and earlier, 2.83 and earlier default form control for passwords and other secrets, <f:password/>, supports form validation (e.g. for API keys). The form validation AJAX requests were sent via GET, which could result in secrets being logged to a HTTP access log in non-default configurations of Jenkins, and made available to users with access to these log files. Form validation for <f:password/> is now always sent via POST, which is typically not logged. |
| CVE-2017-1000400 | Medium | 2018-01-26 | No exploit published | No public exploit | The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /job/(job-name)/api contained information about upstream and downstream projects. This included information about tasks that the current user otherwise has no access to, e.g. due to lack of Item/Read permission. This has been fixed, and the API now only lists upstream and downstream projects that the current user has access to. |
| CVE-2017-1000399 | Medium | 2018-01-26 | No exploit published | No public exploit | The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /queue/item/(ID)/api showed information about tasks in the queue (typically builds waiting to start). This included information about tasks that the current user otherwise has no access to, e.g. due to lack of Item/Read permission. This has been fixed, and the API endpoint is now only available for tasks that the current user has access to. |
| CVE-2017-1000398 | Medium | 2018-01-26 | No exploit published | No public exploit | The remote API in Jenkins 2.73.1 and earlier, 2.83 and earlier at /computer/(agent-name)/api showed information about tasks (typically builds) currently running on that agent. This included information about tasks that the current user otherwise has no access to, e.g. due to lack of Item/Read permission. This has been fixed, and the API now only shows information about accessible tasks. |
| CVE-2017-1000396 | Medium | 2018-01-26 | No exploit published | No public exploit | Jenkins 2.73.1 and earlier, 2.83 and earlier bundled a version of the commons-httpclient library with the vulnerability CVE-2012-6153 that incorrectly verified SSL certificates, making it susceptible to man-in-the-middle attacks. This library is widely used as a transitive dependency in Jenkins plugins. The fix for CVE-2012-6153 was backported to the version of commons-httpclient that is bundled in core and made available to plugins. |
| CVE-2017-1000395 | Medium | 2018-01-26 | No exploit published | No public exploit | Jenkins 2.73.1 and earlier, 2.83 and earlier provides information about Jenkins user accounts which is generally available to anyone with Overall/Read permissions via the /user/(username)/api remote API. This included e.g. Jenkins users' email addresses if the Mailer Plugin is installed. The remote API now no longer includes information beyond the most basic (user ID and name) unless the user requesting it is a Jenkins administrator. |
| CVE-2017-1000394 | High | 2018-01-26 | No exploit published | No public exploit | Jenkins 2.73.1 and earlier, 2.83 and earlier bundled a version of the commons-fileupload library with the denial-of-service vulnerability known as CVE-2016-3092. The fix for that vulnerability has been backported to the version of the library bundled with Jenkins. |
| CVE-2017-1000393 | High | 2018-01-26 | Protected by Waratek | No public exploit | Jenkins 2.73.1 and earlier, 2.83 and earlier users with permission to create or configure agents in Jenkins could configure a launch method called 'Launch agent via execution of command on master'. This allowed them to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of this launch method now requires the Run Scripts permission typically only granted to administrators. |
| CVE-2017-1000392 | Medium | 2018-01-26 | No exploit published | No public exploit | Jenkins 2.88 and earlier; 2.73.2 and earlier Autocompletion suggestions for text fields were not escaped, resulting in a persisted cross-site scripting vulnerability if the source for the suggestions allowed specifying text that includes HTML metacharacters like less-than and greater-than characters. |
| CVE-2017-1000391 | High | 2018-01-26 | No exploit published | No public exploit | Jenkins versions 2.88 and earlier and 2.73.2 and earlier stores metadata related to 'people', which encompasses actual user accounts, as well as users appearing in SCM, in directories corresponding to the user ID on disk. These directories used the user ID for their name without additional escaping, potentially resulting in problems like overwriting of unrelated configuration files. |
| CVE-2017-1000390 | Medium | 2018-01-26 | No exploit published | No public exploit | Jenkins Multijob plugin version 1.25 and earlier did not check permissions in the Resume Build action, allowing anyone with Job/Read permission to resume the build. |
| CVE-2017-1000504 | High | 2018-01-24 | No exploit published | No public exploit | A race condition during Jenkins 2.94 and earlier; 2.89.1 and earlier startup could result in the wrong order of execution of commands during initialization. There is a very short window of time after startup during which Jenkins may no longer show the 'Please wait while Jenkins is getting ready to work' message but Cross-Site Request Forgery (CSRF) protection may not yet be effective. |
| CVE-2017-1000503 | High | 2018-01-24 | No exploit published | No public exploit | A race condition during Jenkins 2.81 through 2.94 (inclusive); 2.89.1 startup could result in the wrong order of execution of commands during initialization. This could in rare cases result in failure to initialize the setup wizard on the first startup. This resulted in multiple security-related settings not being set to their usual strict default. |
| CVE-2017-17383 | Medium | 2017-12-06 | No exploit published | No public exploit | Jenkins through 2.93 allows remote authenticated administrators to conduct XSS attacks via a crafted tool name in a job configuration form, as demonstrated by the JDK tool in Jenkins core and the Ant tool in the Ant plugin, aka SECURITY-624. |
| CVE-2017-1000109 | Medium | 2017-10-05 | No exploit published | No public exploit | The custom Details view of the Static Analysis Utilities based OWASP Dependency-Check Plugin, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to this plugin could insert arbitrary HTML into this view. |
| CVE-2014-9635 | Medium | 2017-09-12 | No exploit published | No public exploit | Jenkins before 1.586 does not set the HttpOnly flag in a Set-Cookie header for session cookies when run on Tomcat 7.0.41 or later, which makes it easier for remote attackers to obtain potentially sensitive information via script access to cookies. |
| CVE-2014-9634 | Medium | 2017-09-12 | No exploit published | No public exploit | Jenkins before 1.586 does not set the secure flag on session cookies when run on Tomcat 7.0.41 or later, which makes it easier for remote attackers to capture cookies by intercepting their transmission within an HTTP session. |
| 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-3727 | Medium | 2016-05-17 | No exploit published | No public exploit | The API URL computer/(master)/api/xml in Jenkins before 2.3 and LTS before 1.651.2 allows remote authenticated users with extended read permission for the master node to obtain sensitive information about the global configuration via unspecified vectors. |
| CVE-2016-3726 | High | 2016-05-17 | No exploit published | No public exploit | Multiple open redirect vulnerabilities in Jenkins before 2.3 and LTS before 1.651.2 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors related to "scheme-relative" URLs. |
| CVE-2016-3725 | Medium | 2016-05-17 | No exploit published | No public exploit | Jenkins before 2.3 and LTS before 1.651.2 allows remote authenticated users to trigger updating of update site metadata by leveraging a missing permissions check. NOTE: this issue can be combined with DNS cache poisoning to cause a denial of service (service disruption). |
| CVE-2016-3724 | Medium | 2016-05-17 | No exploit published | No public exploit | Jenkins before 2.3 and LTS before 1.651.2 allow remote authenticated users with extended read access to obtain sensitive password information by reading a job configuration. |
| CVE-2016-3723 | Medium | 2016-05-17 | No exploit published | No public exploit | Jenkins before 2.3 and LTS before 1.651.2 allow remote authenticated users with read access to obtain sensitive plugin installation information by leveraging missing permissions checks in unspecified XML/JSON API endpoints. |
| CVE-2016-3722 | Medium | 2016-05-17 | No exploit published | No public exploit | Jenkins before 2.3 and LTS before 1.651.2 allow remote authenticated users with multiple accounts to cause a denial of service (unable to login) by editing the "full name." |
| CVE-2016-3721 | Medium | 2016-05-17 | No exploit published | No public exploit | Jenkins before 2.3 and LTS before 1.651.2 might allow remote authenticated users to inject arbitrary build parameters into the build environment via environment variables. |
| CVE-2016-0792 | High | 2016-04-07 | Mitigation candidate | Working exploit published | Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and groovy.util.Expando. |
| 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-0790 | Medium | 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 API tokens, which makes it easier for remote attackers to determine API tokens via a brute-force approach. |
| CVE-2016-0789 | Medium | 2016-04-07 | No exploit published | No public exploit | CRLF injection vulnerability in the CLI command documentation in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors. |
| 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-7539 | High | 2016-02-03 | No exploit published | No public exploit | The Plugins Manager in Jenkins before 1.640 and LTS before 1.625.2 does not verify checksums for plugin files referenced in update site data, which makes it easier for man-in-the-middle attackers to execute arbitrary code via a crafted plugin. |
| CVE-2015-7538 | High | 2016-02-03 | No exploit published | No public exploit | Jenkins before 1.640 and LTS before 1.625.2 allow remote attackers to bypass the CSRF protection mechanism via unspecified vectors. |
| CVE-2015-7537 | High | 2016-02-03 | No exploit published | No public exploit | Cross-site request forgery (CSRF) vulnerability in Jenkins before 1.640 and LTS before 1.625.2 allows remote attackers to hijack the authentication of administrators for requests that have unspecified impact via vectors related to the HTTP GET method. |
| CVE-2015-7536 | Medium | 2016-02-03 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in Jenkins before 1.640 and LTS before 1.625.2 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors related to workspaces and archived artifacts. |
| 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'". |
| CVE-2015-5326 | Medium | 2015-11-25 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in the slave overview page in Jenkins before 1.638 and LTS before 1.625.2 allows remote authenticated users with certain permissions to inject arbitrary web script or HTML via the slave offline status message. |
| CVE-2015-5325 | High | 2015-11-25 | No exploit published | No public exploit | Jenkins before 1.638 and LTS before 1.625.2 allow attackers to bypass intended slave-to-master access restrictions by leveraging a JNLP slave. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-3665. |
| CVE-2015-5324 | Medium | 2015-11-25 | No exploit published | No public exploit | Jenkins before 1.638 and LTS before 1.625.2 allow remote attackers to obtain sensitive information via a direct request to queue/api. |
| CVE-2015-5323 | Medium | 2015-11-25 | No exploit published | No public exploit | Jenkins before 1.638 and LTS before 1.625.2 do not properly restrict access to API tokens which might allow remote administrators to gain privileges and run scripts by using an API token of another user. |
| CVE-2015-5322 | Medium | 2015-11-25 | Protected by Waratek | No public exploit | Directory traversal vulnerability in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to list directory contents and read arbitrary files in the Jenkins servlet resources via directory traversal sequences in a request to jnlpJars/. |
| CVE-2015-5321 | Medium | 2015-11-25 | No exploit published | No public exploit | The sidepanel widgets in the CLI command overview and help pages in Jenkins before 1.638 and LTS before 1.625.2 allow remote attackers to obtain sensitive information via a direct request to the pages. |
| CVE-2015-5320 | Medium | 2015-11-25 | No exploit published | No public exploit | Jenkins before 1.638 and LTS before 1.625.2 do not properly verify the shared secret used in JNLP slave connections, which allows remote attackers to connect as slaves and obtain sensitive information or possibly gain administrative access by leveraging knowledge of the name of a slave. |
| CVE-2015-5319 | Medium | 2015-11-25 | Protected by Waratek | No public exploit | XML external entity (XXE) vulnerability in the create-job CLI command in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to read arbitrary files via a crafted job configuration that is then used in an "XML-aware tool," as demonstrated by get-job and update-job. |
| CVE-2015-5318 | Medium | 2015-11-25 | No exploit published | No public exploit | Jenkins before 1.638 and LTS before 1.625.2 uses a publicly accessible salt to generate CSRF protection tokens, which makes it easier for remote attackers to bypass the CSRF protection mechanism via a brute force attack. |
| CVE-2014-3665 | Medium | 2015-11-25 | No exploit published | No public exploit | Jenkins before 1.587 and LTS before 1.580.1 do not properly ensure trust separation between a master and slaves, which might allow remote attackers to execute arbitrary code on the master by leveraging access to the slave. |
| CVE-2015-1814 | High | 2015-10-16 | No exploit published | No public exploit | The API token-issuing service in Jenkins before 1.606 and LTS before 1.596.2 allows remote attackers to gain privileges via a "forced API token change" involving anonymous users. |
| CVE-2015-1813 | Medium | 2015-10-16 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in Jenkins before 1.606 and LTS before 1.596.2 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2015-1812. |
| CVE-2015-1812 | Medium | 2015-10-16 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in Jenkins before 1.606 and LTS before 1.596.2 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2015-1813. |
| CVE-2015-1810 | Medium | 2015-10-16 | No exploit published | No public exploit | The HudsonPrivateSecurityRealm class in Jenkins before 1.600 and LTS before 1.596.1 does not restrict access to reserved names when using the "Jenkins' own user database" setting, which allows remote attackers to gain privileges by creating a reserved name. |
| CVE-2015-1808 | Low | 2015-10-16 | No exploit published | No public exploit | Jenkins before 1.600 and LTS before 1.596.1 allows remote authenticated users to cause a denial of service (improper plug-in and tool installation) via crafted update center data. |
| CVE-2015-1806 | Medium | 2015-10-16 | No exploit published | No public exploit | The combination filter Groovy script in Jenkins before 1.600 and LTS before 1.596.1 allows remote authenticated users with job configuration permission to gain privileges and execute arbitrary code on the master via unspecified vectors. |
| CVE-2014-2068 | Low | 2014-10-17 | No exploit published | No public exploit | The doIndex function in hudson/util/RemotingDiagnostics.java in CloudBees Jenkins before 1.551 and LTS before 1.532.2 allows remote authenticated users with the ADMINISTER permission to obtain sensitive information via vectors related to heapDump. |
| CVE-2014-2066 | Medium | 2014-10-17 | No exploit published | No public exploit | Session fixation vulnerability in Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to hijack web sessions via vectors involving the "override" of Jenkins cookies. |
| CVE-2014-2065 | Medium | 2014-10-17 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to inject arbitrary web script or HTML via the iconSize cookie. |
| CVE-2014-2064 | Medium | 2014-10-17 | No exploit published | No public exploit | The loadUserByUsername function in hudson/security/HudsonPrivateSecurityRealm.java in Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to determine whether a user exists via vectors related to failed login attempts. |
| CVE-2014-2063 | High | 2014-10-17 | No exploit published | No public exploit | Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to conduct clickjacking attacks via unspecified vectors. |
| CVE-2014-2062 | Medium | 2014-10-17 | No exploit published | No public exploit | Jenkins before 1.551 and LTS before 1.532.2 does not invalidate the API token when a user is deleted, which allows remote authenticated users to retain access via the token. |
| CVE-2014-2061 | Medium | 2014-10-17 | No exploit published | No public exploit | The input control in PasswordParameterDefinition in Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to obtain passwords by reading the HTML source code, related to the default value. |
| CVE-2014-2060 | Medium | 2014-10-17 | No exploit published | No public exploit | The Winstone servlet container in Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to hijack sessions via unspecified vectors. |