Overview 238 matches · 32 protected · 7 exploited · 4 CISA KEV · 15 public PoC · 12 EPSS ≥ 0.5
Protected by Waratek
32
13.4%
Rule in development
0
0.0%
Mitigation candidate
10
4.2%
No exploit published
196
82.4%
blocked by ARMR today
32
13.4%
partly blocked
0
0.0%
not blocked
206
86.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 57 / year
201612
Protected by Waratek1
Mitigation candidate1
No exploit published10
Critical2
High2
Medium8
blocked by ARMR today1
not blocked11
Working exploit published1
No public exploit11
20175
Mitigation candidate1
No exploit published4
Critical2
Medium3
not blocked5
Exploited1
No public exploit4
201857
Protected by Waratek6
Mitigation candidate1
No exploit published50
Critical2
High13
Medium40
Low2
blocked by ARMR today6
not blocked51
Exploited2
Working exploit published1
No public exploit54
201925
Protected by Waratek3
Mitigation candidate1
No exploit published21
High7
Medium18
blocked by ARMR today3
not blocked22
Working exploit published1
No public exploit24
202022
Protected by Waratek2
Mitigation candidate4
No exploit published16
High5
Medium17
blocked by ARMR today2
not blocked20
Working exploit published4
No public exploit18
202131
Protected by Waratek6
No exploit published25
Critical10
High7
Medium14
blocked by ARMR today6
not blocked25
Forecast only1
No public exploit30
202211
Protected by Waratek4
No exploit published7
High5
Medium6
blocked by ARMR today4
not blocked7
Proof of concept only1
No public exploit10
202316
Mitigation candidate1
No exploit published15
Critical1
High9
Medium6
not blocked16
Exploited1
No public exploit15
20246
Protected by Waratek2
No exploit published4
Critical1
High2
Medium3
blocked by ARMR today2
not blocked4
Exploited1
Proof of concept only1
Forecast only1
No public exploit3
202514
Mitigation candidate1
No exploit published13
High1
Medium12
Low1
not blocked14
Exploited1
No public exploit13
202639
Protected by Waratek8
No exploit published31
High18
Medium19
Low2
blocked by ARMR today8
not blocked31
Exploited1
No public exploit38
20162017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-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-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. |