CVE-2004-2105
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 · uneditedThe webacc servlet in Novell NetWare Enterprise Web Server 5.1 and 6.0 allows remote attackers to read arbitrary .htt files via a full pathname in the error parameter.
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 confidenceThe webacc servlet in Novell NetWare Enterprise Web Server 5.1 and 6.0 contains a path traversal vulnerability allowing remote attackers to read arbitrary .htt files by supplying a full pathname in the error parameter. This is a file disclosure issue resulting from insufficient input validation.
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.1= 6.0CVSS 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.
-
Confirm NetWare Enterprise Web Server versionCheck system information or server documentation for the exact NetWare version (5.1 or 6.0) and verify Enterprise Web Server component is installed. Look in system inventory, NWCONFIG, or iManager for installed products.Affected if Version is NetWare 5.1 or 6.0 with Enterprise Web Server component present
-
Identify if webacc servlet is enabledCheck the servlet container configuration (typically in servlet.ini, servlet.xml, or through iManager) for the webacc servlet mapping. Look for servlet definition with name 'webacc' or path pattern '/servlet/webacc'.Affected if webacc servlet is registered and enabled in the servlet container configuration
-
Verify .htt file handling is enabledCheck if .htt file extension handlers are configured in the Enterprise Web Server configuration (httpd.cfg, .htaccess, or through consoleone/iManager). Look for HTT extension mapping to a handler.Affected if The server is configured to process .htt files through the webacc servlet or similar handler
-
Test path traversal via error parameterIf webacc is accessible, attempt a controlled request with error parameter pointing to a known .htt file path (e.g., /servlet/webacc?error=/path/to/sample.htt). Compare response against expected content or check for path traversal in server logs.Affected if The error parameter accepts and processes full filesystem paths to .htt files without proper sanitization
A system is affected if it runs Novell NetWare Enterprise Web Server version 5.1 or 6.0 with the webacc servlet enabled and .htt file handling configured, allowing path traversal through the error parameter to read arbitrary .htt files.
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 dataApply vendor patches if available; otherwise restrict or disable the webacc servlet, implement URL filtering at the network perimeter, or upgrade from legacy NetWare systems.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2105 — 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-2105 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