GHSA-v58w-6xc2-w799 CVE-2012-1987
Puppet Denial of Service and Arbitrary File Write
- Severity
- Low
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 2.52%
- Chance of exploitation in the next 30 days. Higher than 84.87% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
2.6.15- Upgrade puppet to this version or later
Description
A 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.
Affected versions
RubyGems
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
puppet RubyGems → 2.6.15
- bundler
bundle update puppet # Gemfile: gem "puppet", ">= 2.6.15"
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
- github.com/puppetlabs/puppet/commit/0d6d29933e613fe177e9235415919a5428db67bc
- github.com/puppetlabs/puppet/commit/568ded50ec6cc498ad32ff7f086d9f73b5d24c14
- exchange.xforce.ibmcloud.com/vulnerabilities/74794
- github.com/rubysec/ruby-advisory-db/blob/master/gems/puppet/CVE-2012-1987.yml
- hermes.opensuse.org/messages/14523305
- hermes.opensuse.org/messages/15087408
- web.archive.org/web/20120415105345/http://www.securityfocus.com/bid/52975
- web.archive.org/web/20120513213318/http://projects.puppetlabs.com/issues/13553
- web.archive.org/web/20120513224202/http://projects.puppetlabs.com/issues/13552
- web.archive.org/web/20121005145241/http://projects.puppetlabs.com/projects/1/wiki/Re…
- web.archive.org/web/20160808163232/https://puppet.com/security/cve/cve-2012-1987
- lists.fedoraproject.org/pipermail/package-announce/2012-April/079227.html
- lists.fedoraproject.org/pipermail/package-announce/2012-April/079289.html
- lists.fedoraproject.org/pipermail/package-announce/2012-May/080003.html
- ubuntu.com/usn/usn-1419-1
- debian.org/security/2012/dsa-2451
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-mpmx-gm5v-q789 Puppet uses predictable filenames, allowing arbitrary file overwrite | Medium | Also affects puppet |
| GHSA-9pvx-fwwh-w289 Puppet does not properly restrict access to node resources | Medium | Also affects puppet |
| GHSA-qh3g-27jf-3j54 Puppet allows local users to modify the permissions of arbitrary files | Medium | Also affects puppet |
| GHSA-8c56-v25w-f89c Puppet arbitrary file overwrite | Medium | Also affects puppet |
| GHSA-c4mc-49hq-q275 Puppet uses predictable filenames, allowing arbitrary file overwrite | Medium | Also affects puppet |
| GHSA-6xxq-j39w-g3f6 Puppet Arbitrary Command Execution | Medium | Also affects puppet |
| GHSA-77hg-g8cc-5r37 Puppet Privilege Escallation | Medium | Also affects puppet |
| GHSA-vw22-465p-8j5w Tarball permission preservation in puppet | Medium | Also affects puppet |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor