CVE-2006-5327 json
Untrusted search path vulnerability in OpenBase SQL 10.0 and earlier, as used in Apple Xcode 2.2 2.2 and earlier and possibly other product…
published 2006-10-17 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5312
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Untrusted search path vulnerability in OpenBase SQL 10.0 and earlier, as used in Apple Xcode 2.2 2.2 and earlier and possibly other products, allows local users to execute arbitrary code via a modified PATH that references a malicious gzip program, which is executed by gnutar with certain TAR_OPTIONS environment variable settings, when gnutar is invoked by OpenBase.
Patch / fix
- secunia.com/advisories/22390 advisory
- secunia.com/advisories/22474 advisory
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/20562 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
secunia.com
/advisories/22390
third-party-advisory, patch, vendor-advisory
-
secunia.com
/advisories/22474
third-party-advisory, patch, vendor-advisory
-
securityfocus.com
/bid/20562
vdb-entry, exploit
-
lists.apple.com
/archives/security-announce/2007/Oct/msg00001.html
vendor-advisory
-
vupen.com
/english/advisories/2006/4058
vdb-entry
-
secunia.com
/advisories/27441
third-party-advisory
-
vupen.com
/english/advisories/2007/3665
vdb-entry
-
vupen.com
/english/advisories/2006/4059
vdb-entry
-
securitytracker.com
/id?1018872
vdb-entry
- digitalmunition.com /Xcode_OpenBase_pwn.pl
-
exchange.xforce.ibmcloud.com
/vulnerabilities/29624
vdb-entry
- digitalmunition.com /DMA%5B2006-1016a%5D.txt
Sources
- CVE List CVE-2006-5327
- NVD CVE-2006-5327
Fencer Vulns 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.