CVE-2018-6508
puppet: Unparameterized input in multiple modules can allow a remote user to execute arbitrary code
Overview
Description
Puppet Enterprise 2017.3.x prior to 2017.3.3 are vulnerable to a remote execution bug when a specially crafted string was passed into the facter_task or puppet_conf tasks. This vulnerability only affects tasks in the affected modules, if you are not using puppet tasks you are not affected by this vulnerability.
Source: OX vulnerability database
Severity
8 · HIGH
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Weakness: CWE-134
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 15 fixes
Red Hat 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 7 | puppet-apache +1 | affected |
debian 4 releases · 3 packages
| Release | Package | Fixed in |
|---|---|---|
| 11 | puppet-module-puppetlabs-apache | 3.0.0-1 |
| 11 | puppet-module-puppetlabs-apt | 4.5.1-1 |
| 11 | puppet-module-puppetlabs-mysql | 5.3.0-1 |
| 12 | puppet-module-puppetlabs-apache | 3.0.0-1 |
| 12 | puppet-module-puppetlabs-apt | 4.5.1-1 |
| 12 | puppet-module-puppetlabs-mysql | 5.3.0-1 |
5 more rows
echo 1 release · 3 packages
| Release | Package | Fixed in |
|---|---|---|
| puppet-module-puppetlabs-apache | 3.0.0-1 | |
| puppet-module-puppetlabs-apt | 4.5.1-1 | |
| puppet-module-puppetlabs-mysql | 5.3.0-1 |
References
- www.securityfocus.com http://www.securityfocus.com/bid/103020
- access.redhat.com https://access.redhat.com/security/cve/CVE-2018-6508
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2018-6508
- puppet.com https://puppet.com/security/cve/CVE-2018-6508
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2018-6508
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.