CVE-2012-0690
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 · uneditedTIBCO Spotfire Web Application, Web Player Application, Automation Services Application, and Analytics Client Application in Spotfire Analytics Server before 10.1.2; Server before 3.3.3; and Web Player, Automation Services, and Professional before 4.0.2 allow remote attackers to obtain sensitive information via a crafted URL.
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 · moderate confidenceTIBCO Spotfire components (Web Application, Web Player, Automation Services, Analytics Client) before version 10.1.2/3.3.3/4.0.2 contain an information disclosure vulnerability allowing remote attackers to obtain sensitive information via a crafted URL, likely indicating a path traversal or similar injection flaw.
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= 10.0.0= 10.0.1= 3.0.0= 3.0.1= 3.1.0= 3.1.1= 3.2.0= 3.3.0all versions<= 4.0.1CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Identify installed TIBCO Spotfire componentsCheck your environment for any of the following Spotfire components: Analytics Server, Server, Web Player, Automation Services, Professional client, or Analytics Client. Look in installed programs, application directories, or service listings.Affected if Any of these components are present in the environment.
-
Determine the installed version of TIBCO Spotfire componentsLocate the version information for each installed Spotfire component. Common locations include: the product's About dialog, version files in installation directories, or the administrative console. For Server components, check the administration tool or configuration files.Affected if The installed version is 10.0.0 or 10.0.1 for Analytics Server; 3.0.0, 3.0.1, 3.1.0, 3.1.1, 3.2.0, or 3.3.0 for Spotfire Server; any version for Web Player/Automation Services; or 4.0.1 or earlier for Spotfire Professional.
-
Check if Web Player or Automation Services web interfaces are exposedDetermine whether the Web Player or Automation Services components are accessible over HTTP/HTTPS. Check the server configuration, IIS/Apache settings, or firewall rules to see if these web-facing components are enabled and reachable.Affected if Web Player or Automation Services web interfaces are enabled and accessible from the network.
-
Review web server access logs for suspicious URL patternsExamine HTTP access logs from the Spotfire web server for unusual URL patterns that may indicate path traversal attempts. Look for patterns like ../, ..\, or encoded equivalents in requests to Spotfire endpoints.Affected if The web interfaces are exposed and logs show suspicious crafted URLs containing path traversal sequences.
-
Check for unauthorized access indicatorsReview Spotfire server logs and audit records for successful unauthorized information disclosure attempts, such as access to files outside the intended web root or unexpected sensitive file downloads.Affected if Logs indicate successful unauthorized access to files or information that should not be publicly accessible.
You are affected if any TIBCO Spotfire component is installed with a version matching the affected ranges (Analytics Server 10.0.0-10.0.1, Server 3.0.0-3.3.0, Web Player/Automation Services any version, Professional <=4.0.1) AND the web-facing components are accessible to network users.
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 TIBCO Spotfire Analytics Server to 10.1.2 or later (Server to 3.3.3, Web Player/Automation Services/Professional to 4.0.2) to remediate the vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0690 — 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-2012-0690 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