Overview 117 matches · 11 protected · 4 exploited · 1 CISA KEV · 9 public PoC · 6 EPSS ≥ 0.5
Protected by Waratek
11
9.4%
Rule in development
0
0.0%
Mitigation candidate
6
5.1%
No exploit published
100
85.5%
blocked by ARMR today
11
9.4%
partly blocked
0
0.0%
not blocked
106
90.6%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 23 / quarter
Q3 171
Protected by Waratek1
High1
blocked by ARMR today1
Exploited1
Q4 174
No exploit published4
High1
Medium2
Low1
not blocked4
No public exploit4
Q1 181
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 189
Mitigation candidate1
No exploit published8
High2
Medium7
not blocked9
Exploited1
No public exploit8
Q3 180
Q4 180
Q1 194
No exploit published4
Medium4
not blocked4
No public exploit4
Q2 194
No exploit published4
High4
not blocked4
No public exploit4
Q3 197
Protected by Waratek1
No exploit published6
High2
Medium5
blocked by ARMR today1
not blocked6
Proof of concept only1
No public exploit6
Q4 193
Protected by Waratek1
No exploit published2
Critical1
Medium2
blocked by ARMR today1
not blocked2
No public exploit3
Q1 2017
Mitigation candidate5
No exploit published12
Critical3
High8
Medium6
not blocked17
Exploited2
Working exploit published1
Proof of concept only1
No public exploit13
Q2 204
Protected by Waratek1
No exploit published3
High4
blocked by ARMR today1
not blocked3
No public exploit4
Q3 207
Protected by Waratek1
No exploit published6
High3
Medium4
blocked by ARMR today1
not blocked6
No public exploit7
Q4 200
Q1 211
No exploit published1
High1
not blocked1
No public exploit1
Q2 219
Protected by Waratek2
No exploit published7
Medium8
Low1
blocked by ARMR today2
not blocked7
Working exploit published1
No public exploit8
Q3 2123
No exploit published23
High9
Medium14
not blocked23
No public exploit23
Q4 212
Protected by Waratek1
No exploit published1
High1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
Q1 2210
No exploit published10
High1
Medium9
not blocked10
No public exploit10
Q2 2211
Protected by Waratek3
No exploit published8
Critical1
High2
Medium8
blocked by ARMR today3
not blocked8
Working exploit published1
Forecast only1
No public exploit9
Q4 17Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21Q4 21Q2 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-1003010 | Medium | 2019-02-06 | No exploit published | No public exploit | A cross-site request forgery vulnerability exists in Jenkins Git Plugin 3.9.1 and earlier in src/main/java/hudson/plugins/git/GitTagAction.java that allows attackers to create a Git tag in a workspace and attach corresponding metadata to a build record. |
| CVE-2018-1000426 | Medium | 2019-01-09 | No exploit published | No public exploit | A cross-site scripting vulnerability exists in Jenkins Git Changelog Plugin 2.6 and earlier in GitChangelogSummaryDecorator/summary.jelly, GitChangelogLeftsideBuildDecorator/badge.jelly, GitLogJiraFilterPostPublisher/config.jelly, GitLogBasicChangelogPostPublisher/config.jelly that allows attackers able to control the Git history parsed by the plugin to have Jenkins render arbitrary HTML on some pages. |
| CVE-2018-1000600 | High | 2018-06-26 | Mitigation candidate | Exploited | A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCredentialsCreator.java that allows attackers to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2018-1000196 | Medium | 2018-06-05 | No exploit published | No public exploit | A exposure of sensitive information vulnerability exists in Jenkins Gitlab Hook Plugin 1.4.2 and older in gitlab_notifier.rb, views/gitlab_notifier/global.erb that allows attackers with local Jenkins master file system access or control of a Jenkins administrator's web browser (e.g. malicious extension) to retrieve the configured Gitlab token. |
| CVE-2018-1000186 | Medium | 2018-06-05 | No exploit published | No public exploit | A exposure of sensitive information vulnerability exists in Jenkins GitHub Pull Request Builder Plugin 1.41.0 and older in GhprbGitHubAuth.java that allows attackers with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2018-1000185 | Medium | 2018-06-05 | No exploit published | No public exploit | A server-side request forgery vulnerability exists in Jenkins GitHub Branch Source Plugin 2.3.4 and older in Endpoint.java that allows attackers with Overall/Read access to cause Jenkins to send a GET request to a specified URL. |
| CVE-2018-1000184 | Medium | 2018-06-05 | No exploit published | No public exploit | A server-side request forgery vulnerability exists in Jenkins GitHub Plugin 1.29.0 and older in GitHubPluginConfig.java that allows attackers with Overall/Read access to cause Jenkins to send a GET request to a specified URL. |
| CVE-2018-1000183 | Medium | 2018-06-05 | No exploit published | No public exploit | A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.0 and older in GitHubServerConfig.java that allows attackers with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2018-1000182 | Medium | 2018-06-05 | No exploit published | No public exploit | A server-side request forgery vulnerability exists in Jenkins Git Plugin 3.9.0 and older in AssemblaWeb.java, GitBlitRepositoryBrowser.java, Gitiles.java, TFS2013GitRepositoryBrowser.java, ViewGitWeb.java that allows attackers with Overall/Read access to cause Jenkins to send a GET request to a specified URL. |
| CVE-2018-1000143 | Medium | 2018-04-05 | No exploit published | No public exploit | An exposure of sensitive information vulnerability exists in Jenkins GitHub Pull Request Builder Plugin version 1.39.0 and older in GhprbCause.java that allows an attacker with local file system access to obtain GitHub credentials. |
| CVE-2018-1000142 | High | 2018-04-05 | No exploit published | No public exploit | An exposure of sensitive information vulnerability exists in Jenkins GitHub Pull Request Builder Plugin version 1.39.0 and older in GhprbCause.java that allows an attacker with local file system access to obtain GitHub credentials. |
| CVE-2018-1000110 | Medium | 2018-03-13 | No exploit published | No public exploit | An improper authorization vulnerability exists in Jenkins Git Plugin version 3.7.0 and earlier in GitStatus.java that allows an attacker with network access to obtain a list of nodes and users. |
| CVE-2017-1000242 | Low | 2017-11-01 | No exploit published | No public exploit | Jenkins Git Client Plugin 2.4.2 and earlier creates temporary file with insecure permissions resulting in information disclosure |
| CVE-2017-1000092 | High | 2017-10-05 | No exploit published | No public exploit | Git Plugin connects to a user-specified Git repository as part of form validation. An attacker with no direct access to Jenkins but able to guess at a username/password credentials ID could trick a developer with job configuration permissions into following a link with a maliciously crafted Jenkins URL which would result in the Jenkins Git client sending the username and password to an attacker-controlled server. |
| CVE-2017-1000091 | Medium | 2017-10-05 | No exploit published | No public exploit | GitHub Branch Source Plugin connects to a user-specified GitHub API URL (e.g. GitHub Enterprise) as part of form validation and completion (e.g. to verify Scan Credentials are correct). This functionality improperly checked permissions, allowing any user with Overall/Read access to Jenkins to connect to any web server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery. |
| CVE-2017-1000087 | Medium | 2017-10-05 | No exploit published | No public exploit | GitHub Branch Source provides a list of applicable credential IDs to allow users configuring a job to select the one they'd like to use. This functionality did not check permissions, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those could be used as part of an attack to capture the credentials using another vulnerability. |
| CVE-2017-9805 | High | 2017-09-15 | Protected by Waratek | Exploited | The REST Plugin in Apache Struts 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 uses an XStreamHandler with an instance of XStream for deserialization without any type filtering, which can lead to Remote Code Execution when deserializing XML payloads. |