dbcve.org
GroupwiseApplication · Novell

CVE-2011-0333

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
Heap-based buffer overflow in the NgwiCalVTimeZoneBody::ParseSelf function in gwwww1.dll in GroupWise Internet Agent (GWIA) in Novell GroupWise 8.0 before HP3 allows remote attackers to execute arbitrary code via a crafted TZNAME variable in a VCALENDAR attachment in an e-mail message, related to an "integer truncation error."

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

A heap-based buffer overflow vulnerability exists in the NgwiCalVTimeZoneBody::ParseSelf function within gwwww1.dll of the GroupWise Internet Agent (GWIA). The vulnerability is caused by an integer truncation error when parsing a crafted TZNAME variable in a VCALENDAR attachment within an email message. Successful exploitation allows remote attackers to execute arbitrary code on the affected system.

MitigationApply the HP3 patch for Novell GroupWise 8.0 or upgrade to a supported version. Consider implementing email filtering at the gateway to block or sanitize VCALENDAR attachments from untrusted sources until the patch can be 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.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. Verify GroupWise Internet Agent (GWIA) installation
    Check for the presence of gwwww1.dll in the GroupWise installation directory, typically found in the GWIA subfolder (e.g., C:\Program Files\Novell\GroupWise\gwia\ or /opt/novell/groupwise/gwia/). Use command: dir /s gwwww1.dll on Windows or find / -name gwwww1.dll on Linux.
    Affected if gwwww1.dll exists and the GWIA service is installed on the system
  2. Confirm GWIA service is running
    Check if the GroupWise Internet Agent service is running. On Windows, use Services.msc or command: sc query GWIA. On Linux, check for the gwia process: ps -ef | grep -i gwia.
    Affected if The GWIA service is active and listening for incoming email connections
  3. Verify installed GroupWise version
    Check the GroupWise version by examining the DLL properties of gwwww1.dll (right-click > Properties > Version tab), or query the GWIA service version using: gwia -v or check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\GWIA\CurrentVersion on Windows.
    Affected if The installed version is exactly 8.0 (build 8.0.x)
  4. Confirm VCALENDAR attachment processing is enabled
    Check GWIA configuration settings for calendar/VCALENDAR processing. In the GWIA console or configuration files (typically gwia.cfg), verify if iCal/V CALENDAR parsing is enabled for incoming email.
    Affected if VCALENDAR attachment parsing is enabled in the GWIA configuration, allowing the vulnerable code path to be exercised

A system is affected if GroupWise Internet Agent version 8.0 is installed with the GWIA service running and VCALENDAR attachment processing enabled, as the integer truncation flaw in gwwww1.dll is triggered during TZNAME parsing in incoming email.

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

Apply the HP3 patch for Novell GroupWise 8.0 or upgrade to a supported version. Consider implementing email filtering at the gateway to block or sanitize VCALENDAR attachments from untrusted sources until the patch can be applied.

Recommended fix Moderate confidence

GroupWise 8.0 HP3 (or subsequent Service Pack containing the fix)

  1. Locate the HP3 patch for Novell GroupWise 8.0 from the Novell patches/downloads site or Novell Customer Center
  2. Apply the HP3 patch to the GroupWise 8.0 Internet Agent (GWIA) installation
  3. Alternatively, if available, upgrade to a newer GroupWise 8.0 Service Pack that includes the fix
  4. Verify the patch was applied successfully by checking the GWIA version and build number
  5. Test that VCALENDAR attachments with TZNAME fields are properly processed after the update
Caveat Standard patch application precautions apply - test in non-production environment first, ensure backups exist

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-0333 — 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-2011-0333 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