CVE-2010-3106 in the critical feed json
The ienipp.ocx ActiveX control in the browser plugin in Novell iPrint Client before 5.42 does not properly validate the debug parameter, wh…
published 16y ago modified 4mo ago also EUVD-2010-3106
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 37.3%
- EPSS 37.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 3
- Metasploit and Exploit-DB
Summary
The ienipp.ocx ActiveX control in the browser plugin in Novell iPrint Client before 5.42 does not properly validate the debug parameter, which allows remote attackers to execute arbitrary code or cause a denial of service (stack memory corruption) via a parameter value with a crafted length, related to the ExecuteRequest method.
Patch / fix
Is CVE-2010-3106 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/windows/browser/novelliprint_executerequest_dbg)
- Published
Exploit prediction
37.33% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/browser/novelliprint_executerequest_dbg Novell iPrint Client ActiveX Control ExecuteRequest debug Buffer Overflow metasploit exploit, normal rank, 2010-08-04
- EDB-16492 Novell iPrint Client - ActiveX Control ExecuteRequest debug Buffer Overflow (Metasploit) remote, 2010-09-21
- EDB-15073 Novell iPrint Client - ActiveX Control 'debug' Remote Buffer Overflow (Metasploit) remote, 2010-09-21
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- CVE List CVE-2010-3106
- NVD CVE-2010-3106
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.