GroupwiseApplication · Novell

CVE-2011-2663

HIGH · 10.0 CVSS v2.0 Published 2011-10-08
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
Array index error in GroupWise Internet Agent (GWIA) in Novell GroupWise 8.0 before HP3 allows remote attackers to execute arbitrary code via a crafted yearly RRULE variable in a VCALENDAR attachment in an e-mail message.

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

Array index error in GroupWise Internet Agent (GWIA) in Novell GroupWise 8.0 before HP3 allows remote attackers to execute arbitrary code via a crafted yearly RRULE variable in a VCALENDAR attachment in an e-mail message.

MitigationUpgrade to GroupWise 8.0 HP3 or later to patch the array index vulnerability in GWIA that allows remote code execution through malicious VCALENDAR attachments.

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

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 version
    Check the GroupWise client or server version through the installed software properties, version information in the About dialog, or by querying the GroupWise installation directory for version metadata
    Affected if The version is 8.0 without the HP3 patch applied
  2. Confirm GWIA component is installed
    Verify GroupWise Internet Agent (GWIA) is installed on the system by checking the GroupWise installation directory for GWIA executables or checking Windows Services/Unix processes for a GWIA service
    Affected if GWIA is present and running as the vulnerability exists in this component
  3. Determine HP3 patch status
    Check the installed patches or patch level on the GroupWise system - this is typically visible in the GroupWise About information, patch logs, or by querying the patch inventory for HP3
    Affected if The HP3 patch is NOT installed, meaning the array index vulnerability remains unpatched
  4. Verify e-mail processing configuration
    Confirm that the system is configured to accept or process VCALENDAR attachments through GWIA - this is typically the default behavior for Internet Mail services in GroupWise
    Affected if GWIA is configured to handle incoming e-mail with attachments, as the exploit requires a crafted VCALENDAR attachment to be processed

A user is affected if they are running GroupWise 8.0 without the HP3 patch and have GWIA enabled to process incoming e-mail with VCALENDAR attachments.

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

Upgrade to GroupWise 8.0 HP3 or later to patch the array index vulnerability in GWIA that allows remote code execution through malicious VCALENDAR attachments.

Recommended fix High confidence

GroupWise 8.0 HP3 or subsequent release

  1. Obtain and install GroupWise 8.0 HP3 (Hot Patch 3) or later from Novell's support portal
  2. Apply the HP3 patch to all GroupWise servers running the GroupWise Internet Agent (GWIA) component
  3. Verify the patch has been successfully applied by checking the GroupWise version information
  4. Test that the GWIA service is functioning properly after the 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 / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2663 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-2663 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