ID CVE-2010-4321
Summary Stack-based buffer overflow in an ActiveX control in ienipp.ocx in Novell iPrint Client 5.52 allows remote attackers to execute arbitrary code via a long argument to (1) the GetDriverSettings2 method, as reachable by (2) the GetDriverSettings method.
Vulnerable Configurations
  • cpe:2.3:a:novell:iprint_client:5.52
Base: 9.3 (as of 30-12-2010 - 15:03)
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
exploit-db via4
  • description Novell iPrint Client ActiveX Control. CVE-2010-4321. Remote exploit for windows platform
    id EDB-ID:16956
    last seen 2016-02-02
    modified 2011-03-07
    published 2011-03-07
    reporter metasploit
    title Novell iPrint Client ActiveX Control <= 5.52 - Buffer Overflow
  • description Novell iPrint <= 5.52 - ActiveX GetDriverSettings() Remote Exploit (ZDI-10-256). CVE-2010-4321. Remote exploit for windows platform
    file exploits/windows/remote/16014.html
    id EDB-ID:16014
    last seen 2016-02-01
    modified 2011-01-19
    platform windows
    published 2011-01-19
    reporter Dr_IDE
    title Novell iPrint <= 5.52 - ActiveX GetDriverSettings Remote Exploit ZDI-10-256
    type remote
metasploit via4
description This module exploits a stack buffer overflow in Novell iPrint Client 5.52. When sending an overly long string to the GetDriverSettings() property of ienipp.ocx an attacker may be able to execute arbitrary code.
last seen 2019-03-17
modified 2017-10-05
published 2011-03-06
reliability Normal
reporter Rapid7
title Novell iPrint Client ActiveX Control Buffer Overflow
nessus via4
NASL family Windows
description The version of Novell iPrint Client installed on the remote host is earlier than 5.56. Such versions are reportedly affected by one or more of the following vulnerabilities that can allow for arbitrary code execution : - The iPrint ActiveX control fails to sanitize input to the 'GetDriverSettings2()' method in the 'ienipp.ocx' component before copying it into a fixed-length buffer on the stack. (ZDI-10-256 / CVE-2010-4321) - There is a stack-based buffer overflow in both the Netscape (Firefox) and ActiveX (Internet Explorer) plugin components ('npnipp.dll' and 'ienipp.ocx') due to their failure to sufficiently validate the size of a printer-state-reasons status response. (ZDI-10-295) - Buffer overflows exist in both the Netscape (Firefox) and ActiveX (Internet Explorer) plugin components ('npnipp.dll' and 'ienipp.ocx') due to their failure to sufficiently validate the size of an IPP response from a user provided printer-url. (ZDI-10-296 and ZDI-10-299) - The 'nipplib.dll component, as used by both types of browser plugins, does not properly handle the value of the Location response header in an HTTP 301 response when copying it into a buffer of fixed size. (ZDI-10-297) - A stack-based buffer overflow exists in the 'npnipp.dll' Mozilla browser plugin because it fails to validate a user input to a call-back-url before passing it to a urlencode function and copying the result into a fixed-length buffer. (ZDI-10-298) - The 'nipplib.dll component, as used by both types of browser plugins, does not properly handle the value of the Connection response header in an HTTP response when copying it into a stack-based buffer of fixed size. (ZDI-10-300)
last seen 2019-02-21
modified 2018-11-15
plugin id 51367
published 2010-12-29
reporter Tenable
title Novell iPrint Client < 5.56 Multiple Vulnerabilities
packetstorm via4
refmap via4
bid 44966
exploit-db 16014
sreason 8125
saint via4
bid 44966
description Novell iPrint Client ActiveX Control GetDriverSettings buffer overflow
osvdb 69357
title novell_iprint_activex_getdriversettings
type client
Last major update 21-09-2011 - 00:00
Published 30-12-2010 - 14:00
Back to Top