How severe is GHSA-v58w-6xc2-w799?

No CVSS score has been assigned to GHSA-v58w-6xc2-w799 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v58w-6xc2-w799?

GHSA-v58w-6xc2-w799 affects the following packages: puppet (RubyGems), puppet (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-v58w-6xc2-w799?

Update puppet to 2.6.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v58w-6xc2-w799 is resolved across your whole dependency graph.

How do I detect GHSA-v58w-6xc2-w799 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for puppet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v58w-6xc2-w799 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v58w-6xc2-w799?

O3 pinpoints whether GHSA-v58w-6xc2-w799 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v58w-6xc2-w799 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v58w-6xc2-w799 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-v58w-6xc2-w799 published, and has it been updated?

GHSA-v58w-6xc2-w799 was published on May 14, 2022 and was last updated on December 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

GHSA-v58w-6xc2-w799

GHSA-v58w-6xc2-w799 is a security vulnerability in puppet. O3 Security confirms whether GHSA-v58w-6xc2-w799 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Puppet Denial of Service and Arbitrary File Write

Also known asCVE-2012-1987

Published

May 14, 2022

Updated

Dec 7, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

💎puppet💎puppet

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

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 Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`puppet`	≥ 2.6.0&&< 2.6.15	2.6.15
💎RubyGems	`puppet`	≥ 2.7.0&&< 2.7.13	2.7.13

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for puppet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update puppet to 2.6.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v58w-6xc2-w799 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v58w-6xc2-w799 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v58w-6xc2-w799. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-v58w-6xc2-w799 in your dependencies?

O3 detects GHSA-v58w-6xc2-w799 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works