CVE-2004-0684
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 · uneditedWebSphere Edge Component Caching Proxy in WebSphere Edge Server 5.02, with the JunctionRewrite directive enabled, allows remote attackers to cause a denial of service via an HTTP GET request without any parameters.
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 confidenceDenial of service vulnerability in IBM WebSphere Edge Server 5.02 Caching Proxy component. When the JunctionRewrite directive is enabled, an HTTP GET request without any parameters causes the service to crash.
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= 5.0.2= 5.0.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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 IBM WebSphere Caching Proxy installationLocate the WebSphere Caching Proxy installation directory - typically under the IBM WebSphere Edge Server installation path. Look for caching proxy binaries and configuration directories.Affected if The product IBM WebSphere Caching Proxy Server or Edge Server Caching Proxy is installed on the system.
-
Verify the installed version is 5.0.2Check the version of the installed Caching Proxy component. Use the product's version reporting mechanism or check version information in the installation metadata. Compare your installed version against the affected range: version 5.0.2.Affected if The installed version is exactly 5.0.2.
-
Locate the Caching Proxy configuration fileFind the configuration file that contains JunctionRewrite directive settings. This is typically in the Caching Proxy configuration directory under the WebSphere Edge Server installation.Affected if The Caching Proxy configuration file exists and contains JunctionRewrite settings.
-
Check if JunctionRewrite directive is enabledOpen the Caching Proxy configuration file and search for the JunctionRewrite directive. Determine if it is set to enabled or On. The vulnerability applies when this directive is active.Affected if The JunctionRewrite directive is present and enabled in the Caching Proxy configuration.
-
Test service availabilitySend an HTTP GET request with no parameters to the Caching Proxy service to verify it is still responding. A crash indicates the vulnerability has been triggered.Affected if The service does not respond or crashes when receiving an HTTP GET request without parameters while JunctionRewrite is enabled.
The environment is affected if IBM WebSphere Caching Proxy Server or Edge Server Caching Proxy version 5.0.2 is installed AND the JunctionRewrite directive is enabled in the configuration, as this combination allows the DoS condition to occur.
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 dataDisable the JunctionRewrite directive in the Caching Proxy configuration, or apply the relevant IBM patch for WebSphere Edge Server 5.02.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.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 $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0684 — 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-2004-0684 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