dbcve.org
GroupwiseApplication · Novell

CVE-2014-0610

HIGH · 10.0 CVSS v2.0 Published 2014-09-05
Fix available
A fix is available. Upgrade to after 8.03 or later.
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 before 8.0.3 HP4, 2012 before SP3, and 2014 before SP1 on Windows allows remote attackers to execute arbitrary code or cause a denial of service (invalid 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 · moderate confidence

The Novell GroupWise client for Windows contains a vulnerability allowing remote attackers to execute arbitrary code or cause a denial of service via invalid pointer dereference. The vulnerability affects versions before 8.0.3 HP4, 2012 before SP3, and 2014 before SP1.

MitigationUpgrade GroupWise client to version 8.0.3 HP4, 2012 SP3, or 2014 SP1 or later. Apply network segmentation and restrict client exposure to untrusted networks to reduce attack surface until patches are applied.

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.03= 8.0= 8.00= 8.01= 8.02= 8.03= 2012= 2014

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. Locate GroupWise client installation
    Check for GroupWise client installation in typical Windows paths: C:\Program Files\Novell\GroupWise\ or C:\Program Files (x86)\Novell\GroupWise\. Also check Add/Remove Programs for Novell GroupWise entry.
    Affected if GroupWise client is not found in expected installation paths or Add/Remove Programs.
  2. Identify installed GroupWise version
    Right-click on gwclient.exe in the GroupWise installation directory, select Properties, then go to the Details tab to view the File Version. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\Client for the Version value.
    Affected if Unable to locate gwclient.exe or no version information found.
  3. Compare version against affected ranges
    Compare the identified version number to the vulnerable ranges: versions 8.0.x before 8.0.3 HP4, version 2012 before SP3, and version 2014 before SP1. Note that version 8.03 equals 8.0.3.
    Affected if Installed version is 8.0, 8.00, 8.01, 8.02, 8.03 (or any 8.0.x below HP4), 2012 (without SP3), or 2014 (without SP1).
  4. Confirm client component is present
    Verify that the gwclient.exe executable exists in the installation directory. This is the client component where the vulnerability resides. The vulnerability affects the client, not the GroupWise server.
    Affected if Only server components are found and no gwclient.exe exists - the client is not installed.

A user is affected if the GroupWise Windows client is installed and the version matches 8.0.x through 8.0.3, 2012 prior to SP3, or 2014 prior to SP1 based on the version metadata of gwclient.exe.

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
Upgrade available Upgrade to a release after 8.03
Interim mitigation

Upgrade GroupWise client to version 8.0.3 HP4, 2012 SP3, or 2014 SP1 or later. Apply network segmentation and restrict client exposure to untrusted networks to reduce attack surface until patches are applied.

Recommended fix High confidence

GroupWise 8.0.3 HP4 (or 2012 SP3 or 2014 SP1 depending on your branch)

  1. 1. Identify the current GroupWise client version installed on Windows systems
  2. 2. For GroupWise 8.x users: Upgrade to GroupWise 8.0.3 HP4 or later
  3. 3. For GroupWise 2012 users: Upgrade to GroupWise 2012 SP3 or later
  4. 4. For GroupWise 2014 users: Upgrade to GroupWise 2014 SP1 or later
  5. 5. Verify the upgrade was successful by checking the new client version in About or Help section
  6. 6. Test critical GroupWise client functionality after upgrade to ensure normal operation
Caveat Review GroupWise release notes for any changes in functionality between your current version and the target upgrade version; test in non-production environment first if possible

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

Fix this in Groupwise Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0610 — 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-2014-0610 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