CVE-2004-2478
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 · uneditedUnspecified vulnerability in Jetty HTTP Server, as used in (1) IBM Trading Partner Interchange before 4.2.4, (2) CA Unicenter Web Services Distributed Management (WSDM) before 3.11, and possibly other products, allows remote attackers to read arbitrary files via a .. (dot dot) in the URL.
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 confidenceJetty HTTP Server contains an unspecified path traversal vulnerability allowing remote attackers to read arbitrary files via '..' (dot dot) sequences in the URL. This affects IBM Trading Partner Interchange before 4.2.4 and CA Unicenter WSDM before 3.11.
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<= 3.1<= 4.2.2= 4.2.1= 3.1.6= 3.1.7= 4.1.0= 4.1.0_rc4= 4.1.1= 4.2.4= 4.2.5= 4.2.6= 4.2.7= 4.2.9= 4.2.11= 4.2.12CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 if Jetty HTTP Server is installedLocate the Jetty installation directory and check the version information, typically found in a version manifest, README, or startup bannerAffected if The installed Jetty version matches one of these: 3.1.6, 3.1.7, 4.1.0, 4.1.0_rc4, 4.1.1, 4.2.4, 4.2.5, 4.2.6, 4.2.7, 4.2.9, 4.2.11, or 4.2.12
-
Identify if IBM Trading Partner Interchange is installedLocate the IBM Trading Partner Interchange installation and check the product versionAffected if The installed version is 4.2.1 or is 4.2.2 or lower (any version <= 4.2.2)
-
Identify if CA Unicenter WSDM is installedLocate the CA Unicenter Web Services Distributed Management installation and check the product versionAffected if The installed version is 3.1 or lower (<= 3.1)
-
Determine if the HTTP server component is exposedCheck if the Jetty HTTP server is listening on a network port (typically 80, 443, 8080, 8443) and accessible from network locationsAffected if The HTTP server is network-accessible and serving HTTP requests
You are affected if you are running any of the specific Jetty versions listed (3.1.6 through 4.2.12), IBM Trading Partner Interchange <= 4.2.2, or CA Unicenter WSDM <= 3.1, and the HTTP server component is exposed on the network.
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 Jetty to a patched version or implement strict path validation and canonicalization to prevent directory traversal attacks. Restrict file system access permissions to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2478 — 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-2478 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