dbcve.org
Iprint ClientApplication · Novell

CVE-2008-2908

HIGH · 9.3 CVSS v2.0 Published 2008-06-30
Fix available
A fix is available. Upgrade to after 4.35 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
Multiple stack-based buffer overflows in a certain ActiveX control in ienipp.ocx in Novell iPrint Client for Windows before 4.36 allow remote attackers to execute arbitrary code via a long value of the (1) operation, (2) printer-url, or (3) target-frame parameter. NOTE: some of these details are obtained from third party information.

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

Stack-based buffer overflow vulnerability in the ienipp.ocx ActiveX control of Novell iPrint Client for Windows versions prior to 4.36. Overflow occurs when processing overly long strings in the operation, printer-url, or target-frame parameters, allowing remote attackers to execute arbitrary code.

MitigationUpgrade Novell iPrint Client to version 4.36 or later; alternatively, disable the ienipp.ocx ActiveX control in Internet Explorer or via Group Policy if the iPrint functionality is not required.

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
Iprint ClientApplication
Affected:<= 4.35

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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. Check if Novell iPrint Client is installed
    Look for the iPrint Client installation in Program Files directory, check Add/Remove Programs, or query the registry under HKLM\SOFTWARE\Novell\iPrint
    Affected if Novell iPrint Client is found on the system and the installed version is 4.35 or lower
  2. Determine the installed iPrint Client version
    Open the Windows registry and navigate to HKLM\SOFTWARE\Novell\iPrint\Client\CurrentVersion, or right-click the ienipp.ocx file in System32 or SysWOW64 and select Properties to view the File Version
    Affected if The version number shown is 4.35 or any version lower than 4.36
  3. Verify the ienipp.ocx ActiveX control is registered
    Check the Windows registry under HKCR\CLSID for the iPrint ActiveX control CLSID, or run 'regsvr32 /s ienipp.ocx' to check registration status
    Affected if The ienipp.ocx ActiveX control is registered as an Internet Explorer add-on
  4. Confirm the control is enabled in Internet Explorer
    Open Internet Explorer, go to Manage Add-ons, and look for the iPrint ActiveX control under Toolbars and Extensions
    Affected if The ienipp.ocx ActiveX control is enabled and allowed to run in Internet Explorer

A system is affected if Novell iPrint Client version 4.35 or lower is installed with the ienipp.ocx ActiveX control present and enabled in Internet Explorer.

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 4.35
Interim mitigation

Upgrade Novell iPrint Client to version 4.36 or later; alternatively, disable the ienipp.ocx ActiveX control in Internet Explorer or via Group Policy if the iPrint functionality is not required.

Recommended fix High confidence

Novell iPrint Client 4.36 or later

  1. Open Windows Control Panel and navigate to 'Programs and Features'
  2. Locate 'Novell iPrint Client' in the list of installed programs
  3. Note the current version number to confirm it is 4.35 or earlier
  4. Uninstall the current version of Novell iPrint Client
  5. Restart the Windows system if prompted by the uninstaller
  6. Download Novell iPrint Client version 4.36 or later from the official Novell support website (support.novell.com)
  7. Run the installer for the new version and follow the on-screen prompts
  8. Restart the computer after installation completes

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

Fix this in Iprint Client Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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