S-359: Vulnerability in Cisco WebEx Meeting Manager ActiveX Control


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-359: Vulnerability in Cisco WebEx Meeting Manager ActiveX Control
# 1  
Old 08-18-2008
S-359: Vulnerability in Cisco WebEx Meeting Manager ActiveX Control

A buffer overflow vulnerability exists in an ActiveX control used by the WebEx Meeting manager. Exploitation of this vulnerability could allow a remote attacker to execute arbitrary code on the user client machine. The risk is MEDIUM. Exploitation of this vulnerability could allow a remote attacker to execute arbitrary code on the user client machine.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
WIN32_START_SERVICE_CTRL_DISPATCHER(3)					 1				    WIN32_START_SERVICE_CTRL_DISPATCHER(3)

win32_start_service_ctrl_dispatcher - Registers the script with the SCM, so that it can act as the service with the given name

SYNOPSIS
mixed win32_start_service_ctrl_dispatcher (string $name) DESCRIPTION
When launched via the Service Control Manager, a service process is required to "check-in" with it to establish service monitoring and communication facilities. This function performs the check-in by spawning a thread to handle the lower-level communication with the service control manager. Once started, the service process should do 2 things. The first is to tell the Service Control Manager that the service is running. This is achieved by calling win32_set_service_status(3) with the WIN32_SERVICE_RUNNING constant. If you need to perform some lengthy process before the service is actually running, then you can use the WIN32_SERVICE_START_PENDING constant. The second is to continue to check-in with the service control manager so that it can determine if it should terminate. This is achieved by periodically calling win32_get_last_control_message(3) and handling the return code appropriately. PARAMETERS
o $name - The short-name of the service, as registered by win32_create_service(3). RETURN VALUES
Returns TRUE on success, FALSE if there is a problem with the parameters or a Win32 Error Code on failure. EXAMPLES
Example #1 A win32_start_service_ctrl_dispatcher(3) example Check if the service is runnig under the SCM. <?php if (!win32_start_service_ctrl_dispatcher('dummyphp')) { die("I'm probably not running under the service control manager"); } win32_set_service_status(WIN32_SERVICE_START_PENDING); // Some lengthy process to get this service up and running. win32_set_service_status(WIN32_SERVICE_RUNNING); while (WIN32_SERVICE_CONTROL_STOP != win32_get_last_control_message()) { # do some work here, trying not to take more than around 30 seconds # before coming back into the loop again } ?> SEE ALSO
win32_set_service_status(3), win32_get_last_control_message(3), Win32 Error Codes. PHP Documentation Group WIN32_START_SERVICE_CTRL_DISPATCHER(3)