How severe is CVE-2014-3248?

No CVSS score has been assigned to CVE-2014-3248 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-3248?

CVE-2014-3248 affects the following packages: facter (RubyGems), facter (RubyGems), hiera (RubyGems), puppet (RubyGems), puppet (RubyGems), mcollective-client (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2014-3248?

Update facter to 1.7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3248 is resolved across your whole dependency graph.

How do I detect CVE-2014-3248 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facter. 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 CVE-2014-3248 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 CVE-2014-3248?

O3 pinpoints whether CVE-2014-3248 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 CVE-2014-3248 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-3248, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2014-3248?

CVE-2014-3248 is classified as CWE-17 (CWE-17). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-3248 published, and has it been updated?

CVE-2014-3248 was published on November 16, 2014 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

CVE-2014-3248

CVE-2014-3248 is a CWE-17 vulnerability in facter. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2014-3248 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

facter, hiera, mcollective-client, and puppet affected by untrusted search path vulnerability

Also known asGHSA-92v7-pq4h-58j5

Published

Nov 16, 2014

Updated

Apr 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

1 known

Blast Radius

6 pkgs affected

💎facter💎facter💎hiera💎puppet💎puppet💎mcollective-client

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

Untrusted search path vulnerability in Puppet Enterprise 2.8 before 2.8.7, Puppet before 2.7.26 and 3.x before 3.6.2, Facter 1.6.x and 2.x before 2.0.2, Hiera before 1.3.4, and Mcollective before 2.5.2, when running with Ruby 1.9.1 or earlier, allows local users to gain privileges via a Trojan horse file in the current working directory, as demonstrated using (1) rubygems/defaults/operating_system.rb, (2) Win32API.rb, (3) Win32API.so, (4) safe_yaml.rb, (5) safe_yaml/deep.rb, or (6) safe_yaml/deep.so; or (7) operatingsystem.rb, (8) operatingsystem.so, (9) osfamily.rb, or (10) osfamily.so in puppet/confine.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`facter`	all versions	1.7.6
💎RubyGems	`facter`	≥ 2.0.0&&< 2.0.2	2.0.2
💎RubyGems	`hiera`	all versions	1.3.4
💎RubyGems	`puppet`	all versions	2.7.26
💎RubyGems	`puppet`	≥ 3.0.0&&< 3.6.2	3.6.2
💎RubyGems	`mcollective-client`	all versions	2.5.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Untrusted search path vulnerability in Puppet Enterprise 2.8 before 2.8.…

rowediness.comNVDJul 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facter. 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 facter to 1.7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3248 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 CVE-2014-3248 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 CVE-2014-3248. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3248 in your dependencies?

O3 detects CVE-2014-3248 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