dbcve.org
IprintApplication · Novell

CVE-2011-1702

HIGH · 9.3 CVSS v2.0 Published 2011-06-09
Fix available
A fix is available. Upgrade to after 5.60 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
Heap-based buffer overflow in nipplib.dll in Novell iPrint Client before 5.64 allows remote attackers to execute arbitrary code via a crafted file-date-time parameter in a printer-url.

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

Heap-based buffer overflow in nipplib.dll in Novell iPrint Client versions prior to 5.64 allows remote attackers to execute arbitrary code via a specially crafted file-date-time parameter embedded in a printer-url. The vulnerability stems from insufficient bounds checking when parsing the file-date-time parameter, leading to heap memory corruption that can be leveraged for remote code execution.

MitigationUpgrade Novell iPrint Client to version 5.64 or later to patch the vulnerability. If immediate patching is not feasible, restrict access to untrusted printer URLs and disable iPrint client features until the update 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
IprintApplication
Affected:<= 5.60= 4.26= 4.27= 4.28= 4.30= 4.32= 4.34= 4.36= 4.38= 5.04= 5.12= 5.20b

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. Verify Novell iPrint Client is installed
    Check for the presence of the iPrint client software on the system. Common installation paths include C:\Program Files\Novell\iPrint or look for nipplib.dll in the system. On Windows, check Add/Remove Programs for 'Novell iPrint' or 'Novell iPrint Client'.
    Affected if Novell iPrint Client is installed on the system.
  2. Locate and identify the nipplib.dll version
    Find the nipplib.dll file in the iPrint installation directory (typically in the bin or client folder). Right-click the file, select Properties, and check the Version tab to obtain the file version. Alternatively, use the command: dir /s C:\nipplib.dll or search in the Novell installation directory.
    Affected if The nipplib.dll file is found and its version can be determined.
  3. Compare installed version against affected ranges
    Compare the discovered version (from nipplib.dll or the iPrint client installation) against the affected versions: 4.26, 4.27, 4.28, 4.30, 4.32, 4.34, 4.36, 4.38, 5.04, 5.12, 5.20b, and any version 5.60 or lower. Note that versions 5.64 and later are not affected.
    Affected if The installed version matches one of the affected versions listed (4.26, 4.27, 4.28, 4.30, 4.32, 4.34, 4.36, 4.38, 5.04, 5.12, 5.20b) or is 5.60 or lower.
  4. Determine if iPrint printer URLs with file-date-time are processed
    The vulnerability is triggered when the iPrint client parses a specially crafted printer URL containing a file-date-time parameter. Check system logs, network traffic, or user activity for iPrint printer connection attempts. The client must actively process a malicious printer URL for the overflow to occur.
    Affected if The iPrint client is used to connect to printers via URL-based printer installation, and a specially crafted URL with an oversized file-date-time parameter could be processed.

A system is affected by CVE-2011-1702 if Novell iPrint Client is installed with nipplib.dll version 4.26, 4.27, 4.28, 4.30, 4.32, 4.34, 4.36, 4.38, 5.04, 5.12, 5.20b, or any version 5.60 or earlier, and the client processes printer URLs containing the file-date-time parameter.

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

Upgrade Novell iPrint Client to version 5.64 or later to patch the vulnerability. If immediate patching is not feasible, restrict access to untrusted printer URLs and disable iPrint client features until the update can be applied.

Recommended fix High confidence

Novell iPrint Client 5.64 or later

  1. Obtain Novell iPrint Client version 5.64 or later from the official Novell download portal (download.novell.com) or your organization's patch management system
  2. Uninstall the current version of Novell iPrint Client
  3. Install the updated Novell iPrint Client version 5.64 or newer
  4. Verify the installation by checking the client version in the Windows Add/Remove Programs or equivalent

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

Fix this in Iprint Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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