Sponsored Content
Special Forums Cybersecurity Security Advisories (RSS) R-229: Vulnerability in Windows DNS RPC Interface (935966) Post 302153317 by Linux Bot on Monday 24th of December 2007 08:40:53 AM
Old 12-24-2007
R-229: Vulnerability in Windows DNS RPC Interface (935966)

A remote code execution vulnerability exists in the Domain Name System (DNS) Server Service in all supported server versions of Windows that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system. The risk is HIGH. A remote code execution vulnerability exists in the Domain Name System (DNS) Server Service in all supported server versions of Windows that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.


More...
 

2 More Discussions You Might Find Interesting

1. Solaris

is RPC portable accross Unix and windows

Hi All, I am working on Unix(SunOS 5.8) and windows machine.My server lies on Unix machine and clinet on windows. Could you please tell me If I have created abc.x file for unix machine and have written a routine require for remote call, How do I proceed to get client code of RPC for windows... (0 Replies)
Discussion started by: navin_1234
0 Replies

2. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies
Event::RPC::Connection(3pm)				User Contributed Perl Documentation			       Event::RPC::Connection(3pm)

NAME
Event::RPC::Connection - Represents a RPC connection SYNOPSIS
Note: you never create instances of this class in your own code, it's only used internally by Event::RPC::Server. But you may request connection objects using the connection_hook of Event::RPC::Server and then having some read access on them. my $connection = Event::RPC::Server::Connection->new ( $rpc_server, $client_socket ); As well you can get the currently active connection from your Event::RPC::Server object: my $server = Event::RPC::Server->instance; my $connection = $server->get_active_connection; DESCRIPTION
Objects of this class represents a connection from an Event::RPC::Client to an Event::RPC::Server instance. They live inside the server and the whole Client/Server protocol is implemented here. READ ONLY ATTRIBUTES
The following attributes may be read using the corresponding get_ATTRIBUTE accessors: cid The connection ID of this connection. A number which is unique for this server instance. server The Event::RPC::Server instance this connection belongs to. is_authenticated This boolean value reflects whether the connection is authenticated resp. whether the client passed correct credentials. auth_user This is the name of the user who was authenticated successfully for this connection. client_oids This is a hash reference of object id's which are in use by the client of this connection. Keys are the object ids, value is always 1. You can get the corresponding objects by using the $connection->get_client_object($oid) method. Don't change anything in this hash, in particular don't delete or add entries. Event::RPC does all the necessary garbage collection transparently, no need to mess with that. AUTHORS
Joern Reder <joern at zyn dot de> COPYRIGHT AND LICENSE
Copyright (C) 2002-2006 by Joern Reder, All Rights Reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2008-10-25 Event::RPC::Connection(3pm)
All times are GMT -4. The time now is 03:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy