Overview 118 matches · 1 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 3 public PoC · 1 EPSS ≥ 0.5
118matches
1in Waratek scope0.8%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
3public PoC2.5%
1EPSS ≥ 0.50.8%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
0.8%
Outside Waratek scope
2
1.7%
Not applicable
115
97.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
118
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
0.8%
Proof of concept only
3
2.5%
Forecast only
0
0.0%
No public exploit
114
96.6%
split by
peak 21 / year
20091
Not applicable1
Medium1
not blocked1
No public exploit1
20101
Not applicable1
Low1
not blocked1
No public exploit1
20115
Not applicable5
Medium4
Low1
not blocked5
Proof of concept only1
No public exploit4
201212
Not applicable12
Medium5
Low7
not blocked12
No public exploit12
201321
Not applicable21
High4
Medium15
Low2
not blocked21
No public exploit21
201414
Not applicable14
High1
Medium11
Low2
not blocked14
No public exploit14
20150
20164
Not applicable4
Critical2
High1
Medium1
not blocked4
No public exploit4
201720
Not applicable20
Critical3
High7
Medium10
not blocked20
Proof of concept only1
No public exploit19
201816
Outside Waratek scope2
Not applicable14
Critical2
High7
Medium7
not blocked16
No public exploit16
20195
No exploit published1
Not applicable4
Critical2
Medium3
not blocked5
No public exploit5
20203
Not applicable3
High2
Medium1
not blocked3
Working exploit published1
No public exploit2
20217
Not applicable7
Critical1
High2
Medium4
not blocked7
No public exploit7
20223
Not applicable3
Critical1
High1
Medium1
not blocked3
No public exploit3
20235
Not applicable5
Critical2
High2
Medium1
not blocked5
Proof of concept only1
No public exploit4
20240
20251
Not applicable1
High1
not blocked1
No public exploit1
200920112013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2012-3866 | Low | 2012-08-06 | Not applicable | No public exploit | lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml, which allows local users to obtain sensitive configuration information by leveraging access to the puppet master server to read this file. |
| CVE-2012-3865 | Low | 2012-08-06 | Not applicable | No public exploit | Directory traversal vulnerability in lib/puppet/reports/store.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, when Delete is enabled in auth.conf, allows remote authenticated users to delete arbitrary files on the puppet master server via a .. (dot dot) in a node name. |
| CVE-2012-3864 | Medium | 2012-08-06 | Not applicable | No public exploit | Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, allows remote authenticated users to read arbitrary files on the puppet master server by leveraging an arbitrary user's certificate and private key in a GET request. |
| CVE-2012-3408 | Low | 2012-08-06 | Not applicable | No public exploit | lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address. |
| CVE-2012-1989 | Low | 2012-06-27 | Not applicable | No public exploit | telnet.rb in Puppet 2.7.x before 2.7.13 and Puppet Enterprise (PE) 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows local users to overwrite arbitrary files via a symlink attack on the NET::Telnet connection log (/tmp/out.log). |
| CVE-2012-1988 | Medium | 2012-05-29 | Not applicable | No public exploit | Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows remote authenticated users with agent SSL keys and file-creation permissions on the puppet master to execute arbitrary commands by creating a file whose full pathname contains shell metacharacters, then performing a filebucket request. |
| CVE-2012-1987 | Low | 2012-05-29 | Not applicable | No public exploit | Unspecified vulnerability in Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows remote authenticated users with agent SSL keys to (1) cause a denial of service (memory consumption) via a REST request to a stream that triggers a thread block, as demonstrated using CVE-2012-1986 and /dev/random; or (2) cause a denial of service (filesystem consumption) via crafted REST requests that use "a marshaled form of a Puppet::FileBucket::File object" to write to arbitrary file locations. |
| CVE-2012-1986 | Low | 2012-05-29 | Not applicable | No public exploit | Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1 allows remote authenticated users with an authorized SSL key and certain permissions on the puppet master to read arbitrary files via a symlink attack in conjunction with a crafted REST request for a file in a filebucket. |
| CVE-2012-1906 | Low | 2012-05-29 | Not applicable | No public exploit | Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1 uses predictable file names when installing Mac OS X packages from a remote source, which allows local users to overwrite arbitrary files or install arbitrary packages via a symlink attack on a temporary file in /tmp. |
| CVE-2012-1054 | Medium | 2012-05-29 | Not applicable | No public exploit | Puppet 2.6.x before 2.6.14 and 2.7.x before 2.7.11, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x before 2.0.3, when managing a user login file with the k5login resource type, allows local users to gain privileges via a symlink attack on .k5login. |
| CVE-2012-1053 | Medium | 2012-05-29 | Not applicable | No public exploit | The change_user method in the SUIDManager (lib/puppet/util/suidmanager.rb) in Puppet 2.6.x before 2.6.14 and 2.7.x before 2.7.11, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x before 2.0.3 does not properly manage group privileges, which allows local users to gain privileges via vectors related to (1) the change_user not dropping supplementary groups in certain conditions, (2) changes to the eguid without associated changes to the egid, or (3) the addition of the real gid to supplementary groups. |
| CVE-2011-3872 | Low | 2011-10-27 | Not applicable | Proof of concept only | Puppet 2.6.x before 2.6.12 and 2.7.x before 2.7.6, and Puppet Enterprise (PE) Users 1.0, 1.1, and 1.2 before 1.2.4, when signing an agent certificate, adds the Puppet master's certdnsnames values to the X.509 Subject Alternative Name field of the certificate, which allows remote attackers to spoof a Puppet master via a man-in-the-middle (MITM) attack against an agent that uses an alternate DNS name for the master, aka "AltNames Vulnerability." |
| CVE-2011-3871 | Medium | 2011-10-27 | Not applicable | No public exploit | Puppet 2.7.x before 2.7.5, 2.6.x before 2.6.11, and 0.25.x, when running in --edit mode, uses a predictable file name, which allows local users to run arbitrary Puppet code or trick a user into editing arbitrary files. |
| CVE-2011-3870 | Medium | 2011-10-27 | Not applicable | No public exploit | Puppet 2.7.x before 2.7.5, 2.6.x before 2.6.11, and 0.25.x allows local users to modify the permissions of arbitrary files via a symlink attack on the SSH authorized_keys file. |
| CVE-2011-3869 | Medium | 2011-10-27 | Not applicable | No public exploit | Puppet 2.7.x before 2.7.5, 2.6.x before 2.6.11, and 0.25.x allows local users to overwrite arbitrary files via a symlink attack on the .k5login file. |
| CVE-2011-3848 | Medium | 2011-10-27 | Not applicable | No public exploit | Directory traversal vulnerability in Puppet 2.6.x before 2.6.10 and 2.7.x before 2.7.4 allows remote attackers to write X.509 Certificate Signing Request (CSR) to arbitrary locations via (1) a double-encoded key parameter in the URI in 2.7.x, (2) the CN in the Subject of a CSR in 2.6 and 0.25. |
| CVE-2010-0156 | Low | 2010-03-03 | Not applicable | No public exploit | Puppet 0.24.x before 0.24.9 and 0.25.x before 0.25.2 allows local users to overwrite arbitrary files via a symlink attack on the (1) /tmp/daemonout, (2) /tmp/puppetdoc.txt, (3) /tmp/puppetdoc.tex, or (4) /tmp/puppetdoc.aux temporary file. |
| CVE-2009-3564 | Medium | 2009-10-06 | Not applicable | No public exploit | puppetmasterd in puppet 0.24.6 does not reset supplementary groups when it switches to a different user, which might allow local users to access restricted files. |