CVE-2000-0189
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 · uneditedColdFusion Server 4.x allows remote attackers to determine the real pathname of the server via an HTTP request to the application.cfm or onrequestend.cfm files.
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 confidenceColdFusion Server 4.x contains a path disclosure vulnerability where HTTP requests to application.cfm or onrequestend.cfm files return the server's real filesystem pathname in server responses, allowing remote attackers to gather intelligence about the server's internal structure.
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= 4.0= 4.0.1= 4.5CVSS 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 ColdFusion installation and versionCheck the ColdFusion server for installed version by reviewing server documentation, startup scripts, or the cfusion/lib/cfc.jar manifest. Also check the Windows registry (HKLM\SOFTWARE\Allaire\ColdFusion\CurrentVersion) or Unix config files for the version string.Affected if The installed version matches 4.0, 4.0.1, or 4.5 exactly.
-
Locate the web root directoryIdentify the web document root or the directory from which ColdFusion serves web content. This is typically configured in the ColdFusion Administrator or the web server configuration.Affected if A web-accessible directory is configured as the document root.
-
Test application.cfm for path disclosureSend an HTTP GET request to /application.cfm (or any path where application.cfm might exist) using a tool like curl: curl -v http://target/application.cfm. Examine the response headers and body for any filesystem path strings.Affected if The response contains an absolute filesystem path (e.g., C:\inetpub\wwwroot\ or /var/www/html/) rather than a relative or generic error.
-
Test onrequestend.cfm for path disclosureSend an HTTP GET request to /onrequestend.cfm using curl or a browser: curl -v http://target/onrequestend.cfm. Inspect the response for exposed filesystem paths.Affected if The response includes the full server filesystem path in any error message or output.
If ColdFusion Server version 4.0, 4.0.1, or 4.5 is installed AND either application.cfm or onrequestend.cfm returns an absolute filesystem path in the HTTP response, the server is affected by this path disclosure vulnerability.
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 from the deprecated ColdFusion 4.x to a supported ColdFusion version, or implement web server access controls to restrict or block access to these specific .cfm endpoint files.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0189 — 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-2000-0189 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