Tarball permission preservation in puppet
When installing a module using the system tar, the PMT will filter filesystem permissions to a sane value. This may just be based on the user's umask. When using minitar, files are unpacked with whatever permissions are in the tarball. This is potentially unsafe, as tarballs can be easily created with weird permissions.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-10689US | medium5.5 | — | ||
In previous versions of Puppet Agent it was possible to install a module with world writable permissions. Puppet Agent 5.3.4 and 1.10.10 included a fix to this vulnerability. | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2018:2927WEB
- https://github.com/puppetlabs/puppetPACKAGE
- https://github.com/puppetlabs/puppet/commit/17d9e02da3882e44c1876e2805cf9708481715eeWEB
- https://github.com/puppetlabs/puppet/commit/2f1047f85e22cde139a421bc25d371f2ffc92cb1WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/puppet/CVE-2017-10689.ymlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-10689ADVISORY
- https://puppet.com/security/cve/CVE-2017-10689WEB
- https://tickets.puppetlabs.com/browse/PUP-7866WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan