CVE-1999-1006
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 · uneditedGroupwise web server GWWEB.EXE allows remote attackers to determine the real path of the web server via the HELP 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 · moderate confidenceNovell GroupWise web server (GWWEB.EXE) contains an information disclosure vulnerability where the HELP parameter reveals the server's installation filesystem path. This path disclosure aids attackers in reconnaissance by exposing system directory structures.
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.2= 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
- 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 GroupWise web server is installedCheck for the presence of GWWEB.EXE or search for GroupWise installation directories on the system. Common paths include C:\Novell\GroupWise or /opt/novell/groupwise.Affected if GWWEB.EXE exists on the system and is running as a web server
-
Identify installed GroupWise versionCheck the version of the GroupWise installation, typically found in the program files, release notes, or via the web server's banner. Look for version 5.2 or 5.5 specifically.Affected if The installed version is 5.2 or 5.5
-
Test HELP parameter for path disclosureSend an HTTP request to the GroupWise web server with the HELP parameter, such as: http://servername/gwweb.exe?HELP=1 or similar HELP endpoint. Inspect the response for filesystem path information.Affected if The response contains full filesystem paths indicating the GroupWise installation directory
-
Examine web server response headers and error messagesInteract with various endpoints on the GWWEB.EXE web server and observe any error messages, help pages, or diagnostic output for path disclosure.Affected if Path information is revealed in any server response
The system is affected if GroupWise version 5.2 or 5.5 is installed and the HELP parameter exposes the server's installation filesystem path in its 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 dataApply appropriate GroupWise patches from Novell/Micro Focus, or configure the web server to restrict path disclosure via the HELP parameter.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1006 — 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-1999-1006 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