CVE-2006-5328
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenBase SQL 10.0 and earlier, as used in Apple Xcode 2.2 2.2 and earlier and possibly other products, allows local users to create arbitrary files via a symlink attack on the simulation.sql file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a local symlink vulnerability in OpenBase SQL 10.0 and earlier (used in Apple Xcode 2.2 and earlier). Local users can exploit insufficient validation of file paths when creating the simulation.sql file, allowing symlink attacks that create or overwrite arbitrary files on the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.2<= 10.0= 7.0.15= 8.0.4= 9.1.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenBase SQL versionLocate the OpenBase SQL installation and run 'openbase -v' or check the application bundle version info. Common paths include /usr/local/openbase or /Applications/OpenBase SQL.appAffected if Version is 10.0 or earlier, or specifically 7.0.15, 8.0.4, or 9.1.5
-
Check Apple Xcode versionRun 'xcodebuild -version' in Terminal, or check /Developer/Applications/Xcode.app/Contents/Info.plist for CFBundleShortVersionStringAffected if Version is 2.2 or earlier
-
Identify simulation.sql file creation behaviorSearch for any scripts, tools, or processes that create a file named simulation.sql. Check for OpenBase-related tools in /usr/local/openbase/bin or within Xcode's OpenBase integration componentsAffected if The software creates simulation.sql in a user-writable directory without proper path validation
-
Verify directory permissionsCheck write permissions on directories where simulation.sql might be created (commonly /tmp, /var/tmp, or application working directories). Run 'ls -la' on these directories and verify if unprivileged local users can create symlinksAffected if Local users have write access to directories where the simulation.sql file is created, allowing symlink manipulation
-
Check for existing symlink exploitsSearch for any simulation.sql files that are symlinks: 'find / -name simulation.sql -type l -ls 2>/dev/null' and inspect target files for unauthorized modificationsAffected if simulation.sql exists as a symlink pointing to an unintended file, indicating exploitation has occurred
A system is affected if OpenBase SQL 10.0 or earlier (or specifically versions 7.0.15, 8.0.4, 9.1.5) or Apple Xcode 2.2 or earlier is installed and local users can manipulate symlinks in directories where simulation.sql gets created.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to patched versions of OpenBase SQL and Xcode. If patching is not possible, remove the vulnerable software or restrict local user access to prevent symlink manipulation of the simulation.sql file path.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-5328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data