CVE Tools

CVE-2006-5328

No known exploitation. EPSS puts it in the 27th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Apple XcodeAffected: ≤ 2.2Upgrade to: after 2.2Stated by: NVD
  • Openbase International Ltd OpenbaseAffected: ≤ 10.0Upgrade to: after 10.0Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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 create arbitrary files via a symlink attack on the simulation.sql file.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS27th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 27th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 7128 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified

Affected products

And 1 more affected product. See all after sign-in

Technical detail

AV:L/AC:L/Au:N/C:C/I:C/A:C

Scored 7.2 by NVD.

How it is reached

  • Access Vector LocalRequires local access
  • Access Complexity LowNo special conditions required
  • Authentication NoneNo authentication required

Impact if exploited

  • Confidentiality CompleteAll information is disclosed
  • Integrity CompleteAll data can be modified
  • Availability CompleteTotal shutdown of the affected resource

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Xcode, not every advisory.