RendezvousApplication · Tibco

CVE-2007-4159

MEDIUM · 5.0 CVSS v2.0 Published 2007-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
index.html in the HTTP administration interface in certain daemons in TIBCO Rendezvous (RV) 7.5.2 allows remote attackers to obtain sensitive information, such as a user name and IP addresses, via a direct request.

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

The HTTP administration interface in TIBCO Rendezvous 7.5.2 exposes the index.html file to unauthenticated remote attackers, allowing disclosure of sensitive information including usernames and IP addresses.

MitigationRestrict network access to or disable the HTTP administration interface if not required; otherwise, ensure strong authentication is enforced for the admin interface.

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
RendezvousApplication
Affected:= 7.5.2

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
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 checks

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

  1. Locate TIBCO Rendezvous installation
    Search for the TIBCO Rendezvous installation directory on the system. On Windows, common paths are C:\tibco\rv\ or C:\Program Files\tibco\rv\. On Unix-like systems, check /opt/tibco/rv/ or /usr/local/tibco/rv/. Look for executable files such as tibrv.exe, rvd, or rv daemon files.
    Affected if TIBCO Rendezvous software is present on the system
  2. Confirm installed version is 7.5.2
    Determine the exact version of the installed TIBCO Rendezvous. On Windows, right-click the tibrv.exe file and select Properties > Details to view the version number. On Unix systems, run the command 'rvd -version' or 'tibrv-version' from the installation bin directory, or examine a version file in the installation directory.
    Affected if The installed version is exactly 7.5.2
  3. Check if HTTP administration interface is enabled
    Examine the TIBCO Rendezvous configuration files for HTTP administration settings. Look for files named rv.conf, tibrv.conf, or similar configuration files in the installation directory or conf subdirectory. Search for keywords such as 'http', 'admin', 'port', or '8080' to identify if an HTTP admin interface is configured and enabled.
    Affected if The HTTP administration interface is configured and enabled in the Rendezvous configuration
  4. Verify unauthenticated access to index.html
    Using a web browser or curl command, attempt to access the HTTP administration interface without providing any credentials. The default HTTP admin port is typically 7580. Try accessing http://localhost:7580/index.html or http://<hostname>:7580/index.html. If the page loads and displays sensitive information such as usernames or IP addresses without prompting for authentication, the system is vulnerable.
    Affected if The index.html file of the HTTP admin interface is accessible without requiring authentication

The system is affected if TIBCO Rendezvous version 7.5.2 is installed AND the HTTP administration interface is enabled AND the index.html file is accessible without authentication credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to or disable the HTTP administration interface if not required; otherwise, ensure strong authentication is enforced for the admin interface.

Fix this in Rendezvous Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4159 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4159 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