HPSBGN01156 SSRT2400 rev.2 - HP-UX, HP Tru64 UNIX, HP NonStop, Using DNS, Remote Denial of Service (DoS)

  • KM02992241
  • 17-Oct-2017
  • 17-Oct-2017

Summary

HP-UX, Tru64 and NonStop hosts that use DNS are subject to a security vulnerability in the form of a remote Denial of Service (DoS). DNS requests could be caused to resolve to an incorrect host.

Reference

SUPPORT COMMUNICATION - SECURITY BULLETIN

Document ID: KM02992241 (c01038033)

Version: 1

HPSBGN01156 SSRT2400 rev.2 - HP-UX, HP Tru64 UNIX, HP NonStop, Using DNS, Remote Denial of Service (DoS)
NOTICE: The information in this Security Bulletin should be acted upon as soon as possible.

Release Date: 2003-08-07

Last Updated: 2007-04-26


Potential Security Impact: Remote Denial of Service (DoS)

Source: Hewlett-Packard Company, HP Software Security Response Team

VULNERABILITY SUMMARY

HP-UX, Tru64 and NonStop hosts that use DNS are subject to a security vulnerability in the form of a remote Denial of Service (DoS). DNS requests could be caused to resolve to an incorrect host.

References: CERT VU#457875

SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed.

HP-UX, HP Tru64 UNIX HP NonStop Systems may be affected by this vulnerability if it runs a bindv4 name server that is configured to both: support recursive requests and cache the response results to DNS requests made by untrusted systems.

HP-UX 10.0*, 11.0

HP NonStop Server running Domain Name Service (T6021 NAMED) in the TCP/IP subsystem on both G06 and D48 versions of the operating system

HP OpenVMS ( Research continues )

Tru64 V4.0F, V4.0G

BACKGROUND

For a PGP signed version of this security bulletin please write to: security-alert@hp.com

When a bind name server receives a client request to resolve a host name or IP address, and is unable to resolve the request locally, it sends the request to another name server and waits for a response. In BINDv4, multiple client requests for the same domain name generate multiple requests, with multiple responses expected. This increases the probability that an attacker will be able to generate a malicious response that will be accepted as valid, thus compromising the information stored in the name server's cache and potentially causing clients to be misdirected to hostile or compromised hosts.

RESOLUTION

Recommended Workarounds

If you are running a BINDv4 name server configured to respond to recursive requests from untrusted systems, either reconfigure it to disable recursion, or make it inaccessible to untrusted systems.

HP-UX Recommended Workaround

To disable recursion, add the following line to /etc/namedb/named.conf: options no-recursion

Tru64 Recommended Workarounds

To disable recursion, add the following line to /etc/namedb/named.boot: options no-recursion

Note: Because ISC deprecates the use of BINDv4, HP recommends upgrading to a later version of BIND where possible. HP will be providing an updated BIND for HP Tru64 UNIX V4.0x systems at a later date.

To make the system inaccessible to untrusted systems, see traffic filtering recommendations in the CERT publication "Securing an Internet Name Server, available at: http://www.cert.org/archive/pdf/dns.pdf Non-HPE site

In order for BIND clients to reference hosts outside of your domain, they must be able to access some name server able to perform recursive requests safely. If your BINDv4 name server is the primary name server for your domain and you do not choose to move the database, HP recommends that you set up a BINDv8 name server as a slave of the BINDv4 name server -- see the bindsetup utility. Use the original name server's IP address for the BINDv8 name server so that no edit is required on clients. The clients will then receive their local information from the BINDv8 server and are able to recursively query through it safely. The BINDv4 system is protected because it is not performing recursion.

HP NonStop Server Recommended Workarounds

If you are running a Domain Name Service (T6021) configured to respond to recursive requests from untrusted systems, make it inaccessible to untrusted systems.

HISTORY 
Revision: 0 (rev.0) - 7 August 2003 Initial release 
Version: 1 (rev.1) - 19 May 2005 Reformatted 
Version: 2 (rev.2) - 26 April 2007 Reformatted

©Copyright 2007 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HP or its affiliates, subcontractors or suppliers will be liable for incidental,special or consequential damages including downtime cost; lost profits;damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett-Packard Company and the names of Hewlett-Packard products referenced herein are trademarks of Hewlett-Packard Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.