CVE-2012-0411
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 · uneditedUnspecified vulnerability in Novell iPrint Client before 5.82 allows remote attackers to execute arbitrary code via an op-client-interface-version action.
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 confidenceNovell iPrint Client versions before 5.82 contain an unspecified vulnerability that allows remote attackers to execute arbitrary code via the 'op-client-interface-version' action. The CVSS 10 score indicates a critical, easily exploitable flaw with complete compromise potential.
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<= 5.78= 4.26= 4.27= 4.28= 4.30= 4.32= 4.34= 4.36= 4.38= 5.04= 5.12= 5.20bCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Novell iPrint Client is installedCheck Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Novell iPrint' or inspect Program Files for 'Novell iPrint' folderAffected if No Novell iPrint installation is found - the system is not affected by this CVE
-
Locate the iPrint client executable or DLLSearch for niipp.dll, iclppxe.dll, or nipc.dll in the Novell iPrint program directory, typically found under C:\Program Files\Novell\iPrint or C:\Program Files (x86)\Novell\iPrintAffected if The iPrint client binaries are present on the system
-
Retrieve the installed version numberRight-click the main executable or DLL, select Properties, then view the Details tab for Product Version, or query the Windows Registry key: HKLM\SOFTWARE\Novell\iPrint\CurrentVersionAffected if A version number is returned from the binary or registry
-
Compare version against affected listDetermine if the installed version matches any of the following: <= 5.78, 4.26, 4.27, 4.28, 4.30, 4.32, 4.34, 4.36, 4.38, 5.04, 5.12, or 5.20bAffected if The installed version is one of these specific versions - the system is vulnerable to CVE-2012-0411
-
Confirm the vulnerable op-client-interface-version action is accessibleVerify the iPrint service is running and the web interface (typically port 631/9635) is accessible, as exploitation occurs through the 'op-client-interface-version' actionAffected if The iPrint service is exposed and accepts this action - the vulnerability is reachable
A system is affected if Novell iPrint Client is installed with a version matching <= 5.78 or any of the 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, and the iPrint service is accessible to accept the malicious action.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Novell iPrint Client to version 5.82 or later to remediate this vulnerability.
iPrint Client 5.82 or later (for version 4.x users, upgrade to 5.82+)
- Obtain Novell iPrint Client version 5.82 or later from official Novell channels
- Uninstall the current version of Novell iPrint Client
- Install the updated iPrint Client version 5.82 or later
- Verify the installation by checking the client version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0411 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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