Overview 18 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
18matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
18
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
18
100.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
18
100.0%
split by
peak 4 / year
20162
Not applicable2
Critical2
not blocked2
No public exploit2
20174
Not applicable4
Critical4
not blocked4
No public exploit4
20183
Not applicable3
Critical3
not blocked3
No public exploit3
20193
Not applicable3
Critical3
not blocked3
No public exploit3
20200
20211
Not applicable1
Critical1
not blocked1
No public exploit1
20222
Not applicable2
Critical2
not blocked2
No public exploit2
20233
Not applicable3
Critical3
not blocked3
No public exploit3
20162017201820192020202120222023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-5309 | Critical | 2023-11-07 | Not applicable | No public exploit | Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations. |
| CVE-2023-5214 | Critical | 2023-10-06 | Not applicable | No public exploit | In Puppet Bolt versions prior to 3.27.4, a path to escalate privileges was identified. |
| CVE-2023-2530 | Critical | 2023-06-07 | Not applicable | No public exploit | A privilege escalation allowing remote code execution was discovered in the orchestration service. |
| CVE-2022-3275 | Critical | 2022-10-07 | Not applicable | No public exploit | Command injection is possible in the puppetlabs-apt module prior to version 9.0.0. A malicious actor is able to exploit this vulnerability only if they are able to provide unsanitized input to the module. This condition is rare in most deployments of Puppet and Puppet Enterprise. |
| CVE-2022-0675 | Critical | 2022-03-02 | Not applicable | No public exploit | In certain situations it is possible for an unmanaged rule to exist on the target system that has the same comment as the rule specified in the manifest. This could allow for unmanaged rules to exist on the target system and leave the system in an unsafe state. |
| CVE-2021-27023 | Critical | 2021-11-18 | Not applicable | No public exploit | A flaw was discovered in Puppet Agent and Puppet Server that may result in a leak of HTTP credentials when following HTTP redirects to a different host. This is similar to CVE-2018-1000007 |
| CVE-2014-0175 | Critical | 2019-12-13 | Not applicable | No public exploit | mcollective has a default password set at install |
| CVE-2019-10694 | Critical | 2019-12-12 | Not applicable | No public exploit | The express install, which is the suggested way to install Puppet Enterprise, gives the user a URL at the end of the install to set the admin password. If they do not use that URL, there is an overlooked default password for the admin user. This was resolved in Puppet Enterprise 2019.0.3 and 2018.1.9. |
| CVE-2018-11747 | Critical | 2019-03-21 | Not applicable | No public exploit | Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. In version 1.4.0, a unique certificate will be generated on installation or the user will be able to provide their own TLS certificate for ingress. |
| CVE-2018-11749 | Critical | 2018-08-24 | Not applicable | No public exploit | When users are configured to use startTLS with RBAC LDAP, at login time, the user's credentials are sent via plaintext to the LDAP server. This affects Puppet Enterprise 2018.1.3, 2017.3.9, and 2016.4.14, and is fixed in Puppet Enterprise 2018.1.4, 2017.3.10, and 2016.4.15. It scored an 8.5 CVSS score. |
| CVE-2018-11746 | Critical | 2018-07-03 | Not applicable | No public exploit | In Puppet Discovery prior to 1.2.0, when running Discovery against Windows hosts, WinRM connections can fall back to using basic auth over insecure channels if a HTTPS server is not available. This can expose the login credentials being used by Puppet Discovery. |
| CVE-2018-6512 | Critical | 2018-06-11 | Not applicable | No public exploit | The previous version of Puppet Enterprise 2018.1 is vulnerable to unsafe code execution when upgrading pe-razor-server. Affected releases are Puppet Enterprise: 2018.1.x versions prior to 2018.1.1 and razor-server and pe-razor-server prior to 1.9.0.0. |
| CVE-2015-7224 | Critical | 2017-12-21 | Not applicable | No public exploit | puppetlabs-mysql 3.1.0 through 3.6.0 allow remote attackers to bypass authentication by leveraging creation of a database account without a password when a 'mysql_user' user parameter contains a host with a netmask. |
| CVE-2016-5713 | Critical | 2017-12-06 | Not applicable | No public exploit | Versions of Puppet Agent prior to 1.6.0 included a version of the Puppet Execution Protocol (PXP) agent that passed environment variables through to Puppet runs. This could allow unauthorized code to be loaded. This bug was first introduced in Puppet Agent 1.3.0. |
| CVE-2017-2292 | Critical | 2017-06-30 | Not applicable | No public exploit | Versions of MCollective prior to 2.10.4 deserialized YAML from agents without calling safe_load, allowing the potential for arbitrary code execution on the server. The fix for this is to call YAML.safe_load on input. This has been tested in all Puppet-supplied MCollective plugins, but there is a chance that third-party plugins could rely on this insecure behavior. |
| CVE-2016-2788 | Critical | 2017-02-13 | Not applicable | No public exploit | MCollective 2.7.0 and 2.8.x before 2.8.9, as used in Puppet Enterprise, allows remote attackers to execute arbitrary code via vectors related to the mco ping command. |
| CVE-2016-2786 | Critical | 2016-06-10 | Not applicable | No public exploit | The pxp-agent component in Puppet Enterprise 2015.3.x before 2015.3.3 and Puppet Agent 1.3.x before 1.3.6 does not properly validate server certificates, which might allow remote attackers to spoof brokers and execute arbitrary commands via a crafted certificate. |
| CVE-2016-2785 | Critical | 2016-06-10 | Not applicable | No public exploit | Puppet Server before 2.3.2 and Ruby puppetmaster in Puppet 4.x before 4.4.2 and in Puppet Agent before 1.4.2 might allow remote attackers to bypass intended auth.conf access restrictions by leveraging incorrect URL decoding. |