dbcve.org
IprintApplication · Novell

CVE-2011-1706

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
Stack-based buffer overflow in nipplib.dll in Novell iPrint Client before 5.64 allows remote attackers to execute arbitrary code via a crafted iprint-client-config-info 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

Stack-based buffer overflow in nipplib.dll in Novell iPrint Client versions before 5.64 allows remote attackers to execute arbitrary code by sending a crafted iprint-client-config-info parameter within a printer-url. The overflow occurs on the stack, potentially allowing an attacker to overwrite return addresses and inject malicious code.

MitigationUpdate Novell iPrint Client to version 5.64 or later to remediate the vulnerability. Until patched, avoid opening untrusted printer URLs.

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. Locate the Novell iPrint Client installation
    Search for nipplib.dll on the system, typically found in the Novell iPrint client installation directory (e.g., C:\Program Files\Novell\iPrint or similar). Also check Windows Add/Remove Programs for 'Novell iPrint Client'.
    Affected if Novell iPrint Client is not installed or the DLL is not present.
  2. Check the installed iPrint Client version
    Right-click on nipplib.dll, select Properties, then view the Details tab for the File Version. Alternatively, check the Windows registry under HKLM\SOFTWARE\Novell\iPrint or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the iPrint Client entry.
    Affected if The version is 5.60 or lower, or matches any of these specific versions: 4.26, 4.27, 4.28, 4.30, 4.32, 4.34, 4.36, 4.38, 5.04, 5.12, or 5.20b.
  3. Verify the vulnerability trigger condition
    Confirm that the system uses the iPrint Client functionality that processes printer URLs with the iprint-client-config-info parameter. This is typically used when connecting to network printers via iPrint. Check for recent incoming printer connection requests or logs.
    Affected if The iPrint Client processes printer URLs containing the iprint-client-config-info parameter.

A system is affected if Novell iPrint Client is installed with any version listed as vulnerable (5.60 or lower, or any of the specific versions 4.26 through 5.20b) and the client processes iPrint printer URLs with the iprint-client-config-info 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

Update Novell iPrint Client to version 5.64 or later to remediate the vulnerability. Until patched, avoid opening untrusted printer URLs.

Recommended fix High confidence

Novell iPrint Client 5.64 or later

  1. Identify the current Novell iPrint Client version installed on the system
  2. Navigate to the official Novell/NetIQ download page or authorized partner site to obtain iPrint Client version 5.64 or later
  3. Download the appropriate installer for your operating system (Windows32/64)
  4. Close all applications that may interact with iPrint (browsers, print spooler)
  5. Run the installer with administrative privileges
  6. Follow the on-screen installation prompts to complete the upgrade
  7. Verify the installed version matches or exceeds 5.64
  8. Test iPrint functionality to ensure the client operates correctly
Caveat Standard upgrade - verify compatibility with existing print servers and ensure printer mappings are re-established if needed

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

Fix this in Iprint Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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