dbcve.org
RtworksApplication · Tibco

CVE-2007-5655

HIGH · 10.0 CVSS v2.0 Published 2008-01-16
Fix available
A fix is available. Upgrade to after 6.8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
TIBCO SmartSockets RTserver 6.8.0 and earlier, RTworks before 4.0.4, and Enterprise Message Service (EMS) 4.0.0 through 4.4.1 allows remote attackers to execute arbitrary code via crafted requests containing values that are used as pointers.

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 confidence

Memory corruption vulnerability in TIBCO SmartSockets RTserver, RTworks, and Enterprise Message Service where crafted network requests containing user-controlled values are used directly as memory pointers, leading to arbitrary code execution by remote attackers.

MitigationUpgrade to RTserver 6.8.1+, RTworks 4.0.4+, or EMS 4.4.2+. If immediate patching is not feasible, restrict network access to these services and implement input validation at network perimeter controls.

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
RtworksApplication
Affected:<= 4.0.3
Smartsockets RtserverApplication
Affected:<= 6.8.0
Enterprise Message ServiceApplication
Affected:all versions

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TIBCO Rtworks version
    Locate the Rtworks installation directory and check the version file (typically in the installation root or version.info). Use command: find / -name '*rtworks*' -type d 2>/dev/null or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\TIBCO if on Windows.
    Affected if The installed version is 4.0.3 or lower.
  2. Identify installed TIBCO SmartSockets RTserver version
    Locate the SmartSockets/RTserver installation and locate the version file (often version.txt, about.txt, or embedded in executable metadata). Search using: find / -name '*rtserver*' -o -name '*smartsockets*' 2>/dev/null.
    Affected if The installed version is 6.8.0 or lower.
  3. Identify installed TIBCO Enterprise Message Service version
    Locate the EMS installation directory and check the version (typically in version.info or the ems/bin/tibcoems executable version info). Search using: find / -name '*ems*' -type d 2>/dev/null.
    Affected if Any version of EMS is found, since all versions are affected.
  4. Verify if affected TIBCO network services are running
    Check running processes for rtworks, rtserver, or tibcoems daemons. Use commands: ps aux | grep -i 'rtworks\|rtserver\|ems' on Unix or tasklist on Windows. Also check for open listening ports commonly used by these services (typically ports 5000-6000 range for RTserver/RTworks, port 7222 for EMS).
    Affected if Any of these services are running and accessible on the network.

Your environment is affected if any TIBCO Rtworks version 4.0.3 or lower, RTserver version 6.8.0 or lower, or any version of EMS is installed and running with network exposure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.8.0
Interim mitigation

Upgrade to RTserver 6.8.1+, RTworks 4.0.4+, or EMS 4.4.2+. If immediate patching is not feasible, restrict network access to these services and implement input validation at network perimeter controls.

Recommended fix Moderate confidence

RTworks: upgrade to 4.0.4 or later; Smartsockets RTserver: contact TIBCO for patched version; EMS: contact TIBCO for patched version

  1. 1. Identify the specific TIBCO product in use (RTworks, Smartsockets RTserver, or Enterprise Message Service)
  2. 2. For RTworks: upgrade to version 4.0.4 or later as this version contains the security fix
  3. 3. For Smartsockets RTserver: contact TIBCO support to confirm the specific patched version for version 6.8.0
  4. 4. For Enterprise Message Service (EMS): contact TIBCO support to confirm the patched version since the vulnerable range was 4.0.0-4.4.1
  5. 5. After upgrading, verify the running version matches the fixed release
  6. 6. Test mission-critical workflows to ensure the upgrade does not introduce regressions
Caveat Check TIBCO release notes for any compatibility changes or deprecated features between your current version and the upgrade target

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rtworks Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-5655 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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