CVE-2009-1634
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 WebAccess component in Novell GroupWise 7.x before 7.03 HP3 and 8.x before 8.0 HP2 does not properly implement session management mechanisms, which allows remote attackers to gain access to user accounts via unspecified vectors.
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 confidenceThe WebAccess component in Novell GroupWise 7.x before 7.03 HP3 and 8.x before 8.0 HP2 contains a session management flaw that allows remote attackers to bypass authentication and gain unauthorized access to user accounts through unspecified attack vectors.
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= 7.0= 7.0.0= 7.0.2= 7.0.3= 7.03= 8.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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Verify GroupWise WebAccess component is presentCheck if the WebAccess component is installed on the GroupWise server. This is typically accessible via HTTP/HTTPS on ports 80/443 or a configured web server port.Affected if WebAccess component is installed and exposed on the network
-
Identify the installed GroupWise versionCheck the GroupWise version number. In the GroupWise admin interface, navigate to the system information or version details. Alternatively, check the GroupWise binaries or installation directory for version information.Affected if The version number matches 7.0, 7.0.0, 7.0.2, 7.0.3, 7.03, or 8.0, or falls within 7.x before 7.03 HP3 or 8.x before 8.0 HP2
-
Confirm the WebAccess service is accessibleVerify that the WebAccess web interface is exposed and reachable. Attempt to access the WebAccess login page via the configured URL.Affected if WebAccess is accessible over the network and accepts authentication requests
-
Check if the hot pack patch has been appliedReview the installed hot pack patches. In GroupWise admin, check the patch level or version details for HP3 on v7.x or HP2 on v8.x.Affected if The hot pack patch 7.03 HP3 (for v7.x) or 8.0 HP2 (for v8.x) is NOT installed
A user is affected if they are running GroupWise 7.x before 7.03 HP3 or 8.x before 8.0 HP2 with the WebAccess component enabled and accessible on the network.
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 the appropriate hot pack patch (7.03 HP3 for v7.x or 8.0 HP2 for v8.x) to the GroupWise WebAccess component. If patching is not immediately feasible, restrict network access to the WebAccess interface using network segmentation or firewall rules.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1634 — 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-2009-1634 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