CVE-2002-0341
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 · uneditedGWWEB.EXE in GroupWise Web Access 5.5, and possibly other versions, allows remote attackers to determine the full pathname of the web server via an HTTP request with an invalid HTMLVER 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 confidenceGWWEB.EXE in GroupWise Web Access 5.5 and possibly other versions contains an information disclosure vulnerability where sending an HTTP request with an invalid HTMLVER parameter causes the application to return the full filesystem path of the web server, revealing sensitive server configuration information to remote attackers.
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.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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 GroupWise Web Access installationLocate GWWEB.EXE on the web server. Check common web server directories (such as /usr/novell/groupwise/webaccess or C:\Novell\GroupWise\WebAccess) or use file search tools to find GWWEB.EXE.Affected if GWWEB.EXE is found and running as part of the web server application.
-
Identify GroupWise Web Access versionCheck the version metadata of GWWEB.EXE or examine the GroupWise Web Access release documentation. Compare the installed version against the affected version 5.5.Affected if The installed version is GroupWise Web Access 5.5.
-
Verify web service is accessibleConfirm the web server hosting GroupWise Web Access is running and accessible via HTTP/HTTPS on the expected port (typically port 80 or 443).Affected if The GroupWise Web Access web interface is reachable over the network.
-
Test HTMLVER parameter for path disclosureSend an HTTP GET request to the GWWEB.EXE endpoint with an invalid or malformed HTMLVER parameter (for example: GET /gw/webacc?HTMLVER=INVALID HTTP/1.1). Observe the response for any filesystem path disclosure.Affected if The HTTP response contains full filesystem path information such as drive letters and directory structures.
A user is affected if GroupWise Web Access version 5.5 is installed and accessible, and sending a request with an invalid HTMLVER parameter reveals the server's filesystem path in the response.
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 to a patched version of GroupWise Web Access or implement proper input validation on the HTMLVER parameter to prevent path disclosure in error responses. Consider configuring the web server to return generic error messages rather than detailed diagnostic information.
- 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-2002-0341 — 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-2002-0341 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