dbcve.org
IprintApplication · Novell

CVE-2011-4185

HIGH · 10.0 CVSS v2.0 Published 2012-02-21
Fix available
A fix is available. Upgrade to after 5.74 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
The GetPrinterURLList2 method in the ActiveX control in Novell iPrint Client before 5.78 on Windows allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2008-2431 and CVE-2008-2436.

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 · moderate confidence

The GetPrinterURLList2 method in the Novell iPrint Client ActiveX control before version 5.78 on Windows contains a memory corruption vulnerability allowing remote attackers to execute arbitrary code or cause denial of service via unspecified vectors.

MitigationUpgrade Novell iPrint Client to version 5.78 or later, or disable the vulnerable ActiveX control in Internet Explorer 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.74= 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
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 Novell iPrint Client is installed
    Check for the presence of Novell iPrint Client on the Windows system by looking in Add/Remove Programs (appwiz.cpl) or by searching for iPrint-related files in Program Files directory.
    Affected if Novell iPrint Client is present on the system
  2. Determine the installed iPrint Client version
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Novell\iPrint or check the version property of the iPrint ActiveX control file (typically niPrint.dll or similar) in the Windows\System32 or Windows\SysWOW64 directory using properties dialog.
    Affected if The version number cannot be determined or the product is found
  3. Compare installed version against affected list
    If the version is found, compare it to 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, or any version 5.74 and below.
    Affected if The installed version matches any version in the affected list
  4. Confirm the ActiveX control is present and registered
    Check for the iPrint ActiveX control CLSID in the Windows Registry under HKEY_CLASSES_ROOT\CLSID or verify the control is registered in Internet Explorer via Tools > Manage Add-ons.
    Affected if The GetPrinterURLList2 ActiveX method is registered and available in Internet Explorer

The system is affected if Novell iPrint Client version is one of the listed affected versions (4.26-4.38, 5.04-5.74, 5.20b) AND the vulnerable ActiveX control with the GetPrinterURLList2 method is present and enabled.

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.74
Interim mitigation

Upgrade Novell iPrint Client to version 5.78 or later, or disable the vulnerable ActiveX control in Internet Explorer until the update can be applied.

Recommended fix High confidence

Novell iPrint Client 5.78 or later

  1. Verify the currently installed Novell iPrint Client version on the Windows system
  2. Download Novell iPrint Client version 5.78 or later from the official Novell support website
  3. Close all applications that may be using the iPrint functionality
  4. Run the installer with administrative privileges
  5. Follow the on-screen installation prompts to complete the upgrade
  6. Restart the system if prompted by the installer
  7. Verify the installed version matches or exceeds 5.78

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

Fix this in Iprint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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