CVE-2004-2104
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 · uneditedNovell NetWare Enterprise Web Server 5.1 and 6.0 allows remote attackers to obtain sensitive server information, including the internal IP address, via a direct request to (1) snoop.jsp, (2) SnoopServlet, (3) env.bas, or (4) lcgitest.nlm.
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 confidenceNovell NetWare Enterprise Web Server versions 5.1 and 6.0 contain multiple JSP servlets and CGI files (snoop.jsp, SnoopServlet, env.bas, lcgitest.nlm) that leak sensitive server configuration information including internal IP addresses when accessed directly. This is an information disclosure vulnerability exploitable remotely without authentication.
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.
-
Identify NetWare Web Server versionCheck the installed version of Novell NetWare Enterprise Web Server using system information tools or NetWare administrator utilities. Look for version 5.1 or 6.0 specifically.Affected if The installed version is Novell NetWare Enterprise Web Server 5.1 or 6.0
-
Locate vulnerable JSP and servlet filesSearch the web server document root or servlet container directories for the files snoop.jsp and SnoopServlet. These are typically found in JSP or servlet application directories.Affected if The files snoop.jsp or SnoopServlet exist on the server and are accessible via HTTP
-
Locate vulnerable CGI filesSearch the web server CGI-bin directories for the files env.bas and lcgitest.nlm.Affected if The files env.bas or lcgitest.nlm exist on the server and are accessible via HTTP
-
Test endpoint accessibilityAttempt to access the potential vulnerable URLs: /snoop.jsp, /servlet/SnoopServlet, /cgi-bin/env.bas, /cgi-bin/lcgitest.nlm via HTTP from a remote client.Affected if Any of these endpoints return server configuration information or internal IP addresses without authentication
A system is affected if it is running Novell NetWare Enterprise Web Server version 5.1 or 6.0 and has any of the vulnerable files (snoop.jsp, SnoopServlet, env.bas, lcgitest.nlm) accessible via the web server without authentication.
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 dataRemove or disable access to the vulnerable files (snoop.jsp, SnoopServlet, env.bas, lcgitest.nlm) from the web server, or restrict access to these endpoints via web server configuration filters.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2104 — 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-2104 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