dbcve.org
GroupwiseApplication · Novell

CVE-2013-0804

HIGH · 10.0 CVSS v2.0 Published 2013-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The client in Novell GroupWise 8.0 before 8.0.3 HP2 and 2012 before SP1 HP1 allows remote attackers to execute arbitrary code or cause a denial of service (incorrect pointer dereference) 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 · high confidence

The Novell GroupWise client versions 8.0 before 8.0.3 HP2 and 2012 before SP1 HP1 contain an incorrect pointer dereference vulnerability that allows remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors.

MitigationUpdate GroupWise client to version 8.0.3 HP2 or 2012 SP1 HP1 or later. If immediate patching is not feasible, restrict network access to untrusted sources and implement application whitelisting as a compensating control.

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
GroupwiseApplication
Affected:= 8.0= 8.00= 8.01= 8.02= 8.03= 2012

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GroupWise client version
    Locate the GroupWise client installation and retrieve its version information (typically available in the application's About dialog, installation directory metadata, or system registry)
    Affected if The displayed version matches any of the following: 8.0, 8.00, 8.01, 8.02, 8.03, or 2012 (without the required patches)
  2. Confirm version is within affected 8.0.x range
    If the version begins with 8.0, verify whether it is earlier than 8.0.3 HP2 by comparing the full version string
    Affected if The version is 8.0.x where x is less than 3, or the version shows 8.0.3 without the HP2 patch identifier
  3. Confirm version is within affected 2012 range
    If the version shows 2012, verify whether it is earlier than SP1 HP1 by checking the update/patch level
    Affected if The version shows 2012 without SP1, or shows 2012 SP1 without the HP1 patch identifier
  4. Verify vulnerability trigger conditions
    This vulnerability is triggered through unspecified vectors during client processing of remote data. Confirm whether the GroupWise client is configured to handle external or remote content sources
    Affected if The client processes remote or external data without additional validation layers, as this is the attack vector for the pointer dereference flaw

A user is affected if their installed GroupWise client version is 8.0.x before 8.0.3 HP2, or 2012 before SP1 HP1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update GroupWise client to version 8.0.3 HP2 or 2012 SP1 HP1 or later. If immediate patching is not feasible, restrict network access to untrusted sources and implement application whitelisting as a compensating control.

Recommended fix High confidence

GroupWise 8.0.3 HP2 or later (for 8.0 branch); GroupWise 2012 SP1 HP1 or later (for 2012 branch)

  1. Identify the current GroupWise version (8.0, 8.00, 8.01, or 8.02)
  2. For GroupWise 8.0x versions: Upgrade to GroupWise 8.0.3 HP2 or later
  3. For GroupWise 2012: Upgrade to GroupWise 2012 SP1 HP1 or later
  4. Obtain the hot patch from Novell's official support portal (support.novell.com)
  5. Follow Novell's installation documentation to apply the upgrade
  6. Verify the installed version matches the fixed release after patching
Caveat Ensure server/client compatibility after upgrade; review Novell release notes for any known issues with the hot patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Groupwise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0804 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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