dbcve.org
Communigate ProApplication · Stalker

CVE-2002-2375

MEDIUM · 5.0 CVSS v2.0 Published 2002-12-31
Fix available
A fix is available. Upgrade to after 4.0b4 or later.
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
Directory traversal vulnerability in CommuniGate Pro 4.0b4 and possibly earlier versions allows remote attackers to list the contents of the WebUser directory and its parent directory via a (1) .. (dot dot) or (2) . (dot) in a URL. NOTE: it is not clear whether this issue reveals any more information regarding directory structure than is already available to any CommuniGate Pro user, although there is a possibility that it could be used to infer product version information.

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 confidence

Directory traversal vulnerability in CommuniGate Pro 4.0b4 allows remote attackers to list contents of the WebUser directory and its parent directory by using '..' or '.' path traversal sequences in URLs. This could expose directory structure information and potentially reveal product version details.

MitigationImplement input validation to filter or sanitize path traversal characters ('..' and '.') from URL requests before processing. Apply security updates if available from CommuniGate.

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
Communigate ProApplication
Affected:<= 4.0b4

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. Identify if CommuniGate Pro is installed
    Check for CommuniGate Pro processes or services running on the system. On Windows, look for 'CommuniGate Pro' in Services. On Unix/Linux, run 'ps aux | grep -i communigate' or check for the installation directory (commonly /var/CommuniGate or /opt/CommuniGate).
    Affected if CommuniGate Pro process or service is found running on the system
  2. Determine the installed version
    Check the CommuniGate Pro version. Common locations: the About page at the web interface (typically port 80 or 8100), the application banner on startup, or check the version file in the installation directory (often named 'VERSION' or 'ReleaseNotes' in the main folder). Compare the version number to '4.0b4' - any version 4.0b4 or lower is affected.
    Affected if The installed version is 4.0b4 or any earlier version (versions below 4.0b4)
  3. Verify the web server component is accessible
    Check if the CommuniGate Pro web interface is enabled and reachable. Attempt to access the server on common HTTP ports (80, 8080, 8000, or the default admin port 8100). Try accessing the root URL (e.g., http://yourserver:port/) to confirm the web server responds.
    Affected if The CommuniGate Pro web server responds to HTTP requests and is accessible over the network
  4. Test for path traversal vulnerability
    Send an HTTP request to the web server using path traversal sequences. Try accessing: 1) http://yourserver:port/../ (with '..'), 2) http://yourserver:port/./ (with '.'), or 3) http://yourserver:port/..%2F (URL-encoded). Check if the response reveals directory listings or shows parent directory contents instead of being rejected or redirected.
    Affected if The server returns directory listings, shows parent directory contents, or fails to properly sanitize path traversal characters in the URL

A system is affected if CommuniGate Pro version 4.0b4 or earlier is installed and running with its web interface accessible, and the server permits path traversal sequences ('..' or '.') in URLs to expose directory contents.

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
Upgrade available Upgrade to a release after 4.0b4
Interim mitigation

Implement input validation to filter or sanitize path traversal characters ('..' and '.') from URL requests before processing. Apply security updates if available from CommuniGate.

Fix this in Communigate Pro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2375 — 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-2002-2375 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