CVE-2012-0410
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 · uneditedDirectory traversal vulnerability in WebAccess in Novell GroupWise before 8.03 allows remote attackers to read arbitrary files via the User.interface 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 confidenceDirectory traversal vulnerability in Novell GroupWise WebAccess allows remote attackers to read arbitrary files on the server by manipulating the User.interface parameter with path traversal sequences (such as ../). The vulnerability exists in versions prior to 8.03 and enables unauthenticated attackers to access sensitive system files.
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<= 8.02= 5.2= 5.5= 5.57e= 6.0= 6.0.1= 6.5= 6.5.2= 6.5.3= 6.5.4= 6.5.6= 6.5.7CVSS 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 if Novell GroupWise WebAccess is runningCheck for the GroupWise WebAccess service or examine HTTP responses on ports typically used by WebAccess (usually port 80/443 or configured ports). Look for the 'WebAccess' banner or path in HTTP responses.Affected if WebAccess is exposed and accessible on the network
-
Check the installed GroupWise versionLocate the GroupWise installation directory and check version information in the product documentation, or query the WebAccess service for its version banner.Affected if The installed version is 8.02 or earlier, or matches any of these: 5.2, 5.5, 5.57e, 6.0, 6.0.1, 6.5, 6.5.2, 6.5.3, 6.5.4, 6.5.6, or 6.5.7
-
Confirm the User.interface parameter is accessibleSend an HTTP GET request to the WebAccess login page and examine the form parameters, specifically looking for a parameter named 'User.interface' in the request.Affected if The User.interface parameter is present and accepts user-supplied input without validation
-
Verify path traversal is possible in the parameterSend a test request with a path traversal sequence (such as ../../../../etc/passwd) in the User.interface parameter and observe if the response contains file contents or error messages revealing traversal.Affected if The parameter reflects file contents or displays path traversal errors, indicating the vulnerability is present
A system is affected if it runs a vulnerable GroupWise version (8.02 or earlier, or any of the listed specific versions) with WebAccess exposed and the User.interface parameter accepts unsanitized path traversal sequences.
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 GroupWise 8.03 or later to obtain the patch for this vulnerability. If immediate patching is not possible, consider restricting access to the WebAccess interface via network-level controls or deploying a web application firewall (WAF) to filter malicious path traversal attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0410 — 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-2012-0410 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