CVE-2012-4284 in the critical feed json
A Privilege Escalation vulnerability exists in Viscosity 1.4.1 on Mac OS X due to a path name validation issue in the setuid-set ViscosityH…
published 2020-01-10 6 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4228
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 69.5%
- EPSS 69.5% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
A Privilege Escalation vulnerability exists in Viscosity 1.4.1 on Mac OS X due to a path name validation issue in the setuid-set ViscosityHelper binary, which could let a remote malicious user execute arbitrary code
Timeline
- First public exploit (Metasploit exploit/osx/local/setuid_viscosity)
- Published
Exploit prediction
69.52% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/osx/local/setuid_viscosity Viscosity setuid-set ViscosityHelper Privilege Escalation metasploit exploit, excellent rank, 2012-08-12
- EDB-24579 Viscosity - setuid-set ViscosityHelper Privilege Escalation (Metasploit) local, 2013-03-05
- EDB-20485 Viscosity - Local Privilege Escalation local, 2012-08-13
- packetstormsecurity.com https://packetstormsecurity.com/files/120643/Viscosity-setuid-set-ViscosityHelper-Privilege-Escalation.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
exploit-db.com
/exploits/24579
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/120643/Viscosity-setuid-set-ViscosityHelper-Privilege-Escalation.html
exploit, third-party-advisory, vdb-entry
-
sparklabs.com
/viscosity/releasenotes/mac/
release-notes, vendor-advisory
-
securityfocus.com
/bid/55002
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2012-4284
- NVD CVE-2012-4284
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.