Untrusted search path vulnerability in the installation functionality in Ruby 1.9.3-p194, when installed in the top-level C:\ directory, mi…

published 2012-10-11 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5299

cvss: 6.7; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 1; Exploit-DB

Untrusted search path vulnerability in the installation functionality in Ruby 1.9.3-p194, when installed in the top-level C:\ directory, might allow local users to gain privileges via a Trojan horse DLL in the C:\Ruby193\bin directory, which may be added to the PATH system environment variable by an administrator, as demonstrated by a Trojan horse wlbsctrl.dll file used by the "IKE and AuthIP IPsec Keying Modules" system service in Windows Vista SP1, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8 Release Preview. NOTE: CVE disputes this issue because the unsafe PATH is established only by a separate administrative action that is not a default part of the Ruby installation

Timeline

2012-10-11 Published
2013-09-06 First public exploit (EDB-28130)

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-04-22)

Exploit prediction

0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-28130 IKE and AuthIP IPsec Keyring Modules Service (IKEEXT) - Missing DLL (Metasploit) local, 2013-09-06
htbridge.com https://www.htbridge.com/advisory/HTB23108 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	6.7	CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA	3.1	6.7	CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.0	AV:L/AC:H/Au:S/C:C/I:C/A:C

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

htbridge.com /advisory/HTB23108
exploit

Sources

CVE List CVE-2012-5380
NVD CVE-2012-5380

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary