Overview 4 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
25.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
75.0%
blocked by ARMR today
1
25.0%
partly blocked
0
0.0%
not blocked
3
75.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
4
100.0%
split by
peak 1 / month
Apr 191
No exploit published1
High1
not blocked1
No public exploit1
May 191
No exploit published1
Medium1
not blocked1
No public exploit1
Jun 190
Jul 191
No exploit published1
Medium1
not blocked1
No public exploit1
Aug 190
Sep 190
Oct 191
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
Apr 19May 19Jun 19Jul 19Aug 19Sep 19Oct 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-10436 | Medium | 2019-10-16 | Protected by Waratek | No public exploit | An arbitrary file read vulnerability in Jenkins Google OAuth Credentials Plugin 0.9 and earlier allowed attackers able to configure jobs and credentials in Jenkins to obtain the contents of any file on the Jenkins master. |
| CVE-2019-1010241 | Medium | 2019-07-19 | No exploit published | No public exploit | Jenkins Credentials Binding Plugin Jenkins 1.17 is affected by: CWE-257: Storing Passwords in a Recoverable Format. The impact is: Authenticated users can recover credentials. The component is: config-variables.jelly line #30 (passwordVariable). The attack vector is: Attacker creates and executes a Jenkins job. |
| CVE-2019-10320 | Medium | 2019-05-21 | No exploit published | No public exploit | Jenkins Credentials Plugin 2.1.18 and earlier allowed users with permission to create or update credentials to confirm the existence of files on the Jenkins master with an attacker-specified path, and obtain the certificate content of files containing a PKCS#12 certificate. |
| CVE-2019-10303 | High | 2019-04-18 | No exploit published | No public exploit | Jenkins Azure PublisherSettings Credentials Plugin 1.2 and earlier stored credentials unencrypted in the credentials.xml file on the Jenkins master where they could be viewed by users with access to the master file system. |