CVE-2012-0687
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 ActiveMatrix Runtime Platform in Service Grid and Service Bus 2.x before 2.3.2 and BusinessWorks Service Engine before 5.8.2; TIBCO ActiveMatrix Platform in TIBCO Silver Fabric ActiveMatrix Service Grid Distribution 3.1.3, Service Grid and Service Bus 3.x before 3.1.5, BusinessWorks Service Engine 5.9.x before 5.9.3, and BPM before 1.3.0; TIBCO BusinessEvents Runtime in Enterprise and Inference Editions 3.x before 3.0.3, Standard Edition 4.x before 4.0.2, and Standard Edition and Express 5.0.0; and TIBCO BusinessWorks Engine in TIBCO Silver Fabric ActiveMatrix BusinessWorks Distribution 5.9.2 and ActiveMatrix BusinessWorks before 5.9.3 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 · high confidenceInformation disclosure vulnerability in multiple TIBCO enterprise middleware products (ActiveMatrix Runtime Platform, BusinessEvents Runtime, BusinessWorks Engine) allowing remote attackers to obtain sensitive information via a crafted URL. The vulnerability stems from improper input validation in the web layer handling of URLs.
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.0.0= 2.0.1= 2.0.2= 2.1.0= 2.2.0= 2.2.1= 2.3.0= 2.3.1= 3.0.0= 3.0.1= 2.0.0= 2.0.1= 2.1.0= 2.2.0= 2.2.1= 2.3.0= 2.3.1= 2.3.2= 3.0.0= 3.0.1= 3.1.0= 3.1.2<= 5.8.1= 5.6.0= 5.6.3= 5.6.4= 5.7= 5.7.1= 5.7.2= 5.8= 5.9.0= 5.9.1= 5.9.2= 3.1.3= 5.9.2<= 1.2.0= 1.0.1= 1.0.2= 1.1.0= 1.1.1= 3.0= 3.0.1= 3.0.2= 4.0= 4.0.1= 5.0<= 5.9.2CVSS 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 running TIBCO processesUse system commands (tasklist on Windows, ps on Linux) to list running processes and look for TIBCO-related processes such as tibco, Activematrix, BusinessWorks, BusinessEvents, or related service names.Affected if Any TIBCO middleware processes are running on the system
-
Locate TIBCO installation directoryCheck common installation paths such as C:\TIBCO (Windows) or /opt/tibco, /usr/local/tibco (Linux). Look for product-specific subdirectories like tibco/AMX, tibco/bw, tibco/be, tibco/bpm.Affected if TIBCO software is installed in the environment
-
Determine exact product versionExamine version files or startup scripts within the TIBCO installation directory. Common locations include version.info files, README files, or product-specific lib directories. Look for version strings in manifest files (.mf) or product configuration XML files.Affected if The installed version matches any version listed in the affected products and versions for CVE-2012-0687
-
Check if web interface is accessibleAttempt to access the web-based admin console or web services endpoint for the TIBCO product. Default ports include 8080, 8443, 9000, or product-specific ports. Use a browser or curl to send a request to the web layer.Affected if The web management console or web services are exposed and reachable on the network
-
Inspect web layer configurationReview TIBCO configuration files related to web access, such as tra files (TIBCO Runtime Agent), domain configurations, or HTTP transport settings. Look for URL validation settings or web security configurations in the product-specific config directories.Affected if The web layer is configured and enabled for the affected product
A system is affected if it runs any of the listed TIBCO products (Activematrix Service Bus, Service Grid, BusinessWorks, BusinessEvents, BPM) in the specific versions specified in the affected products list and has the web interface accessible.
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 dataApply vendor-supplied patches to upgrade to the fixed versions (Service Grid/Service Bus 2.3.2+, BusinessWorks Service Engine 5.8.2+, BusinessEvents 3.0.3+/4.0.2+, BPM 1.3.0+, BusinessWorks 5.9.3+). Implement URL filtering or WAF rules to block suspicious crafted URL patterns as an interim control.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0687 — 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-0687 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