S-251: Vulnerability in DNS Client


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-251: Vulnerability in DNS Client
# 1  
Old 04-09-2008
S-251: Vulnerability in DNS Client

A spoofing vulnerability exists in Windows DNS clients. The vulnerability could allow an unauthenticated attacker to send malicious responses to DNS requests made by vulnerable clients, thereby spoofing or redirecting Internet traffic from legitimate locations. The risk is MEDIUM. Could allow an unauthenticated attacker to send malicious responses to DNS requests made by vulnerable clients, thereby spoofing or redirecting Internet traffic from legitimate locations.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies

2. Solaris

DNS client - what exactly it is

Hi all, I always thought DNS server = provide DNS response (host to ip / ip to host) to DNS client (which send DNS resolve request). So in my solaris 10 box, i setup /etc/resolv/conf, /etc/nsswitch.conf (added in dns) etc. Yes, i am able to dig and nslookup. But.. am i a DNS client ? ... (5 Replies)
Discussion started by: javanoob
5 Replies

3. Linux

How to add a client to DNS server

Hi all, What is the procedure to add a client to a DNS server. what are the settings and files need to be added/changed ? thanks in advance! (6 Replies)
Discussion started by: lramsb4u
6 Replies

4. IP Networking

How to Determine client's DNS server Ip

Is there a way for a server to determine client's DNS ip? I have an application that logs client's IP but in certain cases its desirable to know their DNS too (1 Reply)
Discussion started by: vickylife
1 Replies

5. Solaris

dns client not working

Hi All, I have configured linux server as local dns server (practice level). I have given the IP and hostname details in /etc/hosts -bash-3.00# cat /etc/hosts # # Internet host table # ::1 localhost 127.0.0.1 localhost 192.168.1.78 dummy.set.com loghost 192.168.1.57 cent.set.com #... (3 Replies)
Discussion started by: vaibhav.kanchan
3 Replies

6. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

7. UNIX for Advanced & Expert Users

DNS client nslookup

Hello, I just got done setting up a DNS server and a client. However, when I do an nslookup with just the hostname, I got this output: Microsoft Windows 2000 (C) Copyright 1985-2000 Microsoft Corp. C:\Documents and Settings\dev9>nslookup dev9 Server: webdev.testsurgemail.com Address:... (3 Replies)
Discussion started by: xnightcrawl
3 Replies
Login or Register to Ask a Question
Net::DNS::Async(3pm)					User Contributed Perl Documentation				      Net::DNS::Async(3pm)

NAME
Net::DNS::Async - Asynchronous DNS helper for high volume applications SYNOPSIS
use Net::DNS::Async; my $c = new Net::DNS::Async(QueueSize => 20, Retries => 3); for (...) { $c->add(&callback, @query); } $c->await(); sub callback { my $response = shift; ... } DESCRIPTION
Net::DNS::Async is a fire-and-forget asynchronous DNS helper. That is, the user application adds DNS questions to the helper, and the callback will be called at some point in the future without further intervention from the user application. The application need not handle selects, timeouts, waiting for a response or any other such issues. If the same query is added to the queue more than once, the module may combine the queries; that is, it will perform the query only once, and will call each callback registered for that query in turn, passing the same Net::DNS::Response object to each query. For this reason, you should not modify the Net::DNS::Response object in any way lest you break things horribly for a subsequent callback. This module is similar in principle to POE::Component::Client::DNS, but does not require POE. CONSTRUCTOR
The class method new(...) constructs a new helper object. All arguments are optional. The following parameters are recognised as arguments to new(): QueueSize The size of the query queue. If this is exceeded, further calls to add() will block until some responses are received or time out. Retries The number of times to retry a query before giving up. Timeout The timeout for an individual query. METHODS
$c->add($callback, @query) Adds a new query for asynchronous handling. The @query arguments are those to Net::DNS::Resolver->bgsend(), q.v. This call will block if the queue is full. When some pending responses are received or timeout events occur, the call will unblock. The user callback will be called at some point in the future, with a Net::DNS::Packet object representing the response. If the query timed out after the specified number of retries, the callback will be called with undef. $c->await() Flushes the queue, that is, waits for and handles all remaining responses. BUGS
The test suite does not test query timeouts. SEE ALSO
Net::DNS, POE::Component::Client::DNS COPYRIGHT
Copyright (c) 2005-2006 Shevek. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.0 2008-10-03 Net::DNS::Async(3pm)